06-01-2021, 11:44 AM
(06-01-2021, 07:35 AM)ttck Wrote: Same as arkoenig, I'm also very interested in how the MRCC does Midi thinning. I have experienced sync problems in the past, when using my Midi faderbank (UC 44 from Faderfox) via USB Midi and a Retrokits RK-005 USB-Host to control my setup.
When quickly changing values on 4 or more faders of the UC44, the Midi clock gets audibly bogged down (by what I think is too much Midi data) and thus the whole track gets temporarily slowed down... This is especially problematic in regards to my (slaved) Model:Cycles and can even knock it off sync compared to the other machines in my setup.
I really hope to avoid these kind of problems with the MRCC so I'm hoping for a smart and "lagless" solution, akin to arkoenigs proposals above.
Other than that, I just want to add that I'm really looking forward to making the MRCC the backbone of my setup as soon as it arrives.
Out of curiosity, what device is generating the master clock and is the UC 44 data being merged into the clock stream or is the UC 44 MIDI being sent to the device that is the master clock, or ???
Having a stable master clock that is distributed out to devices and not chained/merged with a bunch of other MIDI info is ideal. MIDI System Real Time messages (clocks) have higher priority, so any device getting flooded with a lot of MIDI should be throwing away non-clock messages as fast as it can if its buffer is getting full.