aMUSEd: Well, the problem with that approach is that you lose project recall - ie that patches and settings are saved with the project in the sequencer. Also, are you sure that your suggested approach doesn't kill conventional midi/audio for the TI - as far as I recall, the TI goes into USB mode when running the VST. Will have to check it though.
Fireshark: Thanks for chiming in! Since Access is still developing on VC + the OS, I'm somewhat hopeful. I think the problem is that there's been an assumption that doing midi, audio, everything via USB was the right way to go, but that approach caused issues for some users and made it necessary for Access to try various workarounds (Live-mode, D-buttons, different outputs, etc).
I'm guessing that users spending thousands of euros/dollars on a TI are quite likely using it for professional/semi-professional purposes - and as such, they (we) probably already have a soundcard and a midi interface.
By implementing a mode in VC where it works as in standalone, without the USB audio/midi element but with the benefits of VC, they would've come a long way in solving these issues and generally giving their users a much smoother experience. They have a fine UI in VC, so they "just" need to implement that mode within the existing framework.
And at the end of the day, it would ultimately be to their own benefit as well, with fewer support issues, fewer miffed users etc.
So I’m *still* keeping my fingers crossed – but I guess I’ve been doing that for a while now..