audio_jungle wrote:You said you weren't sure how Loopback was programmed.
Just in regards to that one behaviour, before Loopback is "in use", but it makes no difference exactly what's going on and is therefore inconsequential to anything, I just mentioned it for completeness.
audio_jungle wrote:It appears that when you create a virtual Loopback device, define an audio source in Loopback and then another application defines the virtual Loopback device as its "input" and then that application (e.g. Audacity) starts pulling data, then it appears as if Loopback stops routing audio to macOS and your hardware and starts routing it to the application using the virtual Loopback device.
Yes, as I explained above. This is Loopback "in use" as referenced in the manual.
audio_jungle wrote:(In the above scenario, it is also possible that when the virtual Loopback device is not in use, that audio from applications like Firefox is just following its normal path and going directly to macOS and your hardware.)
Yes. Like I say, when not in use, it doesn't matter whether Loopback is doing anything or not, all regular apps are just being output to the system as normal - whether Loopback is doing that or not makes no practical difference.
audio_jungle wrote:However, my suspicion, is that once a virtual Loopback device is created with sources, that it reaches up and starts grabbing audio from the applications in its "audio sources" but lets that audio pass-through to macOS and the hardware until some other application starts requesting/pulling audio, and then Loopback flips an internal switch and the audio flows directly to the application (e.g. Audacity).
Yes, that may be exactly how it's programmed. Or not - like I say, it's an implementation detail that makes no practical difference. It's the "in use" bit where the behaviour is important.
audio_jungle wrote:When I choose "Software Playthrough" it froze up Audacity, and I had to do a "Force Quit"?!
Difficult to help with Audacity, as I think it's terrible software anyway ;)
It doesn't freeze Audacity here.
audio_jungle wrote:When I hit "Record", I could no longer hear the audio as before. So it appears that option in Audacity doesn't do what you expected.
I'll have a look later. I read the docs, it should do what it promises to do, it's the whole point of that feature, and is a standard feature on all DAWs. :headbang:
audio_jungle wrote:In addition, when that option was checked, if I spoke into my headset as music played, I got feedback like before you helped me properly set things up.
If you're getting feedback, this only happen when something from an output is fed back into it's input. Given a correctly configured Loopback system, this is not happening via Loopback, which suggests that maybe your headset is very poor, and audio from the headset headphones is coming back into the headset mic. The only real solution, short of turning the volume down, is to use something else, a better headset, or a proper mic and headphones.
audio_jungle wrote:If I am recording from Firefox and my USB headset, if there any problem having "Mute audio sources" UNCHECKED so that I can monitor my recording as it happens?
This is fine. As stated above, how you choose to monitor is up to you. If you don't wish to use (or can't use) Audacity to monitor, then use Loopback in that manner. I thought I had made that point fairly clear. All I said was to be sure not to do *both* at the same time.
audio_jungle wrote:That doesn't seem to cause any issues, although you recommend leaving it checked.
Recommended because I would be monitoring through my DAW/recorder, but as this seems to be giving you problems, so do it the other way. It's fine, as already said, do it whichever way makes sense for you. Now you have an understanding of what these features do, you can make informed decisions about how to use them. :thumbup:
audio_jungle wrote:And, yes, I do expect companies to create documentation that your grandmother could read and understand the first time. (It all comes down to pride in work...)
I'm not doubting your experience, I just have a hard time associating some of your comments with Rogue Ameoba, who are one of the high end of Mac software utility/app developers who do work really hard and really care, and have been making excellent software for many years, and who I've had some relationship with for a long time.
Their documentation is also really accessible and nicely written, compared to the vast majority of software. There is a four step Quick Start, and a full manual, which is really nicely written, and *should* give you everything you need to make Loopback work, but is not a general tutorial on everything audio and people can often have complex system requirements which require some system design and troubleshooting that is well outside the scope of a tutorial/ reference manual. Obviously it's not working for you for some reason, but everyone is different, and it's hard to please everyone 100%.
Damn, my tea's one cold *again*... :beamup: