The Hapax is synced to my Daw via the Ableton CV Clock plugin. Works great.
But when I stop the DAW Hapax transport is still locked to external sync. I have to go in to the Hapax settings and manually release the Hapax. But I don’t need to have it synced all the time when writing
I take it there is no auto release on stop and it switches to internal clock
Am I missing something?
Not sure
Cant your sync plugin send clock when ableton transport is stopped?
also amazing that it works for you, as people report its broken recently Hapax CV In sync with Logic Pro - #30 by martino
The plugin doesn’t send clock when the Daw is stopped and that’s exactly how you want it. But that’s not the issue.
The problem is when syncing the Hapax to a DAW via CV clock, stopping the DAW does not release the Hapax transport. This works correctly with MIDI clock sync, but not with CV Sync.
This forces users to manually disable sync in settings which is very cumbersome because often we only need the DAW for occasional audio (vocals, orchestra libraries, etc.) and don’t need it running constantly, especially in the early stages of a writing a track.
It’s a significant workflow issue for CV syncing and im rather mystified why this isn’t a feature in the Hapax after all this time since release. I surely cant be the only user syncing their Hapax to a Daw via CV
In regards the Logic problem, that will be the plugin or the audio file squarp link to. That audio file barely works. Squarp should not be linking to it or recommending it and not suggesting people warp the sync audio file it for different Tempos because even in Ableton I never got that audio file to work properly, even once. Far better to suggest using a plugin of which I believe there are quite a few out there
Hey Squarp
Ill put in a feature request for this but Im hoping its not a massive coding job - unlike adding 8 new drum lanes which I think took about 2 years of heavy duty coding 
I queried Ai about this:
Are you saying the transport is released when I stop the Daw (synced via Abletons CV clock plugin)
No, that’s not what I’m saying.The transport is not automatically released when you stop the DAW using the Ableton CV Clock plugin. That’s exactly the issue you described.What the manual mentions (CV RESET = AUTO) only does a position reset after ~2 seconds of no clock pulses. It doesn’t fully release the transport the way MIDI clock sync does — Hapax stays “locked” in external sync mode, which is why you have to manually disable sync every time. Adding proper automatic transport release on CV clock stop would be a useful improvement. It’s currently inconsistent with MIDI clock behavior.
Would this be a complex and time consuming thing for Squarp to code?
No, it shouldn’t be complex or very time-consuming for Squarp.Here’s a realistic breakdown:
Core logic: They already detect when the CV clock signal stops (they use this for the existing CV RESET = AUTO feature that resets after ~2 seconds). Extending that to also release the transport is a small addition to the same code path.
Effort level: For their firmware team, this is probably half a day to 2 days of work including testing different scenarios (different clock rates, dropouts, Ableton plugin quirks, etc.).
It’s not a deep architectural change — it’s more of a “make CV behave like MIDI clock in this specific case” fix.
This kind of sync polish is something Squarp has done before in updates, and they seem to care about clock/sync reliability.Bottom line: It’s a relatively small, high-value change. Definitely worth requesting.
haha don’t believe everything AI hallucinates, might as well ask a fantasy novel writer for his opinion.
In any case, email squarp with your request, they are very responsive to decently formulated issues.
I agree the audio file solution is sub par. In my case it wasn’t working correctly with a plugin either though.
cant you just press stop then?
last time i was testing this - iirc - i had to still set the tempo on the hapax, and therefore i think i was able to do start/stop regardless of incoming cv
When using CV clock the transport of the Hapax isn’t released when I stop the Daw which means hitting play on the Hapax results in it not playing.
If I were using midi clock it works fine ie Hapax transport is released when I stop the Daw allowing me to play the Hapax from its own clock without having to go in to settings and deactive external sync. In the midi clock scenario the Hapax automatically switches to internal clock when stopping the Daw. This is the correct behaviour and what I want for the external CV clock sync
Try syncing your Hapax with a Daw via CV clock and you will understand instantly what I mean. Then sync it via midi clock and you will notice the Hapax transport is released when you hit stop on the daw.
Im not requesting an esoteric feature only I need. Its very much the standard behaviour of most modern sequencers/drum machines.
last time i was testing this - iirc - i had to still set the tempo on the hapax, and therefore i think i was able to do start/stop regardless of incoming cv
Im not sure about that. But this is why I posted, wondering if I am missing something. Ive tried every setting I could many times.
this is a job for
$149
£119
The hapax supports audiosync, why buy something inferior that syncs at lower ppqn?
why ask why? it could serve you outside of use with hapax. i understand your position. you dont need to buy anything but if its that important, here is a solution. perhaps hapax will cover the need you have in a future release. is it ok if i give info that im aware of to attempt to remedy your issue? btw expert sleepers stuff is NOT inferior, they are pioneers in the area of sample accurate midi from daw. im a big fan! good luck with your request, im interested in it as well. i dont have a usamo. they arent so expensive and im sure youll agree that something that does what it does could be useful in a variety of situations!
i’m not saying expert sleepers is inferior, i’m saying the solution is inferior compared to a direct sync in hapax at a much higher ppqn.
i have no reason to doubt expert sleepers being good at what they do, but it’s a totally different beast.
so you started your comment with "this is a job for.. ".. it isn’t. very misleading to whoever might be reading this.
i disagree. however, if you cant wait, this is a job for a $150 solution that will come in handy in other situations potentially. i didnt mean to arouse your anger tho mate! chill. and to you who are confused reading my post, its not the solution the OP was looking for. if there was any confusion. i personally wouldnt be confused 
edit: midi sync includes transport commands and controls the internal tempo of hapax as well as eliminating the faff required to set up audio sync. so it could be seen as SUPERIOR solution currently. know what im sayin mate
Just tested this (it was on my “todo” the continue investigating this workflow - I had it all hooked up and configured a couple of weeks ago but go demotivated because it didnt work)
You are right, its frozen when clock stops, doesn’t revert to internal tempo.
For MIDI source, there’s an AUTO setting that reverts to internal clock, but it doesn’t do anything when syncing to CV.. Sad, this is a very valid feature request imho..
As a workaround, I had made an (unreleased) plugin in the past that did dinsync, it always sends clock, as it’s an “audio unit generator”. But when transport starts, it sends run signal on another output, which could be connected to CV 2 to start/stop the hapax (from what I see in config, this is possible).
I know, not the answer you wanted. But I think I’ll try that soon, still have a spare output on my soundcard. Will post back here with my results.
BTW: I got it to work with the audio file from Squarp, dunno why it didn’t work the first time. Though I just used it as-is (no tempo change). Looking at the wave file I’m not really impressed
I’m wrong.. I was expecting high clock rates, like 192 ppqn (internal clock rate of hapax iirc?), but no, it’s max rate it 24ppqn. Which is just normal midi rate. So yeah USAMO or other tight clocks are “just as good”
They say “Hapax is synchronized in a “step advance” trigger style (old school analog clocking).”.. Hmm..
No it isnt
it is if you gotta have it right now.
Using USAMO or any other sync box would replace the Hapax Cv Sync feature with midi clock which is fine, but not always because using USAMO in Ableton live results in the sync being lost when you solo a track and in my Xp it was unstable(ish). 20+ years later Ableton still refuse to add in safe solo. yes, an FX return is auto safe solo but I couldnt get the plugin to ever work from an aux return. Mind you it was years ago since I used USAMo so maybe things have changed there.
.
Anyway, the Hapax has built in CV clock sync and is a feature Squarp talk about in their Hapax blurb ‘no more sync boxes’.
There are two issues
I found a workaround to reset patterns on stop - send midi clock to the Hapax (its still being synced via Cv clock) but it fortunately still receives the midi/pattern reset message so when stopping and starting the Daw teh Hapax patterns launch from the beginning rather than resuming from where it was stopped.
They will implement this in this in the next update 
i knew it would be a matter of time before this feature fix was in, i was only offering an alternative that my friends use. like i said i would like it to be fixed as well.
oh yeah and reaper can exclude a track from mute/solo and lock the controls so you wouldnt have a problem running a single pulse sample as often as you like or an expert sleepers plugin or what have you. then you could run midisketch or redux or whatever with full midi control from hapax. redux could send midi out to serum2 or whatevs you got.
but doesnt live have cv tools? must they run on a track or can you not lock a track somehow?
but! maybe this helps?
Amazing that Ableton since inception 25 years ago has never implemented safe solo.A feature that was available on mixing consoles from the 70’s because its super useful - just not useful to Abletons prime directive A prime directive which is still in force at Ableton ’ We will not implement a feature if any other Daw has it’
Although today its more like we are reluctantly forced to implement some stuff other Daws have but we will do it in our own way and it will be convoluted..
Thanks, I will check it out
A fix for release of the transport is coming soon I beleive