![]() Very unstable sync from Ableton live to Beatstep Pro (same solution I proposed) E-RM Multiclcok, MIDI Jitter, Sync, MIDI Lag Solutions. A quick search shows many having this same problem, regardless of host… so it’s most likely the Beatstep Pro ability to clock externally that’s the problem to overcome. Jitter is a fairly common problem with some devices that want to be the master. Many devices prefer 16th note or 24 PPQN (DIN Sync). The faster the tempo the better… 8th notes is a default Korg standard. Setup a MIDI file on this instrument that uses whatever PPQN you like. If not the click track, you could make a VSTi with a square wave sound. Take that signal into both the Beatstep and MS20 via mult. To use the click track, you’d change the sound to a simple transient like the Urei Click ( CSG Urei Click - YouTube) and route the Click audio output to an unused physical out. You could use a plugin like Silent Way Sync, or simply use the Click Track in Cubase. Beatstep will stop attempting to calculate tempo and will just respond to pulse like the MS20, at that point. You could clock both these devices via CV Gate using an audio output from Cubase. every time I need to deal with the creepy visual and the layout of things it just doesn’t work for me to get used to it And no i hate Ableton so its not an option to move to other daw. I do insist that there is a solution for that and Ableton is the proof for this in both situation as master or external sync timing are tight and stable. If u have discovered a way to fix this issue the next Cubase update on me ![]() When the project playing you can see the tempo on the beatstep pro start’s drifting from 120 bpm to 118-123. ![]() Determine project tempo, send midi clock to specific device synced to Cubase in my case my beatstep pro controls my old MS20 via cv/gate and sending midi clock to the ms clock in. Yes u understand exactly what i mean when. Wow u have made simple issue like its rocket science. What does “Lags and drifts” mean exactly? Measures slow down and speed up? Could just be a complaint about preference. “Lags and drifts in timings…” isn’t exactly descriptive enough to imagine what they problem is technically. And many people didn’t know how to make groovy setups. These had to be taken care of in the early days when we only used hardware to make music, too. So always try to avoid sending other MIDI signals over the port that is used for MIDI sync, if you can’t avoid sending notes to the same port, shift the notes earlier or later by 1 tick, it will free the timing. MIDI is a slow serial connection, and 2 to 3 bytes of notes are often quantized to the nearest 16th, that position is also occupied by the single byte clock. clock, notes and so on, the slave becomes jittery so easily. This was new in C11.Īlso if you are using a single MIDI port for everything, i.e. If you insert a buffered plugin to the external inst input, the amount will be compensated, too. ![]() This way the MIDI clock will be sent earlier by the latency, so the audio signal arrives at cubase mixer at the exact timing (+the external hardware’s reaction time) which is regardless of buffersize. Try using MIDI clock slaves as external instruments and send clock to it instead of the actual MIDI interface. Lowering the buffer not giving any improvements, believe me i tried everything. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |