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 19:40:52 +0100 [thread overview]
Message-ID: <54FDE934.3060208@ladisch.de> (raw)
In-Reply-To: <alpine.DEB.2.02.1503091524320.7125@lnxricardw1.se.axis.com>
Ricard Wanderlof wrote:
> On Mon, 9 Mar 2015, Clemens Ladisch wrote:
>> 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.
>
> I have noted though, that when sending data with snd_seq_ev_set_sysex()
> that the ALSA lib internally copies the data to an internal, malloced
> buffer, so I always thought that it would take care of any amount of data
> from there, but apparently not then?
The sequencer was designed for real-time events. When events are scheduled
to be sent later, there is no good mechanism to let the current buffer fill
level influence the timing of events, or to report errors back.
Regards,
Clemens
next prev parent reply other threads:[~2015-03-09 18:41 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
2015-03-09 11:37 ` Kalvas, Taneli
2015-03-09 14:29 ` Ricard Wanderlof
2015-03-09 18:40 ` Clemens Ladisch [this message]
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=54FDE934.3060208@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 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.