12/19/2023 0 Comments Erm multiclock set up> I want to add that the I/O latency calibration for the midi ports has no effect whatsoever on the RT messages. Thanks for the feedback! So we're making progress at least. Check if the click is aligned on the grid. ![]() Patch Ardour click to an audio track input, record metronome. Check if the click is aligned on the grid.Įven when routing internally, there's an issue: Patch the sequencer's audio click output into a audio interface input, and connect to a Ardour track. Patch midiclock to the midiport a sequencer is connected to. Make sure audio and midi have been calibrated. I downloaded Ardour to doublecheck and it has the same behaviour. When a external sequencer receives a start message, and we record its (audio) metronome, the record metronome shoul be perfectly aligned on the grid. This means that all latency compensation should apply to these RT messages too. The Real Time start/continue/stop messages should be sent when the actual audio starts to sound, so that synced external sequencers are synced to the recorded audio. When using the midi device calibration results, the offset is worse than when leaving them at default 0. On the other hand, audio latency compensation is spot on: I have correctly calibrated the audio hardware and it’s sample accurate. I spent countless hours checking every possibility I could think of, and reported the issue to Harrison support. They start/continue messages are always sent too early in relation to the grid, and this offset seems to be related to some latency compensation: if I insert a plugin that needs PDC (even the limiter on the main bus) the start/continue messages are issued even earlier but I did not identify a clear sample-accurate pattern. ![]() I have an issue with the midiclock and/or the start/continue messages. 0008153: Midi Real Time messages are sent too early (Mixbus AND Ardour)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |