Any chance this update could have broke the clock CV input?
Hapax is x4 too slow, tested Sample looped and CV Tools Clock device.
PPQN values are matching and I tried with different signal amplitude.
If i reduce the expected clock rate on the Hapax side it goes faster but gets hyper wonky.
Same clock works well on ALM PAM.
Disclaimer: i just rewired all my setup getting rid of tons on midi cables thanks to the new internal virtual cable, but i spent now 4h on this and i feel stuck.
I’m not aware of this issue, I think it should be fixed, if not, can you please send us a bug report with a little procedure? Contact us | Squarp instruments
Yes, please let me know!
Pitchbend had an issue with the “ACTIVE TRACK PORT“ setting that has been addressed, but since we don’t have the same setup, I’d be curious to know if it solved it for you as well.
Cheers,
Are the virtual cables going to spread to all the other locations where USB I/O is selectable? How does it work anyway when there is only port selection and no selection of the USB lane - does the communication happen only on the first lane (virtual cable) in that case?
I think it will/does. Latest beta added virtual cable parameter in the Output fx. Not sure if there are any other places left where you can’t select a virtual cable?