Can anyone ID this audio artifact?

The Lounge Other Gear
1

Hi, I’m having an issue with my computer/interface and trying to troubleshoot the issue. I have some pretty aggressive settings on my interface in order to achieve minimal latency in my system (M2 MacBook Pro, Apollo X8 @ 96khz 64 sample buffer). Still, I believe my equipment should definitely be able to handle this. I have no problems at 48k

Things sound pretty good as long as transport isn’t running. I can play Kontakt instruments and other VSTi’s and for the most part they work fine. However, the second I hit play in a DAW (tested in Ableton and Cubase) I get this kind of repetitive clicking artifact. This happens even if the project is completely empty. My first instinct was that it was CPU related so I’ve tried turning a bunch of things off, closing, apps, etc. But it remains.

Again, this problem goes away at 48k.

Anyway, I thought maybe the nature of the artifact might help point to the issue. Here’s a little recording of it. The first part is me playing a couple notes on a Kontakt instrument. Then, I press play in Ableton and play the same notes again and the artifacts begin.

Does this sound like a specific kind of issue to anyone?

2

I assume you’ve tried different Buffer Sizes (lower AND higher ones) already?

1 Like
3

Yes make the buffer larger at 96k, try 128.

1 Like
4

Check the clock settings on your interface, could be a mismatch – e.g if your system is set to 48kHz and your interface to 96kHz but it’s set to use an external clock (probably your system’s clock in this case)

(to clarify, make sure it’s set to use its internal clock)

2 Likes
5

Thanks all. Interface and DAW are indeed at the same sample rate, with the UAD Console displaying its clock as ‘internal’. I’ve tried rebooting and restarting both Console and the DAW.

At 96khz, I still get artifacts at a 128 buffer (less severe, still unusable though). I have to bring it up to 256 before the artifacts stop. But at that point the RTL is greater than what I can get at 48k + 32 buffer, which I can run without issue.

I guess I’m kind of surprised (read: in disbelief) that I would be hitting the performance ceiling so quickly, given the apparent power of the M2 Pro. I have the 12-core chip (8P+4E). Would really love to shave off a couple more milliseconds off of RTL though!

The reason why: I have my Octatrack connected to the interface. I play virtual instruments and other stuff from the computer into the OT, which I want to use as a real time sampler/looper/jammer/remixer. The interface acts as a digital mixer: the hub and monitoring center for everything. However, I’m often NOT using the sequencer at all so I can’t just use clock sync to keep everything aligned. But I need to keep timing tight between all sources so that I can record in time from the computer to the Octatrack, alongside things that are already playing in the Octatrack. I’ve noticed that with even slightly higher latency, timing start to feel off when I play stuff back on the OT.

So, the latency to and from the DAW isn’t actually that important for my purposes, strictly speaking… rather it’s the latency through the Apollo’s internal Console mixer. And according to folks at UA, the internal Console mixer runs more than twice as fast at 96k vs 48k.

So, still hoping to find some magic setting to make 96/32 work! :crossed_fingers:

Most ‘system optimization’ articles I’ve read are pretty generic and honestly a bit impractical too (turn off iCloud, Dropbox, Time Machine, wifi, bluetooth, safari, anything else that makes your computer useful haha). Still, I’ve tried the suggestions and had no luck!

6

PS as I’m investigating alternatives, does anyone know if RME’s TotalMix FX (the internal mixer, equivalent to UA’s Console) runs at different latencies depending on sample rate?

7

Mac Mini M2 Pro here, no issues at 96kHz and lower buffer sizes (32 or 64 samples) at all. I don’t have any UAD interfaces to test with however.

Mismatched rates could lead to this sort of issue, have you changed your Mac’s audio settings to match the 96kHz? If not give that a try as well, just in case.

1 Like
8

Appreciate the feedback! And thanks for the idea about system settings. Looks like the Apollo was changing the setting in AudioMIDI Setup automatically. Still, I changed all other non-active devices to 96khz but same artifacts…

Do you mind if I ask what interface you use? Wondering if this might just be a driver issue…

9

Darn, well it was worth a shot at least!

I’ve used both Audient’s (EVO16) and DigiGrid’s (IOX) interfaces with this system, and haven’t had any issues with either option. One is connected with USB and the other with Ethernet.

1 Like
10

By the way have you tried using higher sample RATES as well?

The Apollo can do 192kHz as well, right? Give that a go. Found some older posts of people having issues with 96kHz with Apollos on Gearspace.

11

Good thought! Weird result though: for some reason no sound at all makes it to the Apollo when I select 176kh or 192khz in Ableton. I see the meters moving in Ableton but no signals at all in Console.

12

Another interesting twist: I just tried running Logic 11 and I experience no artifacts running at 96 / 64!

1 Like
13

Ok, culprit found!! Turns out my metering plugin (Youlean Loudness Meter 2) was causing the issue. I have it loaded in my default project in both Ableton and Cubase, but not in Logic. The plugin only works when transport is running. As soon as I disabled it, the glitches stopped. Phew!!

4 Likes