The behaviour is identical to using the backend ASIO driver directly… just with more steps, more complexity, and more opportunities for things to go wrong. Instead, what's going to happen is that the multiple PortAudio instances are going to act independently and each of them will try to initialize the backend ASIO driver for themselves. For that to work you'd need some kind of IPC for the client processes to coordinate with each other and mediate access to the ASIO driver. Just enabling the PortAudio ASIO backend is not sufficient to have multiple processes share the same ASIO driver instance. I'm going to see if this is enough to get a "multi-client adapter" working. Interestingly, it appears to be possible to replace the PortAudio DLL shipped with FlexASIO with one that supports ASIO. I gather that an ASIO backend could enable FlexASIO to be used as a multi-client wrapper around some other ASIO driver, so that two applications can share low-latency access to IO.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |