Erm multiclock set up5/2/2023 ![]() 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. 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?
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |