Hello, I’m trying to sync my Hapax with Logic Pro. I’d like to use the method described in the manual: Share Audio synchronization from a DAW: enable sample-rate precision. While this works perfectly with Ableton Live, I can’t get it to work properly with Logic Pro, especially when I want to change the tempo. Is it even worth trying to get it working? Has anyone succeeded? I get the impression that Logic struggles with controlling external hardware and properly handling plugin delay compensation.
audio is audio, a sample player playing a square wave sample should have none or almost no latency.. i have gotten this method working in various software so no reason it shouldnt work in logic [audio]
Yes it works in Logic Pro with the sample provided in the instruction, but only with the tempo at 120bpm. If I change the tempo in Logic, the sync is lost unlike in Ableton (with warp in repitch mode) where sync is tight
You could try using a dedicated plugin to generate the audio pulse instead of a looped sample - I use the Midronome VST found here which I originally had running to send a signal to a Midronome. Once I got the Hapax with its CV in sync, the Midronome became redundant.
Works great for me
the signal output level needs to be close to maximum for it to work well and your audio device needs to be dc coupled
also, the cv clock sent by logic will not change the internal tempo of hapax. you are only starting the next division of time in hapax. hapax is still performing the sequence at internal tempo, and your clock pulse simply starts the next slice according to the receiving rate set in hapax settings. if you want all potential events to be realized, hapax has to bet set to the same tempo internally as logic. either that or dont place midi in hapax piano roll at over 64th note resolution, assuming youre receiving cv cock at 64 pulses per measure.
i don’t use CV so there maybe workarounds as an incoming audio signal but as a general rule Logic hasn’t been able to receive incoming sync (at least MIDI Clock) for several versions now. which may be why it’s also rebelling against CV?
one of those midi sync distrobution devices like mentioned earlier is probably a good buy for your setup. if you cant get cv clock working that is. although they use the same mechanism done the same way.
given a stable midi clock, hapax plays very well. also midi clock from hapax is pretty solid even if im clocking hapax with cv from reaper or live. its the best ive experienced honestly.
confirm the audio from logic is coming from a dc coupled audio device. it may not be. also try turning up levels to hapax. even clipping since its only a square wave. it wont hurt your sound device.
My audio interface has a dedicated clock output (Arturia AudioFuse 16Rig). In Logic Pro I open the sync settings and set the clock to the 16Rig clock output. This works real well but I wish I could still control the Hapax sequencer playback when set to sync to analog in
I’m getting good results with the Midronome plugin (thanks to Martino for the tip 
) as a VST directly on a dedicated output of my Apollo X6. I can also adjust the delay on the MIDI track in Logic to compensate for external latency. I tried something similar with the ERM Multiclock plugin, but strangely enough, no good results.
1 Like
What’s crazy is that I can’t get the MIDI coming from the Hapax (for example, a note every beat to drive a VST Drum synth) to sync in Logic, while the audio from synths sequenced by the Hapax is recorded in Logic perfectly in sync. The same setup with Ableton Live controlling the Hapax gives both audio AND Midi in sync
Do you have any plug ins open in this session? If yes, this is your Problem! Logic is a great shitshow with external gear if you have plug ins open in the session. It´s the Latency Compensation. Try Low Latenty Mode. If this fixes it, you know that´s your Problem… Live does a much better job in this regard. I´m suffering with this Problems since years in Logic… 
I’ve used with the erm multi plugin and alm’s plugin both work into the hapax CV in..
Im working on this aswell but on an ipad and with cubasis. I just orderd a motu ultralight mk5 AVG. I hope that one has dc coupled outputs just like the standard mk5. Just checked and it is lucky me 
That means i can use it for sending a bunch of cv signals aswell. Wow i hadent plan on this i just wanted a cheap food soundcard (second hand unit)
Peace
Hi! Unfortunately, the new 3.0 firmware is causing a cv sync problem for me. I use Logic Pro (macOS) and Midronome plugin. Reverting to version 2.21 works perfectly.
Also having same issues as @bert_pauze with v3.0 firmware + CV sync not working with Midronome plugin.
The Hapax transport appears to start/stop rapidly - are there any specific settings to troubleshoot?
It was working nicely on the old firmware.
make sure to report the issue
1 Like
Thanks - done!
sure you don’t have CV RUN setting enabled? that start/stops it rapidly. See manual Hapax Manual | Squarp instruments
In any case, I cant seem to get proper sync either with the midronome sync gen plugin and hapax set to 24ppqn
Not sure about previous firmware as its the first time I try it (running 3.0)
audio interface is the audient evo 16.. IIRC it is DC coupled, although I don’t see this as a requirement anywhere?
i had to set the hapax CV IN RANGE to -1V/+1V for the hapax to respond. the progress lights on the step sequencer behave very irregular. Both set to 120BPM
I’ll need to verify my settings, but my existing CV sync settings were working flawlessly on previous firmware versions - reverting back from v3.0 had it working nicely again
I submitted a bug report and Jean @ Squarp replied back as below
In summary - seems like some kind of glitch with using the Midronome plugin specifically. I don’t have time to spend on unnecessary troubleshooting so will just stick with the old firmware for now.
–
I’ve just tested 3.00 with Ableton and with this procedure https://squarp.net/hapax/manual/modesettings/#UUs4wZ8
Everything is working fine on my side.
Note :
– I use the CV IN RANGE = -1V +1V
– I need to set on the Ableton audio file WARP = REPITCH
– It’s also important to set the same BPM on Hapax and the DAW
– Maybe try to use a lower CLOCK DIV rate