Hello! The new version on MC6 PRO looks amazing from a MIDI clock stability perspective. Obviously, there are still other bugs to figure out and solidify in that before it is an official update, but I’m wondering if some of these same fixes will show up in the old controllers as well. The “MIDI clock jitter fix”, the “MIDI clock isolation from other real time messages”, and the “MIDI message delay fix when MIDI clock is being received” are all things that would be amazing to implement in the older controllers as well (if possible).
The new features will be added (Selectable ports for MIDI Clock) but the rest are not applicable to the older models. There isn’t any bug related to MIDI clock in the MC3/6/8. The bugs exists (regretfully) on the newer MC6 PRO as it is a different processor we are using so the code base is different.
I understand the different processor code base, and that leading to the regrettable bugs, and that’s cool with the selectable ports! However, while not a bug in nature then, I do experience the clock resetting on every switch press with the older model MC6 MKII I own (excluding the midi clock tap cause by nature, it should be doing that anyway). It’s the main reason why I have to split MIDI clock from my DAW to have a separate thru for my looper, as every time I’d access a switch to change presets or manipulate CC, it would reset the clock and jitter until it got back to the set bpm 2 seconds later. This happens both with external clock sources and with the internal clock as much as I have checked. Even with the looper out of the equation, my delays will be reset as well (confirmed by monitoring the live BPM readout from the Neuro Desktop editor for my Source Audio Collider Delay+Reverb), leading to brief moments of wide time shift and jitter whenever I hit a switch on the MC6, no matter the type of message(s) being sent. If that’s not something the older processors can handle, I can understand that, and let this inquiry rest.
This might be because the MC6 MKII is connected to the editor (i.e. in Edit mode). Can you confirm if this is the case?
Also, just to confirm you’re using the latest v3.11.1 firmware?
This happens in and outside of edit mode. I’m currently in 3.10, as I was also experiencing the MIDI clock getting off by a few BPM that was posted several days ago. I haven’t gone back to 3.11 yet as I’ve had a slew of shows that required external sync, and didn’t want to mess with it. However, I was experiencing this when I was in 3.11 as well.
Same issue with my MC6MK2 here. Every time, I send a start/stop message, my delays jitter for 2 seconds. This is very annoying and definitely a bug. A seperation of the clock from the other midi realtime messages is necessary.
You mean sending the Real Time start/stop message? Those are not sent together with the MIDI clock and are only sent when you explicitly add them in your preset. What delay pedal are you using? It sounds like your delays are reacting to the start/stop messages - not related to the MIDI clock being sent from the MC.
Thanks for your reply! Yes, currently I´m a bit confused by my midi setup.
I use the MC6Mk2 as my master clock and to send start/stop messages to my looper and groovebox. While the looper and groovebox work great, my time based effect pedals change the tempo, as soon as I press a footswitch on the MC6Mk2 to send a start/stop message.
It seems, that the delays recalculate the new bpm between the realtime start/stop message and the next clock beat. Is that, how midi sync works? Is it a normal behavior or can it be fixed? Thanks for your help!
(btw: currently, I´ve changed my midi chain and use the MC6Mk2 still as my midi clock and for PC/CC and I put my looper and groovebox last in the gain. The looper sends the start/stop messages to the groovebox. It works great this way but I really like to understand the reason for this change in delaytime. Thanks!)
It’s hard to say - you’ll need to check with the delay manufacturer for that. It will depend on how they are programmed to react to the Start/Stop messages. The MC6 just send the message out as programmed.