3 May
2013
3 May
'13
9:37 a.m.
When receiving a normal 3 byte MIDI message most gear can process it in the interval
between messages. When receiving a large sysex buffer, a lot of gear chokes on converting
the MSG byte by byte into something usable - either because of a low buffer size, or some
horrible code on the part of the sysex parser.
Slowing sysex messages down has nothing to do with the baud rate of MIDI but more to do
with the between message gap and the processing power available during interrupt handling
periods. Slowing a sysex dump down means "just pause a lot more between bytes so that
the destination CPU can keep up"..
;
--
seclorum
On May 3, 2013, at 9:25, Julien Claassen <julien(a)mail.upb.de> wrote:
Hi Clemens!
Thanks for the tip. I'll try to convert the MIDI file to .syx.
A question: what is so special about amidi? I mean: what is the difference between it
playing a pure sysex file and aplaymidi playing the sysex block from a MIDI file?
Is there a commandline tool to dump sysex like that, using the ALSA sequencer system, by
any chance?
Warm regards
Julien
----------------------------------------
http://juliencoder.de/nama/music.html
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user