I can think of only one "clean" way to have multiple concurrent instances of one ASIO driver in a single process: by somehow tricking the Windows DLL loader to load the same DLL multiple times at different points of the memory address space, such that the various "instances" of the ASIO ...
A change toFlexASIO.tomlwill make FlexASIO issue a driver reset request to the application. What happens next is up to the application; ideally, it should reload FlexASIO and pick up the new configuration. When an exclusive stream is currently running, FlexASIO now advertises every sample rate ...
The backends are shown in red on the diagram. They lead to various paths that the audio can take through the PortAudio library, and then through the Windows audio subsystem, before reaching the audio hardware driver and device. Roughly speaking, each backend maps to a single audio API that ...
audio processing at a low level in the audio driver, or baked into the hardware @@ -99,7 +99,7 @@ the fact that MME appears to [behave very poorly][issue30] with small buffer sizes. Latency numbers reported by MME do not seem to take the Windows audio pipeline into account. This ...