So I tried again to more closely simulate your config there and observe the behaviour:-
- Loopback, hijacking both Quicktime Player (playing audio), *and* my audio interface (which you can both record from/input and monitor from/output) as simulating your USB headset (which is your audio interface really.) Headphones connected to that. Mute sources On in Loopback as I'm monitoring through Audacity.
- System output set to my audio interface too.
- Audacity, set to record from Loopback (3 channels, 1 stereo, 1 mono, manual channel config in Loopback), and output back to my audio interface. Playthrough On.
- Begin playback from Quicktime. The audio is passed to the system, and I hear it from my headphones via the audio interface.
- Hit record in Audacity. There is a brief audio interruption (maybe 1/10th second) as Loopback enables itself. It mutes the audio being sent from Quicktime to the system (as Mute sources is On), and instead passes it through to Loopback, and hence to Audacity, where it's being recorded.
- Audacity has playthrough on, so is monitoring it's incoming audio and sending it back to it's own output, which is set to go to my audio interface. I hear it fine via Audacity. I'm recording three tracks, the first two the stereo audio, the third the mono input from the audio interface (ie your mic). All recorded fine.
So there is no inherent problem in playing back to a device already hijacked in Audacity, as inputs and outputs are treated separately (which makes sense.) I just wanted to confirm that and rule it out as a possible problem.
Everything about this config is working fine, and should be for you too as it's essentially the same thing, unless you are doing something incorrect or have some settings affecting the behaviour that hasn't been mentioned, or the drivers of your headset mic thing are causing problems or something. Unfortunately I can't sit in front of your computer and see what you are doing, so it's impossible to guess.
*In any case*, you have got to a set up that works for you, as far as I can see, by not monitoring from Audacity and intead using Loopback's monitoring, so as I say, stick to what works... :thumbup:
Things I have learnt from this exercise:
- Loopback is really great, and streamlines some otherwise complicated workflows. If/When I need it I'll get it for sure
- Audio Hijack is still great and covers much of the use case of Loopback for my needs. It's much simpler to use in this case as you can see the visual connections, see audio flowing along them, and has inbuilt recorder functionality so one app does the routing, hijacking, and recording, rather than passing things around between the system and other applications. The only thing Loopback can do that AH can't is pass audio to other applications (but I can do that with Soundflower if required.).
This is the exact same config as above, all done in one app:
Mic being recorded to one mono aiff file, stereo audio being recorded to a separate one. We could also record a third mix file of both, if required, in realtime. And avoids the need to use Audacity. ;)
- I still feel the same way about Audacity as I did when I started. :headbang: