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. That’s a hell of a lot more than I can say about Overbridge.Lowering the buffer not giving any improvements, believe me i tried everything. It is more expensive and space-consuming, but it actually works well and in a scalable manner that is compatible with non-Elektron products. And, in my experience, the OB-enabled devices still can’t share their sample-accurate MIDI clocks over their DIN outputs and thereby sync the rest of your setup to the DAW.įor me, it has to be a proper many-channeled audio interface for multitracking (plus instruments that actually have individual outputs: hence I will never gel with the Digitakt, and I slightly resent the design of the Digitone I own) plus USAMO/Multiclock/Expert Sleepers ES series. This is also how Overbridge achieves its sync, but at a price of 60+ milliseconds of latency added to your DAW project. Same principle: delivering sample-accurate MIDI clock from a DAW to hardware by encoding the MIDI data as audio. I use a cheaper alternative to the Multiclock - the Expert Sleepers USAMO. Have only used it when traveling with only a Rytm or whatever. I have been using Overbridge-enabled Elektron instruments for 6 years and I have never been satisfied with OB. OB, you’ve got LOTS work to do… I can see why you’re afraid to show your face… ![]() Now I’m back to recording A4 tracks individually but it sure is great having no drifting on my long delays, Arps that stay in time and microtiming that doesn’t sound messy… So goodbye OB, goodbye multi-track recording, goodbye audio over USB… It’s been challenging, slightly amusing, very frustrating and mildly fun… ERM has shown me just how unstable you are and its time we parted ways… There is no way to manage midi offset when using OB (please enlighten me if you know of a way) and as a result, my A4 triggers a whole step out of time when synced to OB through Ableton… ironically, Ableton is clocking my ERM via audio and its tight, super tight… but the internal clock in Ableton has OB drifting all over the place… and I mean stupid drifts that are unusable! ![]() So I got an ERM Multiclock because I was sick to death of Midi jitter and needed some stability in my set up… Now I have a super tight set up EXCEPT for Overbridge… I’ve had to abandon OB for my A4 and can’t see myself using it again unless its stability can be drastically improved and the latency can be rectified.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |