Skip to contentSkip to conversation

midi and ecasound

linux-audio-user Kai Vehmanen 2 participants 2 messages Aug 16, 2005 – Aug 17, 2005 3 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): 1123884862.12680.62.camel@mindpipe

#3 lore raw

Hi,

Quoted 2 lines · Lee Revell

Um, /dev/snd/midi* are not supposed to be used directly by applications. They are intended to be accessed via alsa-lib.

has there been (or is under planning) any major changes to this, or known problems?

Ecasound (and many other apps) has used /dev/snd/midi* with no reported problems for many years now (at least since ALSA 0.6.x). See for example:
http://lalists.stanford.edu/lad/2001/Apr/0176.html

I understand the general principle of getting rid of all direct "user-space apps <-> ALSA kernel modules" interactions, but in this case I'd like to stick with the current code until there's some practical reason to update (adding support for ALSA sequencer API is another thing). The good ol' read/write interface is quite sufficient for rawmidi, and you can cover many use-cases with one piece of code (ALSA, OSS, pipes, etc)...

PS In this case not using alsa-lib is obviously not the problem as
the same thing happens with /dev/midi*...

--
links, my public keys, etc at http://eca.cx/kv

-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

#4 lore raw

At Wed, 17 Aug 2005 00:48:44 +0300 (EEST),

Quoted 9 lines · Kai Vehmanen

Hi,

Quoted 2 lines · Lee Revell

Um, /dev/snd/midi* are not supposed to be used directly by applications. They are intended to be accessed via alsa-lib.

has there been (or is under planning) any major changes to this, or known problems?

So far, no. Simple open/read/write/close the device should work.

Of course, this will lack of the functionality alsa-lib provides, e.g. like virtual MIDI.

Quoted 8 lines

Ecasound (and many other apps) has used /dev/snd/midi* with no reported problems for many years now (at least since ALSA 0.6.x). See for example:

    http://lalists.stanford.edu/lad/2001/Apr/0176.html

I understand the general principle of getting rid of all direct "user-space apps <-> ALSA kernel modules" interactions, but in this case I'd like to stick with the current code until there's some practical reason to update (adding support for ALSA sequencer API is another thing).

virmidi is already in alsa-lib, so the byte streaming access via snd_rawmidi_read()/write() can work as a sequencer port.

Takashi

-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf