Ableton 11 Mac M1 drifting clock

Hi, I recently got a MacBook Air with m1 chip with Ableton live 11.
I discovered a strange behaviour when setting the driver error compensation. If I do the usual procedure of sending audio into one of the inputs of my sound interface and recording it back in, it seems like the latency is getting bigger and bigger. I am seeing his by setting a loop in Ableton and letting the recording run. This is especially annoying when I try to record some hardware synths as the same drifting problem happens.

At first I thought my sound card was the issue as it is a pretty old Behringer one but I tried with a brand new Focuscrite one and the issue is still there. I am starting to think that the fact that Ableton is running on top if Rosetta could be the issue.

Did anyone else come across this issue / has any clue how to fix it ?

Hey thanks for your reply !
It could be yes, will write them a report. I should also mention I did the same experiment with Live 10 and had the exact same behaviour :frowning:

How long does it take for the clock to drift? I have not noticed anything, and I record a DFAM clocked using the audio outs.

gear: mbp m1, Ableton 11, ultralite mk5

…ableton already silicon optimized…?
…no to brag, but bitwig is all ready for m1 and what’s next to follow, coming from cuppertino…

whatsoever…rosseta should also not gain in latency during play…
ableton will fix this soonish anyways…no worries…

It is not. But for me this is not a really problem so far.

It drifts off pretty much directly. I am just setting up a one bar loop in Ableton with a sample on the 1 beat and the recorded audio never falls on the same spot

No it is still running on top of Rosetta. And yes I tried Bitwig and it is much more stable ! Definitely thinking of moving completely there too as there seems to be some really nice features :slight_smile:

I really cannot reproduce this. It stays stable for at least 10 minutes.
I only have issues when adding some effects/vsts with a small buffer. But the audio glitches too.
I’m always using external effect or external instruments by the way.

Hmm alright, thank you for checking out though !
Could also be that something went wrong with my rosetta installation although surely its installed properly as it’s running Ableton in the first place :man_shrugging:

Why do you think it’s because of rosetta? It’s sounds more like a driver issue and potentially user error (not to blame you, I think this area is really badly explained and very hard to setup correctly)
Btw, I’m only using an aggregated sound card (with my tr6s) with the drift correction activated.
I don’t know if it makes a difference though.

No particular reason just figured that fact that it’s emulated could cause this issue but you’re right could absolutely be a driver or setup issue !
Hmm yeah could be, but I don’t seem to have any kind of setting like that in my sound card configuration though !
Which sample rate/ buffer size are you using ?
Somehow at 44.1KHz it doesn’t happen all time while it’s consistently reproducible at 48kHz…

It’s on macOs, when you create an aggregate device. But I would not recommend it, this usually causes more problems.

I’m using 48khz, 256 buffer size.

Did you try using the “External Audio Effect” device ? I don’t really understand what you are trying to achieve. Maybe upload your project or post a screenshot

Oh, I just saw that. Why are you setting this? Your driver should report it correctly already in most cases.
It is the case with my Focusrite and my MOTU. It’s really exact and everything is perfectly aligned to the grid.
If you send audio and record it, make sure you don’t monitor the track.
I enable “Delay Compensation” and disable “Reduced Latency When Monitoring”.