[seq] latency

jaiserpe's icon

Using [seq] I am getting a latency of about 230 ms since I send the Start message to when the first sound is produced.

Would I reduce this latency using an external MIDI sound module?

Emmanuel Jourdan's icon

Try sending the delay 0 message, it will start from the first MIDI information.

jaiserpe's icon

Thanks but it doesn't improve

Jeremy's icon

Please post a patcher along with the MIDI data in question. Thanks!

jaiserpe's icon

The latency is similar with any MIDI file. The patcher I'm pasting is part of a Max tutorial so you guys should have the MIDI file in your search path.

The first bang triggers everything.

Max Patch
Copy patch and select New From Clipboard in Max.

broc's icon

Just did a quick test and found latency less than 1 ms.
So I guess your midi player device is the culprit.

Max Patch
Copy patch and select New From Clipboard in Max.

jaiserpe's icon

Yes, with a similar meassurement method I also get less than 1 ms.

But I'm meassuring the latency in a different way. From a practical point of view I'm interested in the latency between the key (or mouse button) hit and the first sound comming out of the speakers. Of course here the MIDI player device is involved.

I use Audacity to record both the mouse click sound for activating the first bang and the speakers with the MIDI sounds. This way I can meassure the latency back in Audacity.

I'm curious to see other laptops' latencies using this method. I use a Toshiba. Could you guys let me know your laptops' latency? Thanks!

jaiserpe's icon

Maybe the problem comes from the Microsoft GS Software Wavetable Synth. It is said it introduces a large latency.

Any other "soft-synth" as an alternative?

yaniki's icon

I think, JAISERPE is right. It's probably latency of the MS GS Software Wavetable Synth and/or latency of your audio port.