desmond wrote:audio_jungle wrote:But it doesn't work for me... ;-)
The *feature* is working fine in Audacity, it's the overall behaviour of all the other components that aren't doing what you want yet. You have to break down and isolate things to troubleshoot.
You've already said that if you don't monitor in Audacity, and monitor via Loopback, everything works as you need. So why not stop there? - it's working how you like.
That is fine with me.
SInce you said you were able to get it working, I was just trying to figure out what I was doing wrong.
But I have bigger audio problems to tackle right now, so I can certainly "monitor" using Loopback.
desmond wrote:We can go on to troubleshoot this alternative way of using the system (monitoring through Audacity) but if you already have a config that is working, it's just a waste of time.
For now, yes it probably is.
desmond wrote:In this monitoring via Audacity case, the problem seems to be that really you always want to monitor back to your headset, which is a combined mic+headphones device, and one that you have *already captured* in Loopback - so you're outputting back to a device already captured by Loopback.
So, it seems wise to just monitor via Loopback, in the way you already have working.