I’m running Ableton on 2 Macs. Mac2 sends out audio clock sync from an audio track (plus another for start/stop), to an audio interface, into the audio interface of Mac1. Then ‘CV Clock In’ tool is used in Ableton on Mac1, which starts the Transport and sets the BPM, and of course keeps every thing in sync.
It works fine… except for one thing.
On Mac2, I’ll set the BPM to say 84BPM, and Mac1 will show something like 84.03BPM.
Everything stays in sync (it’s mostly just for clocking time-based FX etc).
Except, when I do a Beat Repeat on one of the tracks on Mac1, and lock the Repeat button so it stays repeating a small section, then eventually the Beat Repeat slips out of time (due to the tiny BPM difference I think).
That is likely due to a rather insignificant amount of jitter. A clock displaying a .03 delta in timing should be disregarded. It’s not likely the cause of your issue.
Is it possible to have this, and any other timing sensitive/time-based effects tracks, hosted on Mac2 where the master clock is?
Agreed! My ears can tell it’s going out of time though!
I’m using audio-syncing because it’s tighter, and far less jitter. The best way to sync!
I think I might have an idea… put a little trigger to stop and start the clock every 16 bars or so. Might be seamless if its only a sample or two apart from each other.
How long does it take before this drift is noticeable? How long are you hoping to hold the buffer for?
It’s not a device that I use but I wonder if its intended use isn’t for indefinite looping. It could be a fundamental timing inconsistency with the device itself that otherwise wouldn’t be noticeable during momentary/short term use.
…u’ll find me even surprised, to hear u just end up with such a small amount of jitter…
even with most rocksolid midi clock solutions, any tempo displayed on the synced/hooked up end will show u some constantly changing count of bpm, sometimes even up to one full bpm…
which is usually still no big deal in final listening results…
if u sync up via audio, it should be even get a little worse…especially when it comes to realtime jam activation of stutter like beat repeats…
only way around that…all micro timing relevant elements of ur arrangement must happen in one place…so either mac1 OR mac2 it is…leave all the rest to the other one…
usually u better pick the master machine for all the most timing relevant stuff…
oh, and if u put any beat repeat stuff on the hard test to let it repeat short parts to eternity, if will always fail u at some point, at least in overall musical impression, even if it’s supertight in naked reality…
It does take a while. Like if I’m looping a small section of a track for 32 bars or more the drift gets noticeable.
I don’t think (will test more tomorrow) it happens on Mac2. Will report back…
Very little jitter with audio-syncing, I’ve tested this quite extensively!
Doesn’t exist in my experience! Definitely makes no sense sending clock down the same cable as notes and CC’s etc. Better for clock to have a dedicated cable!
My system is mostly setup like this. Mac1 is basically a sound-module. This particular beat-repeat has to be on Mac1 though, to enable the track filter to go post beat-repeat, and to enable that track filter to be individually by-passable by individual samples.
Not sure what this means tbh! I just want it not to drift out over 32 bars!