Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"Kalvas, Taneli" <taneli.v.m.kalvas@jyu.fi>
Subject: Re: RawMIDI behaviour with MidiFace 4x4
Date: Mon, 09 Mar 2015 09:47:41 +0100	[thread overview]
Message-ID: <54FD5E2D.40801@ladisch.de> (raw)
In-Reply-To: <alpine.DEB.2.02.1503090933530.7125@lnxricardw1.se.axis.com>

Ricard Wanderlof wrote:
> On Sat, 7 Mar 2015, Kalvas, Taneli wrote:
>> I am developing a patch librarian for a synthesizer. Because the
>> communication happens with Midi sysex and timing is not relevant I chose
>> RawMIDI interface and not the alsa sequencer. The problem I have
>> encountered is that writing to the midi port with snd_rawmidi_write()
>> seems to broken. The function accepts any size of data block and claims
>> to have sent everything. In reality only a part of the message is sent.
>> For a large block size I can see the activity light blinking for
>> fraction of a second. This happens both in blocking and non-blocking
>> mode. I would expect the snd_rawmidi_write() to accept only a part of
>> the message.
>
> Can't help with rawmidi, but I can at least report that my experience
> using the sequencer interface has been that it is rather straightforward
> to use, even if just using it to send and transmit sysex data, even when
> the data is longer than 300 bytes.

If the data is larger than the RawMIDI buffer size (4096 bytes), the
sequencer does not wait (like snd_rawmidi_write() would do), but just
drops data.


Regards,
Clemens

  reply	other threads:[~2015-03-09  8:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-07 17:26 RawMIDI behaviour with MidiFace 4x4 Kalvas, Taneli
2015-03-09  8:38 ` Ricard Wanderlof
2015-03-09  8:47   ` Clemens Ladisch [this message]
2015-03-09 11:37     ` Kalvas, Taneli
2015-03-09 14:29     ` Ricard Wanderlof
2015-03-09 18:40       ` Clemens Ladisch
2015-03-09  8:43 ` Clemens Ladisch
2015-03-09 19:22   ` Kalvas, Taneli
2015-03-09 21:47     ` Clemens Ladisch
2015-03-10  7:32       ` Kalvas, Taneli
2015-03-10  8:02         ` Clemens Ladisch
2015-03-24  6:42           ` Kalvas, Taneli
2015-03-25 21:45             ` 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=54FD5E2D.40801@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=ricard.wanderlof@axis.com \
    --cc=taneli.v.m.kalvas@jyu.fi \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox