Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Pedro Lopez-Cabanillas <plcl@telefonica.net>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: rawmidi problems
Date: Mon, 08 Jul 2002 17:50:18 +0200	[thread overview]
Message-ID: <s5h1yaeuslh.wl@alsa2.suse.de> (raw)
In-Reply-To: <200207081741.46397.plcl@telefonica.net>

At Mon, 8 Jul 2002 17:41:46 +0200,
Pedro Lopez-Cabanillas wrote:
> 
> El Lun 08 Jul 2002 12:40, Takashi Iwai escribió:
> > At Fri, 5 Jul 2002 19:30:42 +0200,
> > Pedro Lopez-Cabanillas wrote:
> > > with /dev/midi00 ouput goes to ens-1371, /dev/midi01 goes to the first
> > > usb midi device, and /dev/midi02 goes to the second, but both usb devices
> > > have 2 inputs ans 2 outputs. Can I get all my five midi ports work with
> > > oss midi emulation?
> >
> > do you really need to use oss midi devices?
> > as long as you only reading/writing midi byte streams (i.e. no
> > ioctls), you can use simply alsa rawmidi devices, /dev/snd/midiCxDx,
> > instead of /dev/midiXX.
> 
> No, I agree with you. In fact, I don't need the raw midi devices at all, as 
> the sequencer API can do all and more.
> 
> My question was if I made a mistake or I am forgiving something, or if it is a  
> limitation on ALSA OSS emulation. Only trying to deeply test the new  
> snd-usb-midi driver. And for the fun of doing the things in several different 
> ways.
 
ok, point taken.

on OSS emulation, only up to two devices can be assigned per card.
one is assigned to /dev/midiXX and another to /dev/amidiXX.
which device is mapped can be changed via snd_midi_map and
snd_amidi_map options for snd-rawmidi module.
as default, they are specified as 0 and 1, respectively.


> As an example, and only for fun, this is a bash script for cron (hourly, of 
> course) that plays thru raw midi devices without any special program.
 
cool :)


ciao,

Takashi


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Oh, it's good to be a geek.
http://thinkgeek.com/sf

      reply	other threads:[~2002-07-08 15:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-05 15:53 rawmidi problems Pedro Lopez-Cabanillas
2002-07-05 16:33 ` Maarten de Boer
2002-07-05 16:57   ` Pedro Lopez-Cabanillas
2002-07-05 16:37 ` Takashi Iwai
2002-07-05 17:30   ` Pedro Lopez-Cabanillas
2002-07-08 10:40     ` Takashi Iwai
2002-07-08 15:41       ` Pedro Lopez-Cabanillas
2002-07-08 15:50         ` Takashi Iwai [this message]

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=s5h1yaeuslh.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=plcl@telefonica.net \
    /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