If you set the M:C’s sequencer to take tempo from an external clock source but then do not send it any clock messages, then the M:C does not know how fast to run and so will not play.
The section of the MIDI specification that covers clock messages is titled “System Real-Time Messages”. Regarding Start and Continue messages, it says:
When a receiver is synchronized to incoming Real Time messages … , the receipt of a Start (FAH) or Continue (FBH) message does not start the sequence until the next Timing Clock (F8H) is received.
Haaaa ok I see, you have not understood what I ws explaining.
Sure that I send in this situation an external clock
Well, still here you have not understood what I am requesting and which is perfectly respecting the midi specs :(.
In what I request the output of clock will start be emitted when we press the Play button, not in permanence as soon as we select the pattern.
I don’t think it’s a glitch/bug as it happens on all my other elektron devices to my knowledge, just some parameters it is more noticable and based on how fast you move a knob and how fast your bpm is. Basically you can tweak parameters in between each lock, it can have a neat effect some times but other times it will be bothersome.
That’s also bad practice. Any device receiving the clock messages would not be pre-locked to the transmitter’s tempo and so the receiver may not play at the correct tempo for a short period after the Start message.
Don’t know if this has already been suggested but it would be cool if we could disable the auto-track-select on the pads. Then you could jam out on all the other pads while tweaking the current selected machine.
as of today, i would say that USB audio DOESN’T WORK.
using it with ASIO4ALL in order to simply allow it and my audio interface to work together. the audio is TERRIBLE. it is in-the-red and distorted and there is no master volume for USB at all.
The audio is so loud that Ableton Live has consistently shut down all audio to protect hardware.
i’ve been experimenting with some serial track configurations to regulate it.
otherwise, using “CTRL-ALL” with volume/distortion helps… maybe if the resolution of this control was multiplied X2 or 4 or so it would allow compensation for different dynamic ranges.