I can code an Arduino sketch for the RK002 midi processor to delay the message, but it would be completely disconnected from the audio: and the amount of the offset is dependent on the samplerate, buffersize and PDC.
There still would be jitter, but at least it would work. If only we could set a delay on the midi start message I would be happy. I sincerly believe there's something fundamentally wrong here, and am quite exhausted from spending countless hours trying to find a definitive answer. They should start when we hear the audio played back from mixbus, and it looks like they start 1 buffer early which is 1024 samples in my case. My particular focus is on getting external drum machines playing in sync. (05-26-2020, 07:57 AM)m4granger Wrote: Is this related to your question? Using Ardour 6 which I assume is same audio engine. If midi drum track is routed to an audio bus and then to an audio track it is recorded in sync to the midi track. Routing from midi drum track direct to another track the sync is lost and the audio is early.īut. Ive tried recording from a midi drum track to mix down to audio. It should be "set and forget" and this is not the this related to your question? Using Ardour 6 which I assume is same audio engine. I really like MixBus, great sounding, great workflow, but it's a showstopper if I can't count on the sync. It's pretty annoying, I do not have such issues with other DAW's and if this is not fixed rapidly, I have the choice to buy a ERM multiclock for 550€ or switch to another DAW. Like I said, I have reported the issue but didn't hear back yet. But midi sync and internal routing is incorrectly clocked.
ERM MULTICLOCK VS DAW FULL
Latency compensation for full audio roundtrips, once the hardware calibration has been properly executed, is spot on: that's great. This means that external devices synced to Mixbus start too early to. So, the metronome starts running, midiclock starts streaming and midi start messages are sent too early relative to the grid. Basically, what happens is that there's an issue with hardware latency compensation relative to clocked streams that are hardware independant, such as internal routings. What you describe sort of confirms that it's not related to my specific system.
(05-25-2020, 12:48 PM)Dirk Offringa Wrote: Hi, thanks for taking the time to do this little experiment. It should be "set and forget" and this is not the case.yet. Hi, thanks for taking the time to do this little experiment.
0 kommentar(er)
