Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Midi delay to hardware sampler
#1
Been loving the nerdseq so much!! but run into my first little problem,
Im sending the midi out to an emu or Akai rack sampler (ESI 4000/CD3000i) 
my mate pointed out there's a slight delay on it and now it cant be unheard  Confused
When checking the signals on a computer there's between 0.005-0.01 second difference in the triggering of the cv and internal samples to the midi samplers 
there's no midi chain its direct form nerdseq to sampler
When ive searched if its a problem on the sampler side of things all I can find is people saying the advantage of them (over computers) is the lack of signal delay.

Am I missing any setting I can change or any routes round how to fix it?  outside of recording it on a different channel and editing on a computer? 

thanks for reading and making this beast of a sequencer
hope you having a good day
x
Reply
#2
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.
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!  Smile
Reply
#3
These 1ms delay will be lower once the USB MIDI adapter is there because of the much higher data rate and thus reduced latency. A similar argument goes for the amount of data that could be sent w/o adversely affecting timing. Any news or a rough ETA when that expander will be available?
Reply
#4
(03-13-2021, 05:53 PM)XORadmin Wrote: 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.

Thanks for the quick response, that all makes sense.

Just incase anyone else gets here searching for the same thing
turning off the midi clock send did seem to reduce it a bit and then putting in a gate delay (5ms) on the cv/gate tracks put everything into time (close enough) to not really be able to hear Smile


Would be a cool if in a future update we could put a slight delay on triggering the internal sample tracks too, I think I could get everything synced super tight then.

Thanks again Smile
Reply
#5
(03-13-2021, 07:00 PM)mgd Wrote: These 1ms delay will be lower once the USB MIDI adapter is there because of the much higher data rate and thus reduced latency. A similar argument goes for the amount of data that could be sent w/o adversely affecting timing. Any news or a rough ETA when that expander will be available?

Actually that would be in theory. Practically most USB midi with computers is much more worse than that in combination with operating systems.
No ETA yet. I just found out that the microcontroller i use got a factory lead time of more than 52 weeks and it seems to be sold out everywhere. I got to see what I can do. 
In combination with the hardware gear it most probably won’t make any difference.
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!  Smile
Reply
#6
Just out of curiosity:
I'm aware of the overhead the OS can put on USB MIDI. I assumed the NerdSEQ is essentially run on a powerful microcontroller and thus does not suffer from OS overhead. Or not?
Reply
#7
(03-13-2021, 07:46 PM)mgd Wrote: Just out of curiosity:
I'm aware of the overhead the OS can put on USB MIDI. I assumed the NerdSEQ is essentially run on a powerful microcontroller and thus does not suffer from OS overhead. Or not?

I am talking about NersSEQ -> computer and there the rules of the OS appear.

The USB is not integrated in the NerdSEQ (and never intended to, to avoid any overhead, in the end it is a embedded system). So the midi would not be USB speed, but a higher rate than midi.
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!  Smile
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)