Quick fader move slows tempo (Overflow?)

Midihub Support
1

Hello I have the following midihub patch:

image
image441×750 34.9 KB

FROM A (Octatrack transport and clock)

TO B (Digitakt input with a THRU that goes to Analog Four)
TO C (Goes to an Analog Rytm)

FROM D (Novation Launch Control XL Incoming params)

TO D (Octatrack Input to receive CC from Novation)
TO B, TO C accordingly.

The idea is to have Novation control everything via midihub’s magic but keep the clock and transport from the Octatrack.

Now my problem is that when I do something quick with the Novation fader it will slow the clock down for all the devices

(Edit: When I monitor FROM A or FROM D while the tempo drifts when violently moving the fader I see no overflow messages)

DICHOTIC-MAIN-1.mhp (678 Bytes)

2

Does the same issue occur if you send the Novation XL controls to MIDI C instead, so Octatrack is not getting affected by the CCs at all?

3

Hey, back at the studio to test this.

If I bypass this chain:

image
image238×109 5.98 KB

So Octatrack receives NO input from the Novation (keeps sending transport & clock!), the problem keeps happening.

Also, another thing I didn’t mention previously is that the Octatrack tempo is NOT getting affected whatsoever, stays rock solid.

It’s like Midihub’s message queue is getting so many messages from a violent fader move that clock messages are getting buffered and delivered later.. If that makes any kind of sense on how MH works…