Starting a fresh thread from here as my issue seems to be seperate but related from the discussion in the other clock thread.
I run Fender Studio Pro as my DAW, sending a clock to my Hapax CV1 input via @rv0’s clock plugin. Everything had been very tight up until I experienced wierd clock/transport issues on the Hapax when v3.0 came out. After lots of wasted time troubleshooting and then reading the above thread where others reported similar issues, I reverted back to the previous Hapax firmware and stayed there happily until v3.20 was released.
With the clock updates in v3.20, I thought I would give the new firmware a shot. Since updating, I’ve been experiencing bad timing issues in Studio Pro, with audio recordings landing on the grid early by ~2770 samples (almost 60ms). Trying to offset this with track delays in the DAW is obviously problematic as ~60ms is excessive.
After a whole weekend of troubleshooting (MIDI router settings, Windows 11 settings, loopback tests in the DAW, etc etc) I finally tried reverting back to Hapax OS v2.21 - and my issues are resolved. Unfortunately not an easy fix, as the Hapax wont read SD card files from v3.20 so all my settings seem to be gone.
Is anyone else dealing with clock issues on v3.20? Are there any Hapax clock settings I should be double-checking in the v3.20 firmware that might be incorrectly set?
I’m at a real loss with this and after a solid two days of troubleshooting and trying different things, have reverted back to using my Midronome sync box to provide midi clock to the Hapax
you seem to talk about recordings landing early (!) which indicates some sort of compensation applied by your daw.
The question is, if you let the daw play for example 16th notes, and let the Hapax do the same, pan each left and right and record that, how does it sound and how does it record?
In cases like this, keep things simple, try a simplified PoC and build up to the setup you have in mind.
Thanks for the replies, it is indeed a pretty strange scenario with the audio landing ahead of the grid. I don’t have any track delays or audio compensation set in my DAW at all.
At this point I’ve tried pretty much every possible troubleshooting step and different combinations I think I can try and can only conclude there is something funky going on with the Hapax clock on the v3.x firmware and how it functions with my set up.
Reverting to v2 firmware fixes the issue (either using Midronome clock VST or rv0’s plugin) but isn’t really a viable solution given the Hapax’s config is longer compatible after the firmware upgrade (SD card error due to version mismatch) and I’m missing out on v3.x features
Putting my Midronome sync device back in between my PC and my Hapax (v3.20) to manage clocking resolves the issue, so for now it looks like I’ll just stick with that
Between two CV pulses, the Hapax runs at its own internal tempo. If that tempo doesn’t match your DAW, notes can land early, by up to one pulse. ~2770 samples is about one pulse at 8ppqn around 120 BPM, so it might be “just that”, what do you think ?
Did you try this on v3.22:
SETTINGS > SYNC IN > CV FOLLOW TEMPO = ON (new in 3.20, off by default)
the highest clock rate rv0’s plugin can send (48 or 96ppqn), should set the same on the Hapax
If it’s still off after that, please send us the details through the contact form on squarp.net (CV clock rate, BPMs, and whether all notes are early or only off-beat ones) and we’ll dig into it.