Ryan Underwood wrote: > On Mon, Jun 30, 2003 at 10:46:24AM +0200, Clemens Ladisch wrote: > > Ryan Underwood wrote: > > > /dev/sound/midi00 > > > > This is pretty much identical to /dev/snd/midiC0D0. > > There should be a midi01 file for your second card. (?) > > Yeah, it doesn't look like the snd-mpu401 driver registers an OSS > device. I think it should!
ALSA's rawmidi code is responsible for this AFAICS. > > > /dev/sound/sequencer > > > > The OSS sequencer, which handles all ports on all cards. > > Ok, so catting a file to this device will send it to all ports on all > cards? I don't really know, but I think it will be sent to the default port. What I meant to say is that it's possible to access all ports with this device file. > > > The data coming from midiC1D0, sequencer, and sequencer2 are all > > > different, but responds to my keyboard, so it must be the MIDI data > > > coming from the ISA MPU401 card, right? > > > > Yes. > > > > However, there isn't any device file that would output .mid files, you > > have to use a sequencer to record MIDI files. > > Interesting. Do you know anything about the differences between the > data produced by those three devices? Reading from the raw midi devices (/dev/snd/midiCxDx and /dev/sound/midi0x) will give you the MIDI data, at the same as it's received, without any timing information in the data itself. The data from /dev/sequencer(2) will include timing information and the source port; see the OSS documentation for details. HTH Clemens ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
