💿 hapaxOS PUBLIC BETA 2.30 E

Hey everyone,

Thank you so much for your beta testing and your incredibly valuable feedback!

We’re excited to announce that a new beta version (E) is now available here: HapaxOS update | Squarp instruments

  • Improved MPE compatibility – it’s now very close to the release version.

  • Bug fixes – several issues have been resolved.

  • New features – a few smaller additions, and we’re already cooking up major new features for upcoming updates.

We’ve also prepared a new setup guide for the Osmose, as we discovered a better way to connect it. You can check out the updated configuration here: https://beta.squarp.net/hapax/manual/modempe/#OaX2Gku

Have fun exploring the update!

11 Likes

Hello, can you confirm that the SLIDE routing bug from Input MIDI MPE 1…16 to USB dev 2…16 lowerz is still not resolved in this beta?

Thank you

Good Sunday all,

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.

Good catch! I can reproduce it. We will fix it and let you know, thanks!

5 Likes

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

Thanks!

2 Likes

I’ll double check and let you know THANK YOU

Tested and working, thanks!

Hi Mikei,

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,

Tom

1 Like

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?

1 Like

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?

1 Like