)...It would come in handy in some situations if MuLab was able to open all my ASIO interfaces, rather than just one at a time. I've got JACK installed and it's got JackRouter, which would let me route audio between multiple applications (much like Reaper has ReaRoute but without it being proprietary). It would be one more step towards my only needing MuLab... (JackRouter also has internal bit bridging, so a 64bit application can exchange audio with a 32bit application.)
The idea is I'd be able to use route audio from (64bit) MuLab to an external program, e.g. Jamulus or Jamtaba (both 32bit) and then back - send and return.
You'd need two new modules to make it easy to use: "send to audio destination", which would let you choose the ASIO driver and its "input"; "receive from audio source", which would let you choose the ASIO driver and its "output". The lists would exclude the primary ASIO driver in use, if there was one.
Then you'd plug in the send as usual, picking the destination from its editor. Any audio reaching it would get sent to the destination and passed through, too. (If you didn't want this, you'd have to stop the rack you'd plugged the send into passing the audio any further.) Elsewhere, you plug in a receive and any audio from the source would get mixed into the signal path. The receive side is probably tricky unless treated as per existing audio ins but I'd like to keep them semantically distinct for my use case
.(If not using ASIO, of course, you get the risk of the user choosing the ASIO driver for the hardware outs they're using and causing a crash/lock-up... so maybe only have the feature available if ASIO is in use, or limit the audio drivers available to match the current driver type, rather than only ASIO.)
