I vote for this one too!
In fact I think this may be the single most important missing feature for executables.
The developer should have a modules, analogue to the MIDI device selection, to allow smooth integration within the user interface.
Additionally, the developer should have the option to remove the menubar from the executable.
- Allow using multiple (separate) devices (i.e. if you have one ASIO device in your MIDI controller and another one in your recording hardware).
- Allow multiple (separate) channels for input and output (i.e. mix, monitor, metronome, tuning signal, 5.1/7.1/etc.)
- Allow it to be fully integrated in the developer-created user interface.
- Remember the prefered audio driver.
- Allow "automatic" selection of prefered audio driver (i.e. scan for the first line with "Audio 8" in it, otherwise the first line with "ASIO").
- Allow the developer to assist the user in selecting audio devices and integrate help functionality.
- Allow the removal of the menu bar.
It could be implemented pretty much identical to how MIDI devices can be selected, just an added "channel" integer and int array and it looks pretty much the same.
The only issue I can think of would be how to determine whether it's standalone or plug-in. With a simple boolean module, this issue could be solved.
I've made a quick mockup of what I think the modules could look like. It's not particularly spectaculair or special, and neither should it be. Can't upload to this forum, so here's a link to a file I uploaded on my website:
That's an OUT connector on the right. You know, for when it's a plug-in, it needs outs. And yes, it would also need an in and a selector module; I forgot
Actually, you wouldn't even need the selectors and multiplexers if you'd just wrap the VST-only module inside an executable module with all the device plumbing