I can only test with Built-in Audio for older projects that were recorded at 44.1 KHz due to internal audio maxing out at 48KHz. But, I can give that a shot and report back later.Michael Canavan wrote: ↑Sat Dec 21, 2024 11:47 pm
Ugh, this could be it right here, Rogue Ameba the makers of Audio Hijack among other Mac OS audio tools said they were excited about changes to Sequoia that were of benefit to their apps. So most likely the Focusrite interfaces if they're more than a few in/outs do have a driver that installed with the app. Mac OS has been doing a "driverkit" driver that you can read about on RME's site if you want, it's removing drivers and audio interfaces further from the kernel.
So that's the obvious test, run your projects from the built in audio and see if they skip when listening from the headphone out.
I just checked the Focusrite site again. They only have drivers for Windows. I don't need or use Focusrite Control for my mixing room Scarlett interface, because it's essentially just a hardware dongle for the higher sampling rates and a convenient volume knob. I don't see anything about Sequoia incompatibility in their specs or "Help Centre," other than some other unrelated issues.
I do have SoundSource installed. It allows the user to set audio levels, routing, and custom EQs for every app. I could try disabling that. I can report back on that later, too.
I watched the RME video on audio extension. https://rme-audio.de/driverkit-vs-kernel-extension.html Looks like Ventura was the most current OS when it was produced. Good info about starting a M1 (etc) Mac in Recovery Mode of which I was unaware (Shut down, wait, hold power button until Recovery screen appears).