Using Voicemeeter, or VB Audio Matrix (same company), if I set an audio device in or out chop to use any of the virtual ASIO devices, I get no audio in or out. There is no error showing in the info for the chop.
If I use the real audio interface ASIO device, it works as expected.
I have verified that with other applications the virtual ASIO devices do work as expected, so I can only assume the issue is with TD.
It was suggested to me that the issue might be related to the sample rate (and other bug reports here showed that TD used to crash entirely using Voicemeeter and 192k), so I tried setting everything everywhere to 44100 (instead of my usual 48000) but this did not make any difference.
Hi any update on this? I’m facing the same issue, I can pipe audio properly back and forth between audio interface / DAW and Voicemeeter, and virtual output in VM is working as expected. But audio audiodevin1 has no input, and also no error displayed. Tested using 44.1 and 48k.
A bit more info in case it’s useful: Tested with VB audio matrix, sending audio from DAW virtual channels a) to ASIO hardware out audio goes through speakers, b) to virtual channels (all 8 virtual to be sure) nothing is showing up in TD even when the audio is being clearly piped from DAW to virtual channels as seen in the image. No errors displayed.
I have the same issue. I just started trying to use the software. I’m using a MOTU. I actually had the ASIO work briefly on all voicemeeter asio outputs and other asio outputs such as asio4all2. But then it stopped working and will not work again. I can exit and restart the application to no avail. Why it worked briefly on ASIO I don’t know. ASIO works fine with other applications. A downer because I thought this could solve a problem for me but apparently not. To note, it breaks all asio so asio doesn’t work at all.
From my testing, the bug is only present when using Float32LSB sample type in VBAudioMatrix (which is the default). If you switch to Int32LSB Virtual ASIO Type under Settings then that should resolve the input/output issues you’re experiencing while we work on a fix in the meantime.
I’m not sure about other virtual devices, but if they have an option to choose between float vs int then int should be used for now.