From: Clemens Ladisch <clemens@ladisch.de>
To: "Kalvas, Taneli" <taneli.v.m.kalvas@jyu.fi>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: RawMIDI behaviour with MidiFace 4x4
Date: Tue, 10 Mar 2015 09:02:46 +0100 [thread overview]
Message-ID: <54FEA526.10708@ladisch.de> (raw)
In-Reply-To: <6A72E9C91650BD49A6D9B305755BC04C42D80787@mbs1.ad.jyu.fi>
Kalvas, Taneli wrote:
> This is a common problem with many devices across several brands of
> devices and influences not only Linux but also other systems (see for
> example a list by wabbiguy at http://forum.highlyliquid.com/archive/index.php/t-500.html).
These devices use different firmwares and drivers, and as far as I know,
work flawlessly in Linux. This appears to be a problem with the Windows
MIDI framework. (Apparently, it behaves like the ALSA sequencer, i.e.,
drops data when its internal buffer overflows; there is no blocking API
like snd_rawmidi_*.)
> What do you think about a possibility for a customized driver for this
> class of hardware (I mean usb compliant midi interfaces with broken
> output ring buffer)?
Such a customization would be possible. But it's unlikely that I will
find time in the near future.
Regards,
Clemens
next prev parent reply other threads:[~2015-03-10 8:02 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
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 [this message]
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=54FEA526.10708@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--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.