A lil delayed but added the FHX-8CV to output note envelopes from poly tracks via fx section and works great so far. Also added outputs for it to output the two project lfos. In total that’s an FHX-8CV, FHX-8GT, and ESX-8GT for expansion of the FH-2; 32 additional outputs for the Hapax
I had the same results when I set mine up a year ago, working fluidly to Usb-C but skipping notes/info to Usb-A
3 Likes
How are people experiencing their Hapax + expert sleepers FH-2 setups lately? My Hapax keeps getting stuck every now and then - every few hours when trying to load a project. And my friend thinks (due to his own prior experiences with similar gear) it might be an issue between Hapax and FH-2 (over the FH2 usb C port).
This issue didn’t exist until the new Hapax 2.0 beta (and current Hapax firmware)
Any other people that use the FH2 that also have a bricking Hapax every now and then?
1 Like
So far all is fine here with Hapax USB-Host to FH-2 USB-C. FW 2.0.
I didn’t update yet to HapaxOS 2.01, because I don’t use MPE.
1 Like
Thanks - I’m having trouble to pinpoint where the issue of my bricking Hapax is coming from. I’ve decided to put some effort in trying to figure out where it’s coming from, or at least documenting my situation/setup/project every time it bricks. Hopefully at some point I can start reproducing the issue. (Lengthy way of saying: thanks for sharing your side, everything helps:)
1 Like
Was there a solution for the problem? I am sending from Hapax to FH-2 FHX-8CV extension by usb. Just simple kick note from Hapax at 128bpm, at every beat. I use a different note at every beat. All other tracks muted. I monitor using Mordax scope and often there is no voltage change on the FHX-8CV (gate and cv at the same time not changing) when Hapax sends a note. It skips a note approx every x seconds. Sometimes already after 10s, sometimes after more than 30s, can’t predict when). The time between the skips varies. All 4 notes have a length of 1 and a chance of 100% on the Hapax and there are no effects on the kick track of the Hapax. Using Hapax OS 2.02 and FH-2 firmware v1.23.0
What do you mean by different note at every beat and are you using a drum track on the Hapax for the kick trigger?
I am simply sending a gate and a pitch cv to the kick drum. Just note track, not drum track.
I don’t have these problems. Do you use Hapax USB-Host to FH-2 USB-C?
1 Like
Indeed. The problem of lost notes is only when using usb. I do not have the problems when using hapax midi din to FH-2 midi din expansion.
I mean, are you really using Hapax USB-Host to FH-2 USB-C and not Hapax USB-Device to FH-2 USB-A?
1 Like
The original MIDI 1.0 specification sets a hardware limitation of 31.25 kbaud (3125 bytes/second). This limitation applies to both DIN and USB MIDI connections - USB MIDI generally follows these same constraints for compatibility, despite USB itself having higher theoretical bandwidth.
CORRECTION: it’s not required by the spec, but could still be implemented as an engineering convention. Hapax does not rate-limit MIDI over USB (see below).
Are you sure that USB MIDI devices follow this same limit from the original 1983 spec?
I didn’t think there was a speed limit specified in the USB Device Class Definition for MIDI Devices 1.0 in 1999.
The purpose of this extension was that the increased bandwidth allowed for more possibilities (16 virtual midi cables each supporting 16 midi channels for a total of 256 vs the original 16 channel limit).
I was paraphrasing this guy
MIDI over Din has a hardware limitation of 3125B/s (bytes per second), MIDI over USB doesn’t have a defined limitation, but is often limited to this rate for compatibility reasons.
So you’re right; it’s not required by the spec, but could still be implemented as an engineering convention. 
Perhaps the Hapax team can tell us if they adhere to that limit. But I guess we gotta send an email? It seems they don’t like to engage with us on the forums.
1 Like
Hapax does not rate-limit MIDI over USB
3 Likes
thank you!