Mac M1, latest version of OS and Live.
The Hardware Latency setting in the devices is making the latency longer, not shorter. I did the same as this Ableton instructor https://youtu.be/2ONL4ZWgy7E?t=308 but am not having the same result.
One MIDI track has an external instrument or fx control (I've tried both). One Audio track taking sound from Pre or Post FX in the MIDI track. Delay Compensation on. Did the Delay Compensation exercise and have it locked on to be visually, well zoomed in, sample accurate.
I press Play and then try to record a clip in the Audio track.
First I measured 14 ms latency for a Roland TR-08 over USB audio, whether synced by MOTU MIDI out, an Expert Sleepers USAMO, or Roland SBX-1.
However, setting 14 ms Hardware Delay in either an External Instrument or External FX control and then recording doesn't change anything. It records in the same incorrect spot, 14 ms forward from zero.
However if I move the delay time in the MIDI track back to zero from 14 ms, while playing, the recording lines up on the grid while it's playing/recording.
If I stop audio and try to record another clip with the 14 ms delay setting, 14 ms is then added instead of removed. That is the opposite of how it’s supposed to work. Increasing the Hardware delay time is supposed to pull the test signal back in time, not push it forward.
What could be going on here?
External Instrument/FX Hardware Latency Delay working opposite of how it should
Re: External Instrument/FX Hardware Latency Delay working opposite of how it should
I learned that Live doesn't delay compensate MIDI clocks or MIDI delay in its overall PDC calculation!
Someone created a Max device that seems to be doing the job, called "Clock". https://nukemodular.gumroad.com/l/qjpEU
I'm still testing it out but so far seems to work.
It's fine for the Boutiques over USB MIDI but even tighter when I send clocks from the Max device to the SBX-1: sub-1ms jitter from the TR08/09.
Someone created a Max device that seems to be doing the job, called "Clock". https://nukemodular.gumroad.com/l/qjpEU
I'm still testing it out but so far seems to work.
It's fine for the Boutiques over USB MIDI but even tighter when I send clocks from the Max device to the SBX-1: sub-1ms jitter from the TR08/09.
Re: External Instrument/FX Hardware Latency Delay working opposite of how it should
I had Chat GPT write a rap about the issue. Couldn't help but share:
(Verse 1)
I like tight clocks and I cannot lie
Syncing beats so precise, you can't deny
From the TR-08 to the TR-09
Even the TR-06 keeps the rhythm fine
TR-8S, 808, and the 909
Casio RZ-1, we got them online
When it comes to drum machines, we stay on top
MIDI sync on point, we never drop
(Chorus)
I like tight clocks and I cannot lie
Drum machines in sync, no need to ask why
Ableton Live, you're lagging behind
Clocking issues, you can't define
(Verse 2)
MIDI sync, the heartbeat of our groove
Clocking them tight, we make the crowd move
But Ableton Live, oh, what a shame
Your clocking skills ain't in the same game
No MIDI Clock Delay, no compensation
Your plugin delay leaves us in frustration
We need precision, we need it right
But Ableton Live, you're causing a fight
(Chorus)
I like tight clocks and I cannot lie
Drum machines in sync, no need to ask why
Ableton Live, you're lagging behind
Clocking issues, you can't define
(Bridge)
Give us the beats, give us the groove
MIDI sync tightly, that's what we approve
TR-08, TR-09, they never miss a beat
But Ableton Live, you're incomplete
(Verse 3)
So let's step it up, let's find a way
To sync our machines, no delays, okay?
We'll explore alternatives, find what's right
For our tight clocks, we'll fight the fight
But for now, let's groove with the drums
TR-06, TR-8S, they're the ones
Clocking in sync, keeping us on track
While Ableton Live, you're holding us back
(Chorus)
I like tight clocks and I cannot lie
Drum machines in sync, no need to ask why
Ableton Live, you're lagging behind
Clocking issues, you can't define
(Outro)
So remember, folks, when it's time to rock
Choose the machines that sync on the dot
TR-08, TR-09, and the rest
Tight clocks are what we love best!
(Verse 1)
I like tight clocks and I cannot lie
Syncing beats so precise, you can't deny
From the TR-08 to the TR-09
Even the TR-06 keeps the rhythm fine
TR-8S, 808, and the 909
Casio RZ-1, we got them online
When it comes to drum machines, we stay on top
MIDI sync on point, we never drop
(Chorus)
I like tight clocks and I cannot lie
Drum machines in sync, no need to ask why
Ableton Live, you're lagging behind
Clocking issues, you can't define
(Verse 2)
MIDI sync, the heartbeat of our groove
Clocking them tight, we make the crowd move
But Ableton Live, oh, what a shame
Your clocking skills ain't in the same game
No MIDI Clock Delay, no compensation
Your plugin delay leaves us in frustration
We need precision, we need it right
But Ableton Live, you're causing a fight
(Chorus)
I like tight clocks and I cannot lie
Drum machines in sync, no need to ask why
Ableton Live, you're lagging behind
Clocking issues, you can't define
(Bridge)
Give us the beats, give us the groove
MIDI sync tightly, that's what we approve
TR-08, TR-09, they never miss a beat
But Ableton Live, you're incomplete
(Verse 3)
So let's step it up, let's find a way
To sync our machines, no delays, okay?
We'll explore alternatives, find what's right
For our tight clocks, we'll fight the fight
But for now, let's groove with the drums
TR-06, TR-8S, they're the ones
Clocking in sync, keeping us on track
While Ableton Live, you're holding us back
(Chorus)
I like tight clocks and I cannot lie
Drum machines in sync, no need to ask why
Ableton Live, you're lagging behind
Clocking issues, you can't define
(Outro)
So remember, folks, when it's time to rock
Choose the machines that sync on the dot
TR-08, TR-09, and the rest
Tight clocks are what we love best!
Re: External Instrument/FX Hardware Latency Delay working opposite of how it should
For anyone interested -
The solution is that the input and output audio devices must be the same device, otherwise you get varying amounts of latency. Aggregate audio is the solution here, not the problem, so long as you pick the exact same aggregate device for both input and output.
If you use different devices for input and output, every time you reload the audio engine you'll get a different amount of driver error and the sound will land in a different spot on the grid.
The solution is that the input and output audio devices must be the same device, otherwise you get varying amounts of latency. Aggregate audio is the solution here, not the problem, so long as you pick the exact same aggregate device for both input and output.
If you use different devices for input and output, every time you reload the audio engine you'll get a different amount of driver error and the sound will land in a different spot on the grid.