You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Perhaps it's useful for other people have access to what it looks like the internal Overbridge message protocol.
Audio and MIDI are already available thru their respective ports. What we are talking about here is the data needed to synchronize the Overbridge plugins with the devices such as knob position or active step.
The unknown bytes in the USB blocks can be easily arranged in blocks of 128 bytes. Here you see 2 consecutive blocks from my Digitakt while being stopped.
Perhaps it's useful for other people have access to what it looks like the internal Overbridge message protocol.
Audio and MIDI are already available thru their respective ports. What we are talking about here is the data needed to synchronize the Overbridge plugins with the devices such as knob position or active step.
The unknown bytes in the USB blocks can be easily arranged in blocks of 128 bytes. Here you see 2 consecutive blocks from my Digitakt while being stopped.
Looks like there is an
e0 xx yy zz tt
header, wherexx yy zz tt
is a 4 bytes counter.Data is only 80 bytes long (ending with a
ef
) and the last 48 bytes are zeros.You can print these values with this patch.
It's not sure if this would be implemented as we need to know what's really going on under. But we can create a branch.
These two blocks are with the Digitakt playing.
The text was updated successfully, but these errors were encountered: