Today I realized (after monitoring the MIDI messages in the USB virtual cables) that the clock sync out option “clock+transport” does not actually mean “send clock to all virtual cables in USBx” but actually is just “send clock to cable 1”, for both USB Host and USB Device “Sync Output” config parameters.
To me, it would make more sense to have the following possible behaviors for the USB Host and USB Device sync output parameter:
“Clock+Transport”: sending clk & t to all the virtual cables in the USB H/C port
“Clock+T x” options, with x>=1 for sending clock only to one of the virtual cables.
Currently, x>=2.
The behavior for x=1 is the current behavior of “Clock+Transport” value.
I would rather add a new “Clock+T 1”, and change the behavior of “Clock+Transport” to mean “clock to all the virtual cables”.
I am ATM connecting 3 devices over the USB Host connection in the Hapax, and, without workarounds, I cannot send the clock to all the 3 “virtual cables” simultaneously.
Is there a rationale for why Squarp decided to not enable clock to all virtual cables simultaneously in FW 3.10?
Is there a rationale for why Squarp decided to not enable clock to all virtual cables simultaneously in FW 3.10?
I think the assumption is, that the the connected virtual hub is either flexible enough to route the clock as necessary or on the other hand possibly too dumb/slow to handle multiple clocks without adding them together or something.
It makes sense to not send the clock to all the virtual cables to not overload the receiving device merge / router and to minimize the message latency / jitter.
Ran into the same issue, solved it with my mioXL MIDI hub. All note/parameter connection from Hapax to it is via USB, except for a DIN pair that carries clock and transport. In the mioXL the connection is filtered to allow clock and transport only and then assigned to all destinations, besides the normal note and parameter data coming over USB virtual cables. Works like a charm.
A good Midi hub with USB connections, advanced routing, remapping and filtering hugely expands the Hapax’s capabilities, especially after the virtual cables and 16 drum rows per track were added in 3.00 and 3.1.
Yess this is how I solv3d it as well, took quite some time, and did not understand why my transport did not work, very very annoying. Found the seperate MIDI A to mioXL for sync by accident. Now I understand, so thanks!!
Dont like te separate loose midi cable visually though, but hey, it works now. Would be better if they changed this imho though =]