[linux-audio-user] MIDI confusion

Joe Hartley jh at brainiac.com
Sun Dec 26 11:40:38 EST 2004


On Sun, 26 Dec 2004 17:11:21 +0100
mchristoph.eckert at t-online.de (Christoph Eckert) wrote:

> 
> > [root at rickenbacker root]# aconnect -i
> > client 0: 'System' [type=kernel]
> >     0 'Timer           '
> >     1 'Announce        '
> > client 64: 'M Audio Audiophile 24/96 MIDI - Rawmidi 0'
> > [type=kernel] 0 'M Audio Audiophile 24/96 MIDI'
> 
> This means that your MIDI in has been properly set up and can 
> now be connected to any application which should be driven by 
> the incoming MIDI signal.

Ah, you've missed my mail goal here.  I don't want to use the 
Audiophile 24/96 MIDI interface - I don't want the system to even
see it, because I have a USB MIDI device (an M-Audio Radium keyboard)
that I want as the lone MIDI controller.

I think this is more a matter of not loading modules (snd-seq-midi?
snd-seq-midi-event?) for the Audiophile, and letting the USB module
do all the MIDI work, rather than setting something with aconnect, but
I certainly could be wrong!

-- 
======================================================================
       Joe Hartley - UNIX/network Consultant - jh at brainiac.com
Without deviation from the norm, "progress" is not possible. - FZappa




More information about the Linux-audio-user mailing list