I use redundant Ableton Sessions for live playback, running multitracks to Dante Virtual Soundcard, multiple RTP MIDI networks, and MIDI out through the IAC bus.
I’ve started having an issue on my A machine where jumping between locators (as setlist management software runs) causes the A machine to fall behind the B machine, alongside a decent CPU spike (sits stable at 4-5% during playback, jumps up to 45-50% when jumping between locators). I can’t seem to find a fix since it’s started happening. I’m quite sure it’s on the Ableton/MacBook side, as the issue happens with AbleSet Controller (via a midi controller to both machines), AbleNet, and Strange Electronic's SetList device. Each time it jumps to the next song, the drift gets worse.
Has anyone had a similar issue? Both Machines run at 128 buffer and both have Dante Virtual Soundcard as their Output device, no input device. Machine A is in theory, a lot slower than Machine B (specs below), however they have both been running a similar session for a year’s worth of touring now and this issue is recent. They both sit under 5% CPU during actual playback as well. I can’t imagine just jumping around the transport is causing that much of a CPU spike to push the machines out of sync, right?
If anyone’s seen a similar problem or has any ideas on a solution let me know!
OS and Version:
Laptop A: MacBook Pro M1, 8Gb | Sequoia 15.5 | Only has playback software/files
Laptop B: MacBook M4 Pro, 48Gb | Sequoia 15.5 | Doubles as personal machine
Version of Ableton Live: 12.2.1
PLAYBACK: Jumping locators causing delay/latency
Re: PLAYBACK: Jumping locators causing delay/latency
Since you said it started recently, supposing your setup didn't change we might want to consider Live updates.
And there was actually a fix related to CPU spikes when jumping between Locators recently in L12.2... it's not impossible that this created an unnoticed new issue.
You're probably better off contacting Support.
And there was actually a fix related to CPU spikes when jumping between Locators recently in L12.2... it's not impossible that this created an unnoticed new issue.
You're probably better off contacting Support.
Ableton Forum Moderator