A huge thank you to our beta testers, your insights have been crucial in refining this software. We are pleased to announce that Beta F is officially available for download: HapaxOS update | Squarp instruments
We’ve addressed several reported bugs.
This build introduces several improvements.
Our team is currently developing major feature sets for subsequent releases.
Thank you so much for your beta testing and your incredibly valuable feedback!
Looking forward to the full release! The virtual cable feature is a gamechanger for me
hey 
it seems like there is no clock going out to USB host - im clocking a sp404 mk2 - Hapax to a OXI e16-controller going to sp404 mk2 - notes play but the it doesnt receive midi clock - switching to a normal midi port and it syncs again
There is new setting options in SYNC OUT: CLOCK + TRANSPORT → CLOCK + T CABLE 2 and so on. Maybe that helps?
For me host port and device port sync work, using Linnstrument and iPad.
Thanks Concrete3vidence - good to know it works in your end - i will investigate - it might be the OXI e16 that is the problem. Im using it as a hub and controller at the same time .- i have another midi hub i can connect via usb that i will try out
Noticed this evening that when pattern sync time is set to ‘patterns’ or track 1,2,3 etc… it doesn’t seem to be actually following the length of the patterns. Its switching patterns instantly even though all my patterns are 16 bars. Tested on 2 different projects.
Is anyone else noticing this?
Not really specific to this Beta…But the Beta and Prod manual refer to a pTRSP SYNC setting under Misc but it’s actually called TRANSPOSE SYNC there.
edit:
Also, there’s a PROJECT SYNC parameter not defined in the manual (see photo)
Is it possible that the “Midi” folder on the SSD card could allow for a folder structure? This way we can organize our midi for faster recall?
Did you ever get to the bottom of this? I’m finding the same - excited to try using the new USB virtual routing, only to find my drum machine won’t start! It’s definitely there and working but transport is ignored
Hapax → mio10 → Roland R8 → Intellijel Cascadia
Cascadia plays notes via the R8’s midi Thru, but the clock doesn’t seem to sync right. R8 won’t play at all.
Have tried CLOCK + TRANSPORT and all variations!
Didn’t you accidentally filter out transport messages in your mio10? I know that it is able to do so, and it seems to be the most obvious cause to me?
No, I’ve been through the new control app for the Mio and nothing is set to filter.
Very odd!
omg +1 on that
Hi Ben thanks for reminding me i just checked it out .. just replaced the OXI e16 with a simple Miditech 4x4 midi hub - (HAPAX - MIDItech hub - sp404 mk2) and it works fine ..my sp404 and my drumbreaks now sync to the Hapax and follows the bpm up and down - so for my part it must be the OXI e16 that doesnt seem to register midiclock thru usb
Np and thanks for checking!
I had another play around having gone through the hoops of updating the iConnectivity control panel and there isn’t any filtering active.
Think I’ve got it sorted though - Clock + Transport will only send transport out of DIN 1 on the Mio. So if I change it to Clock + T5 (the DIN port my R8 is plugged into on the mio) it gets transport and clock messages. Much the same analogy as Hapax midi output 1 sending clock, and then the mio handles routing it to everything else that has an onboard sequencer.
Looking at it, I’ll probably end up using an internal rule on the mio to send the Hapax’s clock and transport via (say) Clock + T7 (annoyingly 9+ didn’t work on the mio?) to everything plugged in, route that in the mio so it goes to all the DIN ports.
Fun fun fun…
Since updating to the latest beta, I’ve had a lot of random dropped notes. It’s not consistent, but notes in different tracks will just not play, and there is no probability involved, they should always play. If I downgrade back to the latest public release it stops happening.
I think i am also noticing dropped notes my end as well
Hi everyone! If you’re experiencing issues such as dropped notes (or any other bugs), please contact us via email so we can investigate further.
At the moment, with version 2.30F we haven’t been able to reproduce these issues on our end, and this version may be officially released soon.
Thanks!
I want just want to say AWESOME!
I recently acquire my Hapax and it came with HapaxOS 2.21.
I planned to use it with multiple MPE controllers, multiple MPE compatible synths, among more standard ones like the MC-707, and the MPE features announced in the 2.30 betas are a game changer for my setup.
I’m also using a Conductive Labs MRCC as a MIDI Hub and its 4 USB host ports so the USB Ports new features are as much important.
It goes like this:
So this way I can play my synths with my MPE controllers through the Hapax (via MRCC routing), and can play sequences from the Hapax to the synths.
At least that’s the plan. I’m waiting for the official 2.30 release to update and test all this.
But I wanted to say thanks for the great team work, which comforts me in the idea I have made the right choice with purchasing the future proof Hapax 
Indeed. I got mine just as this fw came out and it’s checking all of my MPE boxes so far. MPE + Virtual Cables = 
