+- XOR Userforum (https://forum.xor.eu)
+-- Forum: Products (https://forum.xor.eu/forumdisplay.php?fid=3)
+--- Forum: NerdSEQ (https://forum.xor.eu/forumdisplay.php?fid=6)
+---- Forum: General Questions (https://forum.xor.eu/forumdisplay.php?fid=17)
+---- Thread: Midi latency (/showthread.php?tid=691)
Midi latency - theotteryears - 04-18-2020
Hi,
Do you know what the latency is from triggering from the midi expander?
I'm sending triggers out from the Nerdseq and also from the midi expander to the same drum module.
I've got them pretty bang on by delaying all non-midi tracks by OC in the track delay. However, the sample tracks dont have a track delay setting...
Midi jitter is annoying though!
RE: Midi latency - XORadmin - 04-18-2020
There is no delay in triggers compared to Midi. I assume some microseconds plus the time it takes to send a midi message.
Midi Jitter is more a problem of Computers, but not with embedded devices. The only thing i could think of if you send too many midi messages, then too much data goes through one midi port. But that is a problem with Midi speed specifications itself.
How does your setup look like and did you check already if your drum module has issues by itself?
In general, Triggers, Midi and Samples are send at the same time with the NerdSEQ, only differs some microseconds.
RE: Midi latency - theotteryears - 04-18-2020
hi! thanks for the reply.
I think it must be the Nord Drum 2 which has a small processing time (2 or 3ms).
I record a hit sent from Nerdseq trigger out, and also a hit from Nerdseq midi expander. Recorded onto two tracks there is a 2 or 3ms difference. I was trying to line these up perfectly, which is why I tried to delay all the other Nerdseq tracks so that the trigger is sent a little later so it matches up with the midi hit better.
Not sure if I'm going about that the right way though :S