03-13-2021, 05:53 PM
You will always have a delay of 0,001 seconds with midi anyway per command which is caused by the midi bytes. You will never have better than this (excluding running status for now).
That is not a NerdSEQ thing but a midi speed thing.
Then they can be commands in between, not sure if you sequence more than only notes, that would increase the delay. All Midi FX commands are executed before the note play.
Then a clock byte also with it if enabled.
You can get to the delay easily but that is mainly a midi issue.
The only way to measure the real delay is to scope like the trigger and the end of the midi stream.
And if you use also program changes, then the wirst delay is nearly always on the receiver side. Sometimes up to 1 second or so.
That is not a NerdSEQ thing but a midi speed thing.
Then they can be commands in between, not sure if you sequence more than only notes, that would increase the delay. All Midi FX commands are executed before the note play.
Then a clock byte also with it if enabled.
You can get to the delay easily but that is mainly a midi issue.
The only way to measure the real delay is to scope like the trigger and the end of the midi stream.
And if you use also program changes, then the wirst delay is nearly always on the receiver side. Sometimes up to 1 second or so.
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!