All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Joerg-Cyril.Hoehle@t-systems.com
Cc: alsa-devel@alsa-project.org
Subject: Re: Must MIDI SysEx data contain the start byte 0xf0 and the end byte 0xf7?
Date: Fri, 18 Jan 2013 18:29:00 +0100	[thread overview]
Message-ID: <50F9865C.4010200@ladisch.de> (raw)
In-Reply-To: <8E4C156DA5797D418DBFADFD8CE655A41EFE3BA591@HE113481.emea1.cds.t-internal.com>

Joerg-Cyril.Hoehle@t-systems.com wrote:
> I've read about SysEx continuations aka. divided SysEx
> http://www.allegro.cc/forums/thread/607445
> http://www.sonicspot.com/guide/midifiles.html
>
> What it means is that within a MIDI file, a long sysex could be split
> across several events with different delta times, giving the receiver
> some processing time in between (e.g. flash EEPROM etc.).  The delta
> times tell when to send the parts.
>
> Now, is that truth?  How to do that with ALSA?

Just put the partial chunks into separate events.
The first must begin with the F0 byte, the last end with F7.
(This is not actually checked; you can put arbitrary bytes into SysEx
event data.)

> The documentation on snd_seq_ev_set_sysex insists:
> "the sysex data must contain the start byte 0xf0 and the end byte 0xf7."

This is wrong.  For that matter, when the sequencer receives from the
hardware a SysEx that is too large for its internal buffer, it will
split it into pieces.


Regards,
Clemens

  reply	other threads:[~2013-01-18 17:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-18 16:17 Must MIDI SysEx data contain the start byte 0xf0 and the end byte 0xf7? Joerg-Cyril.Hoehle
2013-01-18 17:29 ` Clemens Ladisch [this message]
2013-01-18 18:41   ` Joerg-Cyril.Hoehle
2013-01-20 16:40     ` Clemens Ladisch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50F9865C.4010200@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=Joerg-Cyril.Hoehle@t-systems.com \
    --cc=alsa-devel@alsa-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.