I’ve started having an issue on my A machine where jumping between locators as AbleSet 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. AbleSet’s drift correction does a good job at nudging the B machine backwards to match A, but after it aligns itself the first time, it won’t trigger again. 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 SE’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 AbleSet: 2.7.5
Version of Ableton Live: 12.2.1
Networking info if needed:
- Playback to ExBox.MD via Dante Virtual Soundcard
- There’s Dante, RTP, and dLive control on the same network
- All devices on the network are static IPs in 192.168.1.X range
