hebele Thanks for offering to look at this.
I think I figured out my problem, and I think it's the interaction of the framework you're using (requiring an active audio device) with the way the ASIO Link Pro program takes control of the Windows default audio device when it runs. Since you mentioned providing a fake/dummy audio device, I realized I could do this on my own (outside of your program - no need for your program to provide it!), and in fact it does fix the problem. My use is very much an edge case, and it's fixed simply by providing an alternate audio device other than the Windows default audio device.
So, no need for you to worry about it (and the answer is that providing a fake/dummy audio device, for your program to always stay set to, does solve that problem). (And what you mentioned doesn't seem to be part of the original intent/design of your program, so no need to bother.) But thanks very much for offering.
