All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ryan C. Underwood" <nemesis@icequake.net>
To: alsa-devel@alsa-project.org
Subject: rawmidi virtual and long sysexes
Date: Sat, 19 Dec 2015 15:31:44 -0800	[thread overview]
Message-ID: <20151219233143.GK28165@localhost.localdomain> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 879 bytes --]


Hi alsa-devel,

Recently I noticed this problem and fixed it in the client consuming
sequencer events:
https://github.com/munt/munt/commit/0ea0846d0849872acf4384bdf5edeff026d12f42

Basically, the rawmidi virtual plugin enforces a 256-byte limit on
events, and emits multiple events if e.g. a >256 byte sysex is
encountered.

This does not seem to be documented behavior for
snd_seq_event_input(), nor is the fixed limit described anywhere.

Would it be better if the maximum event size could be configured
through params?  That would avoid needing this clumsy workaround by
sequencer clients.  In any case, it seems that the documentation
should be updated to reflect the need to receive multiple sequencer
events to complete a sysex if EOX is not located in the first.

Please cc me as I'm not subscribed.

-- 
Ryan C. Underwood, <nemesis@icequake.net>

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 173 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



             reply	other threads:[~2015-12-19 23:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-19 23:31 Ryan C. Underwood [this message]
2015-12-22  5:51 ` rawmidi virtual and long sysexes Clemens Ladisch
2015-12-22 18:11   ` Ryan C. Underwood
2015-12-22 20:23     ` Stas Sergeev

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=20151219233143.GK28165@localhost.localdomain \
    --to=nemesis@icequake.net \
    --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.