If you can't easily implement negative MIDI clock offset with respect to the metronome in this revision, it's probably not worth the complexity of including offset adjustment at all positive offset is much less likely to be needed, in my experience. These are scenarios where the MIDI clock needs to be slightly ahead of the metronome. Typically I'm trying to compensate for a device that has some internal latency, in order to bring it back into time with the metronome that everyone's playing to, or to compensate for a synth patch or tremolo-type effect with a soft attack envelope, where I want the notes to begin sounding sooner to partially compensate. Unfortunately, the type of offset I need to dial in most frequently is negative offset. I think parsing MIDI clock is where some of these programmers get a little out of their depth, or don't do enough testing, and fail to minimize or internally compensate for the resulting latency (not naming names, but guitar pedal makers are the main culprits in my experience).ģ) I am not a big modular guy, but I would think that devices that clock to CV/Analog/DIN sync are hopefully a little more likely to be "bang on", so not having the ability to dial in offset there should be fine. I also think it's "good enough" because:ġ) one hopes you won't have more than one misbehaving device in your rig.Ģ) My only experience with devices needing negative offset to line up properly has been with ones that take MIDI clock. It minimizes the added complexity to the interface design, as well as implementation and testing. Your solution of only providing for offset on only one of the MIDI outputs seems like a fairly elegant one. Yes, that was me with the long list on Facebook! If that works, what about the audio click and the CV/Analog/DIN outputs? The easiest is for them to stay where they are, with Output #1, but I guess you would want them to be moved as well, so the setting is basically negative latency on MIDI Output #1. So, with that in mind, what would you say to having a simple setting, a value in milliseconds (0 by default, probably 150 max) which will be a latency added on MIDI Output #2? If you need to have negative offset simply use MIDI Output #1 (which compared to Output #2 will have negative offset). And the list of settings is already getting very long. So there are no possibilities for menus and like. (just FYI the reason the MIDI Clock is implemented in a non-standard way is how I could obtain such a low jitter)Ģ) The settings interface is very limited, it's basically just a knob you can turn and press, and a 3-digit LED display. I'm gonna be very open about this - there are two issues with implementing this:ġ) First because of the way the MIDI Clock is sent it's actually a lot of code work - that means time to code, time to test, more troubles down the line. This leads me back to my original question.Nice to hear Daniel and thank you for writing!Īre you also the one who gave me that whole list on Facebook about how many usages you have of the per-output latency adjustment? So your solution is nice but it clearly hinges on having a very expensive sequencer that has a multi year waiting list. And yea the cirklon is super tight and can clock everything but how many ppl have a cirklon? Not many. I too had a cirklon and a usamo combo for a while and switched to the multiclock because of the issues i had. If the Usamo works for you that is awesome, but for me that was the case for the above reasons. I have been down both paths and for my studio it is no contest and worth the extra money. The erm plugin is rock solid in ableton and never hiccups or crashes for me. The erm has an onboard user interface that i can quickly adjust for latency. This is excellent for portable live jam syncing. The erm has 4 outputs so i can clock 4 pieces of hardware directly with no thru device if needed. The erm sends midi out along with clock so i can send that midi from ableton into my sequencer of choice and into my synths. No finnicky dial needs to be fine tuned on the erm, it works out of the box with about any interface. Also noted by os on his compatibility site. Usamo is not consistently sending clock out of my rme interface and constantly requires fine tuning to get close. Not sure on that one but its never been resolved thT im aware of. It is a known issue and Os says its an ableton thing. The usamo plugin fails to start in ableton consistently after i hit a track count of around 20.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |