What is the normal process for that within this forum?
I have a mutated version of your dual-sequencer running the VCV voices you had and driving some Eurorack modules plus a kick coming from the Alphabase. Pretty interesting start… Heading to bed but can post tomorrow.
I have the same problem, no matter if I try to sync internally with Ardour or Renoise, or from my external Midibox Sequencer, a lot of pulses get dropped in VCV’s Midi-CV Module.
See my reply here: Midi clock renoise-vcv rack
If you manage to verifyably pin the problem down to Rack’s implementation of MIDI clock, that would be great, then we can get Andrew’s eyes on it.
I would love to be able to pin it down profesionally, but I can only read and understand a portion of code and believe, that if it would be easy, it already would have been solved .
Midi-Clock was always not 100% accurate. Most Softwares have a sort of “smoothing” or “calculate average” to get a “stable” clock.
By design Midi-Clock is hex 0xF8.
And if I see it right, MIDI_CV.cpp (Line 229ff) from github, triggers a Pulse in dsp::PulseGenerator in case the Midi Message is 0x8. But that does not happen everytime. Also, it is somehow depending on the Sample Rate. Higher VCV Engine Samplerate creates more Pulses.
CV-Midi sets a boolean (0 or 1) in midiOutput.setClock, wich then sends the hex 0xF8 as Midimessage, that, when monitoring it with f.e. MIDI-OX is pretty stable.
Problems I found here is that Midi-Message Start (hex 0xFA) and Stop (hex 0xFC) or Continue (0XFC) are not always transmitted, plus my Ardour and Cakewalk behave differently if VCV is set as Master (wich might be Ardours Midi-Implementation).
Interesting findings Alasdair! Instead of measuring the pulses on a scope, maybe try and listen to them, through a module that accepts a trigger and produces a sound, like a drum, or Rings, or something. The ear is really good at catching “a missing beat”. Then you could actually record the result in terms of audio, which can be used for a bug-report on the Rack github. I would be very interested if you can produce results, that demonstrate it if Rack’s MIDI clock is not reliable. Over the time a lot of folks have been muttering about this MIDI clock instability, so a lot of people would be thankful (me included) if you could crack this one open, and submit a good bug report.
Hi Omri! I wanted to circle back on this issue. I have created a new setup where the Impromptu Clocked is being synced to an external analogue clock (it is essential to my setup that VCV receives the external clock - but the clock has some flutter it. I wish I could let VCV be the master but I have things synced though an ER-M Multiclock and VCV needs to follow this clock as well.
I am using VCV to clock my Eurorack setup but the CLOCKED bpm but it very hard to reply on for recording. I am wondering how your experience is using an external clock, does is stay solid? Could this simply be a CPU or GPU issue?
I am going to give a try with Stellare’s Link device… I do have an Ableton link session running in sync with the ER-M so maybe that would provide a more stable source for Clocked… Anyway, just curious about your experience with this.
Just to update this thread, it turned out to be the computer… I reset everything up with a Macbook pro and the clock is tight and solid - Entire studio sharing the clock and VCV playing a massively central role in clock distribution… SO NICE!
Hi there,
I have started to explore vcv a few weeks ago. Now I ave done a number of tutorials etc from youtube.
Something that still bugs me out is the sync from ableton clock to vcv. I am sending pulses to impromptu clock in vcv via Bridge. I’m sending 4 pulses per quarternote and choosing the mode to p4 in Impromptu. Well… the impromptu clock jumps immediately to 450bmp. My bpm cable is flashing in tempo, so its the run led of impromptu, this do follow the tempo of pulses,bpm indication stucks on 450, no matter my tempo in ableton. Ratios / sending a continuous signal, while x apparently works fine…
I did a quick test and it seems that 450BPM is the fastest clock you can force CLOCKED to externally. My theory therefor is, that you are sending way faster than 4PPQ into it. Check your settings in Ableton. Also, Bridge is totally unsupported now, and never really worked well. Maybe also check this out:
Hello there just reading about this i’ve tried everytnhig and work goods on most machines BUT there is no way i can get a stable clock with the RD8 . anyone =?