Of course, you can either set an offset so that your gear is in sync on the output of your mixer, or so that it's exactly in sync when you record it into your DAW. But your ERM Multiclock can do that instead, so you actually can get around this problem. The only problem by now is that you can't set an offset for Clock signals on Push itself, in order to compensate the latency. I don't know for sure, but it seems there's no conversion happening at the CV output, so that's why you have a difference.īut again, this is NOT a bug or a faulty hardware, every audio interface does produce a latency because of its converters. The rest is due to the DA conversion of Push's audio interface. The 707 Core Kit contains a few audio effect devices in its return track, this may produce some of the the latency. So there's definitely around 7 ms of latency compared to the CV out. I noticed that there is 3 ms of silence at the beginning of the kick drum sample (this is probably the 3 ms of difference in your DAW test).

Yesterday I did a test again with Push, this time with the 707 Core Kit and I had exactly the same latency of 10 ms as in your test. thats why some users uses ERM Multiclock.

I will do the Test when the USB Hub is disconnected later the Day.Īlso a Fact is that my Sequencers that are slaved to ERM that receives the clock from Push are at least 10-13ms to early.Īnd all other devices like Akai Force and my Ableton DAW are using the same 24PPQN via ERM Multiclock to sync with my hardware dont have that negaitive latency. The only thing that could be different from yours is that i have connected a USB hub with two MIO XLs, but they are not assigned in this project I can also do it with CV Tools clock later the day. Not synced with Push no sync at all.īefore i posted this I did the same Test with Ableton from DAW there is nearly no Latency between Corekit 707 and the Pulse signal.īut i used the ERM Multiclock plugin in this test. No Latency adjust.īoth tracks are recorded in a plain project in Ableton on my DAW. This is connected to my RME Raydat PCIe via ADAT. Track two Corekit 707 ( no other Plugins ! )īoth Tracks are connected to a Behringer X32. CV Tools CLock 24PPQN Trigger CV1 out ( nothing else !)Ģ. You'd have the same problem with MIDI Sync, even if you were able to offset the Clock signal.ġ. You'll have to manually cut it out or nudge the WAV file, so that the beat is on grid and in sync again. When you zoom in to the beginning of the recorded WAV file, there's probably a few milliseconds of silence before the first downbeat. But the latency that you hear, when you playback a recorded drum beat, derives from the input latency during the recording process. You're able to compensate the output latency on the ERM Multiclock, as you already do with the -14 ms, so this is the right way to go. Your case is kinda same, but a bit different, because you're sending an analog signal here, not a MIDI Clock.

It's possible in the Ableton Live software, but not on Push Standalone yet. To get around this, you have to offset the MIDI Clock in order to compensate that latency. Like any other audio interface, Push's built-in interface causes a latency, this is normal due to technical reasons. It's maybe not a bug, but definitely a missing feature. Well, in the video they're talking about MIDI Clock issues and that there's no possibility on Push to adjust an offset for it, in order to get other gear perfectly in sync.

Erm multiclock ableton shonky