[linux-audio-user] UM2 USB midi interface is the guilty ?

Lee Revell rlrevell at joe-job.com
Thu Aug 18 20:55:08 EDT 2005

On Wed, 2005-08-17 at 16:45 +0200, Clemens Ladisch wrote:
> > Surprisingly, aseqdump is detecting both devices.
> This one uses the ALSA API correctly. 

Actually I think there is a bug.  Here's my MIDI setup:

 Port    Client name                      Port name
  0:0    System                           Timer
  0:1    System                           Announce
 62:0    Midi Through                     Midi Through Port-0
 64:0    Audigy MPU-401 (UART)            Audigy MPU-401 (UART)
 64:32   Audigy MPU-401 (UART)            Audigy MPU-401 #2

If have gmidimon running on /dev/midi, aseqdump -p 64:0 fails with
-EBUSY, and dmesg says this:

ALSA sound/core/seq/seq_midi.c:187: midi input open failed!!!

But this should work, since gmidimon opens /dev/midi readonly:

rlrevell at mindpipe:~/cvs/alsa$ sudo lsof /dev/snd/midiC0D* /dev/midi*
gmidimon 20112 rlrevell    4r   CHR   14,2      3793 /dev/midi

Is concurrent access to MIDI by the ALSA sequencer and OSS apps really
forbidden?  The debug printk leads me to believe that this is supposed
to work.

BTW I hate GTK 1.2 so much that I took 10 minutes to port gmidimon to
gtk-2.0.  Patch is attached.  Apply it *after* running ./configure, as I
couldn't get autoconf work right as it insists on
using /usr/bin/gtk-config which doesn't exist in GTK-2.0.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: gtk-2.0.patch
Type: text/x-patch
Size: 2221 bytes
Desc: not available
Url : http://music.columbia.edu/pipermail/linux-audio-user/attachments/20050818/ce482461/gtk-2.0.bin

More information about the linux-audio-user mailing list