25 May
2003
25 May
'03
9:18 a.m.
Hi,
I'm trying to figure out what device I should point
applications (ardour) at in order for them to see
incoming mmc and to send mtc. I've got what appears to
be a working USB midiman 8x8:
aconnect -i
client 0: 'System'
[type=kernel]
0 'Timer '
1 'Announce '
client 72: 'Rawmidi 1 - MidiSport 8x8' [type=kernel]
0 'MidiSport 8x8 Port 0'
1 'MidiSport 8x8 Port 1'
2 'MidiSport 8x8 Port 2'
3 'MidiSport 8x8 Port 3'
4 'MidiSport 8x8 Port 4'
5 'MidiSport 8x8 Port 5'
6 'MidiSport 8x8 Port 6'
7 'MidiSport 8x8 Port 7'
8 'MidiSport 8x8 Port 8'
aconnect -o
client 72: 'Rawmidi 1 - MidiSport
8x8' [type=kernel]
0 'MidiSport 8x8 Port 0'
1 'MidiSport 8x8 Port 1'
2 'MidiSport 8x8 Port 2'
3 'MidiSport 8x8 Port 3'
4 'MidiSport 8x8 Port 4'
5 'MidiSport 8x8 Port 5'
6 'MidiSport 8x8 Port 6'
7 'MidiSport 8x8 Port 7'
8 'MidiSport 8x8 Port 8'
With a M-Audio Audiophile 2496 I used
device="/dev/snd/midiC1D0" but this device doesn't
seem to be working.
/dev/snd/ has the following devices:
controlC0 midiC1D0 pcmC0D0c pcmC0D0p seq timer
I'm using alsa-patch-bay to manage the connections:
Could not subscribe ports:
Subscription Rawmidi 1 - MidiSport 8x8::MidiSport
8x8 Port 1 -> Rawmidi 1 - MidiSport 8x8::MidiSport 8x8
Port 0 failed:
Resource temporarily unavailable
Subscription 'Rawmidi 1 - MidiSport 8x8::MidiSport 8x8
Port 1' -> 'Rawmidi 1 - MidiSport 8x8::MidiSport 8x8
Port 1' succeeded
Subscription 'Rawmidi 1 - MidiSport 8x8::MidiSport 8x8
Port 1' -> 'Rawmidi 1 - MidiSport 8x8::MidiSport 8x8
Port 2' succeeded
Subscription 'Rawmidi 1 - MidiSport 8x8::MidiSport 8x8
Port 1' -> 'Rawmidi 1 - MidiSport 8x8::MidiSport 8x8
Port 3' succeeded
Subscription 'Rawmidi 1 - MidiSport 8x8::MidiSport 8x8
Port 1' -> 'Rawmidi 1 - MidiSport 8x8::MidiSport 8x8
Port 4' succeeded
Subscription 'Rawmidi 1 - MidiSport 8x8::MidiSport 8x8
Port 1' -> 'Rawmidi 1 - MidiSport 8x8::MidiSport 8x8
Port 5' succeeded
Subscription 'Rawmidi 1 - MidiSport 8x8::MidiSport 8x8
Port 1' -> 'Rawmidi 1 - MidiSport 8x8::MidiSport 8x8
Port 6' succeeded
Subscription 'Rawmidi 1 - MidiSport 8x8::MidiSport 8x8
Port 1' -> 'Rawmidi 1 - MidiSport 8x8::MidiSport 8x8
Port 7' succeeded
Subscription 'Rawmidi 1 - MidiSport 8x8::MidiSport 8x8
Port 1' -> 'Rawmidi 1 - MidiSport 8x8::MidiSport 8x8
Port 8' succeeded
OK, that all seems fairly normal but I'm thinking it
isn't. From the 8x8 perspective; incoming data to the
8x8 Midi IN 2 should go out of all eight channels but
it fails to go out channel 1. So, there's something
funny going on. This is according to the indicator
lights on the front of the 8x8.
From Alsa's perspective Midi IN 2 = port 1
Anyway, I've been up all nite and am tired. If my
message isn't clear enough please ask questions and
I'll reply. Hey, ladcca, alsa-patchbay and the 8x8
firmware driver are lookin' sweet. Thanks much!
ron
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
25 May
25 May
9:23 p.m.
Hi,
Disreguard the port routing stuff. But I am still
looking for the device from which mmc and mtc messages
are recieved and sent.
ron
--- R Parker <rtp405(a)yahoo.com> wrote:
Hi,
I'm trying to figure out what device I should point
applications (ardour) at in order for them to see
incoming mmc and to send mtc. I've got what appears
to
be a working USB midiman 8x8:
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
aconnect -i
client 0: 'System'
[type=kernel]
0 'Timer '
1 'Announce '
client 72: 'Rawmidi 1 - MidiSport 8x8' [type=kernel]
0 'MidiSport 8x8 Port 0'
1 'MidiSport 8x8 Port 1'
2 'MidiSport 8x8 Port 2'
3 'MidiSport 8x8 Port 3'
4 'MidiSport 8x8 Port 4'
5 'MidiSport 8x8 Port 5'
6 'MidiSport 8x8 Port 6'
7 'MidiSport 8x8 Port 7'
8 'MidiSport 8x8 Port 8'
aconnect -o
client 72: 'Rawmidi 1 -
MidiSport 8x8' [type=kernel]
0 'MidiSport 8x8 Port 0'
1 'MidiSport 8x8 Port 1'
2 'MidiSport 8x8 Port 2'
3 'MidiSport 8x8 Port 3'
4 'MidiSport 8x8 Port 4'
5 'MidiSport 8x8 Port 5'
6 'MidiSport 8x8 Port 6'
7 'MidiSport 8x8 Port 7'
8 'MidiSport 8x8 Port 8'
With a M-Audio Audiophile 2496 I used
device="/dev/snd/midiC1D0" but this device doesn't
seem to be working.
/dev/snd/ has the following devices:
controlC0 midiC1D0 pcmC0D0c pcmC0D0p seq timer
I'm using alsa-patch-bay to manage the connections:
Could not subscribe ports:
Subscription Rawmidi 1 - MidiSport 8x8::MidiSport
8x8 Port 1 -> Rawmidi 1 - MidiSport 8x8::MidiSport
8x8
Port 0 failed:
Resource temporarily unavailable
Subscription 'Rawmidi 1 - MidiSport 8x8::MidiSport
8x8
Port 1' -> 'Rawmidi 1 - MidiSport 8x8::MidiSport 8x8
Port 1' succeeded
Subscription 'Rawmidi 1 - MidiSport 8x8::MidiSport
8x8
Port 1' -> 'Rawmidi 1 - MidiSport 8x8::MidiSport 8x8
Port 2' succeeded
Subscription 'Rawmidi 1 - MidiSport 8x8::MidiSport
8x8
Port 1' -> 'Rawmidi 1 - MidiSport 8x8::MidiSport 8x8
Port 3' succeeded
Subscription 'Rawmidi 1 - MidiSport 8x8::MidiSport
8x8
Port 1' -> 'Rawmidi 1 - MidiSport 8x8::MidiSport 8x8
Port 4' succeeded
Subscription 'Rawmidi 1 - MidiSport 8x8::MidiSport
8x8
Port 1' -> 'Rawmidi 1 - MidiSport 8x8::MidiSport 8x8
Port 5' succeeded
Subscription 'Rawmidi 1 - MidiSport 8x8::MidiSport
8x8
Port 1' -> 'Rawmidi 1 - MidiSport 8x8::MidiSport 8x8
Port 6' succeeded
Subscription 'Rawmidi 1 - MidiSport 8x8::MidiSport
8x8
Port 1' -> 'Rawmidi 1 - MidiSport 8x8::MidiSport 8x8
Port 7' succeeded
Subscription 'Rawmidi 1 - MidiSport 8x8::MidiSport
8x8
Port 1' -> 'Rawmidi 1 - MidiSport 8x8::MidiSport 8x8
Port 8' succeeded
OK, that all seems fairly normal but I'm thinking it
isn't. From the 8x8 perspective; incoming data to
the
8x8 Midi IN 2 should go out of all eight channels
but
it fails to go out channel 1. So, there's something
funny going on. This is according to the indicator
lights on the front of the 8x8.
From Alsa's perspective Midi IN 2 = port 1
Anyway, I've been up all nite and am tired. If my
message isn't clear enough please ask questions and
I'll reply. Hey, ladcca, alsa-patchbay and the 8x8
firmware driver are lookin' sweet. Thanks much!
ron
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com 
26 May
26 May
7:17 a.m.
R Parker wrote:
I'm trying to figure out what device I should point
applications (ardour) at in order for them to see
incoming mmc and to send mtc. I've got what appears to
be a working USB midiman 8x8:
If the data is from/to an external device connected to the 8x8, it should
work with the appropriate port (0-7). If the data is for the 8x8 itself,
you could try the ninth port ("Port 8") which is called "Control Port"
in
the Windows driver.
I don't actually have a MidiSport, so I don't know if or how it has to be
configured to do MIDI timing.
HTH
Clemens
aconnect -i
client 72: 'Rawmidi 1 -
MidiSport 8x8' [type=kernel]
0 'MidiSport 8x8 Port 0'
1 'MidiSport 8x8 Port 1'
2 'MidiSport 8x8 Port 2'
3 'MidiSport 8x8 Port 3'
4 'MidiSport 8x8 Port 4'
5 'MidiSport 8x8 Port 5'
6 'MidiSport 8x8 Port 6'
7 'MidiSport 8x8 Port 7'
8 'MidiSport 8x8 Port 8'
2:53 p.m.
Hi Clemens,
Thanks for the reply. I still don't understand where
the usb-midi i/o device is.
Here's my device chain Tascam DM-24 digital mixing
consol and ardour.
DM-24 (mmc) -> to Ardour, Ardour (mtc) -> DM-24
The DM-24 sends a deferred play (type =3) to Ardour
and causes the Ardour transport to play engage. Ardour
in turn replies with MTC to syncronize the location of
the DM-24 transport with itself.
I've used 'dd...' to look for incoming messages:
'dd bs=1 if=/dev/snd/midiC1D0'
There's no messages passing through /dev/snd/midiC1D0
which is the device I use with the Audiophile 2496 for
example <MIDI-port tag="midisport"
device="/dev/snd/midiC1D0" type="alsa/raw"
mode="duplex"/>.
Perhaps I'm missing the obvious.
ron
--- Clemens Ladisch <clemens(a)ladisch.de> wrote:
R Parker wrote:
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
I'm trying to figure out what device I should
point
applications (ardour) at in order for them to
see
incoming mmc and to send mtc. I've got what
appears to
be a working USB midiman 8x8:
[type=kernel]
aconnect -i
client 72: 'Rawmidi 1 -
MidiSport 8x8' 0 'MidiSport 8x8 Port 0'
1 'MidiSport 8x8 Port 1'
2 'MidiSport 8x8 Port 2'
3 'MidiSport 8x8 Port 3'
4 'MidiSport 8x8 Port 4'
5 'MidiSport 8x8 Port 5'
6 'MidiSport 8x8 Port 6'
7 'MidiSport 8x8 Port 7'
8 'MidiSport 8x8 Port 8'
If the data is from/to an external device connected
to the 8x8, it should
work with the appropriate port (0-7). If the data is
for the 8x8 itself,
you could try the ninth port ("Port 8") which is
called "Control Port" in
the Windows driver.
I don't actually have a MidiSport, so I don't know
if or how it has to be
configured to do MIDI timing.
HTH
Clemens
5:05 p.m.
R Parker wrote:
I still don't understand where the usb-midi i/o
device is.
...
There's no messages passing through /dev/snd/midiC1D0
This file handles all nine ports. The ALSA library uses a magic IOCTL to
select the desired port; when you access the file directly, you get the
first port only.
If possible, you should use a program that can access MIDI ports via the
ALSA library (the 8x8's ports would be named "hw:1,x", x = 0..8).
If you want to access other MIDI ports than the first with a device file,
you have to load the snd-virmidi driver, which will give you some virtual
MIDI ports, and to connect these ports to the 8x8's ports with aconnect.
HTH
Clemens
5:33 p.m.
Hi Clemens,
--- Clemens Ladisch <clemens(a)ladisch.de> wrote:
R Parker wrote:
After examining things a little closer, your reply
confirms my conclusion.
I think there's something wrong because no data is
making it to the /dev/snd/midiC1D0 file.
For demonstration, I've connected everything:
I still don't understand where the usb-midi
i/o
device is.
...
There's no messages passing through
/dev/snd/midiC1D0
This file handles all nine ports. The ALSA library
uses a magic IOCTL to
select the desired port; when you access the file
directly, you get the
first port only. aconnect -li
client 0: 'System'
[type=kernel]
0 'Timer '
1 'Announce '
Connecting To: 128:0, 129:0
client 72: 'Rawmidi 1 - MidiSport 8x8' [type=kernel]
0 'MidiSport 8x8 Port 0'
Connected From: 72:1, 72:2, 72:3, 72:4, 72:5,
72:6, 72:7
1 'MidiSport 8x8 Port 1'
Connecting To: 72:0, 72:1, 72:2, 72:3, 72:4,
72:5, 72:6
Connected From: 72:1, 72:2, 72:3, 72:4, 72:5,
72:6, 72:7
2 'MidiSport 8x8 Port 2'
Connecting To: 72:0, 72:1, 72:2, 72:3, 72:4,
72:5, 72:6, 72:7
Connected From: 72:1, 72:2, 72:3, 72:4, 72:5,
72:6, 72:7
3 'MidiSport 8x8 Port 3'
Connecting To: 72:0, 72:1, 72:2, 72:3, 72:4,
72:5, 72:6, 72:7
Connected From: 72:1, 72:2, 72:3, 72:4, 72:5,
72:6, 72:7
4 'MidiSport 8x8 Port 4'
Connecting To: 72:0, 72:1, 72:2, 72:3, 72:4,
72:5, 72:6, 72:7
Connected From: 72:1, 72:2, 72:3, 72:4, 72:5,
72:6, 72:7
5 'MidiSport 8x8 Port 5'
Connecting To: 72:0, 72:1, 72:2, 72:3, 72:4,
72:5, 72:6, 72:7
Connected From: 72:1, 72:2, 72:3, 72:4, 72:5,
72:6, 72:7
6 'MidiSport 8x8 Port 6'
Connecting To: 72:0, 72:1, 72:2, 72:3, 72:4,
72:5, 72:6, 72:7
Connected From: 72:1, 72:2, 72:3, 72:4, 72:5,
72:6, 72:7
7 'MidiSport 8x8 Port 7'
Connecting To: 72:0, 72:1, 72:2, 72:3, 72:4,
72:5, 72:6, 72:7
Connected From: 72:2, 72:3, 72:4, 72:5, 72:6,
72:7
8 'MidiSport 8x8 Port 8'
With this scenario anything that comes in port_N,8
should be seen in the file /dev/snd/midiC1D0. Am I
right?
I'm sending commands into 2 and 8 but there's no data.
If possible, you should use a program that can
access MIDI ports via the
ALSA library (the 8x8's ports would be named
"hw:1,x", x = 0..8).
I've always used dd to see check for incoming mmc
messages. It's always worked. Is this what you're
referring to?
If you want to access other MIDI ports than the
first with a device file,
you have to load the snd-virmidi driver, which will
give you some virtual
MIDI ports, and to connect these ports to the 8x8's
ports with aconnect.
Yes, that confirmed my other conclusion and this is
pretty darned cool.
ron
HTH
Clemens
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
27 May
27 May
9:12 a.m.
R Parker wrote:
No, dd doesn't use the ALSA library.
The ALSA library hides the device files behind device names. Instead of
accessing the ALSA device files directly, you are supposed to use some
program which uses the ALSA library.
There is an ugly test program which can display the data from an ALSA
rawmidi port in the alsa-lib/test directory. Please go there, run "make
rawmidi", and start it with
./rawmidi -v -i hw:1,x
HTH
Clemens
--- Clemens Ladisch <clemens(a)ladisch.de> wrote:
Well, what I said earlier isn't entirely correct, accessing
/dev/snd/midiC1D0 will open the first free port. Connecting ports will
open them, so the first free port in your case was probably Port 8.
And when you connect port x to port 0, data from the device at port x will
be written to port 0, but you won't be able to read it from port 0 because
MIDI Out 1 and MIDI In 1 are different ports.
I think you really need virmidi to do what you want.
Please add the following lines (or modify them) in your modules.conf:
options snd cards_limit=3
alias snd-card-2 snd-virmidi
alias snd-slot-2 snd-card-2
options snd-virmidi index=2
then connect the desired ports of the 8x8 to port 80:0, and then the
incoming data should be available at /dev/midi02.
R Parker wrote:
After examining things a little closer, your reply
confirms my conclusion.
I think there's something wrong because no data is
making it to the /dev/snd/midiC1D0 file.
For demonstration, I've connected everything:
...
With this scenario anything that comes in port_N,8
should be seen in the file /dev/snd/midiC1D0. Am I
right? I still don't understand where the usb-midi
i/o
device is.
...
There's no messages passing through
/dev/snd/midiC1D0
This file handles all nine ports. The ALSA library
uses a magic IOCTL to
select the desired port; when you access the file
directly, you get the
first port only. If possible,
you should use a program that can
access MIDI ports via the
ALSA library (the 8x8's ports would be named
"hw:1,x", x = 0..8).
I've always used dd to see check for incoming mmc
messages. It's always worked. Is this what you're
referring to?
8:10 p.m.
Hi Clemens,
Before I reply below; with your instructions which due
to my lack of familiarity I only partially grasp, I've
configured a setup where Input ports are working but
the output ports aren't open/opening.
The output ports in this simple setup are used to
transmit MTC generated by Ardour back to the mixing
consol (Tascam DM-24) in order to sync the Ardour and
DM-24 transports.
To be half way there is very encouraging. Anyway, I'll
reply to your suggestions below.
--- Clemens Ladisch <clemens(a)ladisch.de> wrote:
Well, what I said earlier isn't entirely correct,
accessing
/dev/snd/midiC1D0 will open the first free port.
Connecting ports will
open them, so the first free port in your case was
probably Port 8.
And when you connect port x to port 0, data from the
device at port x will
be written to port 0, but you won't be able to read
it from port 0 because
MIDI Out 1 and MIDI In 1 are different ports.
Here's what I've got and you'll notice "Output: NONE".
I've been staring at all this for awhile and am not
improving my understanding.
./rawmidi -v -i hw:3,0 -I /dev/snd/midiC3D0
Using:
Input: device hw:3,0
Output: NONE
snd_rawmidi_open hw:3,0 failed: -2
Read midi in
Press ctrl-c to stop
read f0
read 7f
read 01
read 06
read 01
read f7
The "read:_N" are an mmc stop instruction. BTW,
'ctrl-c' fails to exit rawmidi, I have 'kill...'.
Anyway, at this point I need a device with both the
Input and Outputs that are open.
The ALSA library hides the device files behind
device names. Instead of
accessing the ALSA device files directly, you are
supposed to use some
program which uses the ALSA library.
Does this apply to applications? If yes, then Ardour
accessing the Alsa device="/dev/snd/midiC3D0" directly
should be changed to use the Alsa library. Yes, no?
There is an ugly test program which can display the
data from an ALSA
rawmidi port in the alsa-lib/test directory. Please
go there, run "make
rawmidi", and start it with
./rawmidi -v -i hw:1,x
It's telling us a story. :)
I appreciate all the help,
ron
HTH
Clemens
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
9:23 p.m.
Clemens,
Disreguard the previous message. I had a cable problem
and the system is now working.
Gotta run, session just walked in,
ron
--- Clemens Ladisch <clemens(a)ladisch.de> wrote:
R Parker wrote:
Well, what I said earlier isn't entirely correct,
accessing
/dev/snd/midiC1D0 will open the first free port.
Connecting ports will
open them, so the first free port in your case was
probably Port 8.
And when you connect port x to port 0, data from the
device at port x will
be written to port 0, but you won't be able to read
it from port 0 because
MIDI Out 1 and MIDI In 1 are different ports.
I think you really need virmidi to do what you want.
Please add the following lines (or modify them) in
your modules.conf:
options snd cards_limit=3
alias snd-card-2 snd-virmidi
alias snd-slot-2 snd-card-2
options snd-virmidi index=2
then connect the desired ports of the 8x8 to port
80:0, and then the
incoming data should be available at /dev/midi02.
No, dd doesn't use the ALSA library.
The ALSA library hides the device files behind
device names. Instead of
accessing the ALSA device files directly, you are
supposed to use some
program which uses the ALSA library.
There is an ugly test program which can display the
data from an ALSA
rawmidi port in the alsa-lib/test directory. Please
go there, run "make
rawmidi", and start it with
./rawmidi -v -i hw:1,x
HTH
Clemens
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
--- Clemens Ladisch <clemens(a)ladisch.de>
wrote:
> R Parker wrote:
> > I still don't understand where the usb-midi
i/o
> device is.
> > ...
> > There's no messages passing through
> /dev/snd/midiC1D0
>
> This file handles all nine ports. The ALSA
library
> uses a magic IOCTL to
> select the desired port; when you access the
file
directly,
you get the
first port only.
After examining things a little closer, your reply
confirms my conclusion.
I think there's something wrong because no data is
making it to the /dev/snd/midiC1D0 file.
For demonstration, I've connected everything:
...
With this scenario anything that comes in port_N,8
should be seen in the file /dev/snd/midiC1D0. Am I
right? If
possible, you should use a program that can
access MIDI ports via the
ALSA library (the 8x8's ports would be named
"hw:1,x", x = 0..8).
I've always used dd to see check for incoming mmc
messages. It's always worked. Is this what you're
referring to?
26 May
26 May
5:57 p.m.
Hi Clemens,
Just some added information. We connected a Kurzweil
K2000R to the 8x8 port 7 and are able to control
information going to that device. So the routing
aspects are working. It's just the /dev/snd/midiC1D0
file that's not happening.
ron
--- Clemens Ladisch <clemens(a)ladisch.de> wrote:
R Parker wrote:
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
I still don't understand where the usb-midi
i/o
device is.
...
There's no messages passing through
/dev/snd/midiC1D0
This file handles all nine ports. The ALSA library
uses a magic IOCTL to
select the desired port; when you access the file
directly, you get the
first port only.
If possible, you should use a program that can
access MIDI ports via the
ALSA library (the 8x8's ports would be named
"hw:1,x", x = 0..8).
If you want to access other MIDI ports than the
first with a device file,
you have to load the snd-virmidi driver, which will
give you some virtual
MIDI ports, and to connect these ports to the 8x8's
ports with aconnect.
HTH
Clemens
6:04 p.m.
Hi,
Sorry to flood all this into lau. Maybe it's not the
right list?
Anyway
crw-rw---- 1 root audio 116, 40 Dec 31
1969 midiC1D0
I'm using a capabilities patched kernel and running as
a regular user but my user is a listed member or audio
group:
audio::18:parker,studio
Well, that was just a hunch that doesn't seem to be
going anywhere. I'll sort that out later, got some
other work to do.
ron
--- R Parker <rtp405(a)yahoo.com> wrote:
Hi Clemens,
Just some added information. We connected a Kurzweil
K2000R to the 8x8 port 7 and are able to control
information going to that device. So the routing
aspects are working. It's just the /dev/snd/midiC1D0
file that's not happening.
ron
--- Clemens Ladisch <clemens(a)ladisch.de> wrote:
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
R Parker wrote:
will
I still don't understand where the usb-midi
i/o
device is.
...
There's no messages passing through
/dev/snd/midiC1D0
This file handles all nine ports. The ALSA library
uses a magic IOCTL to
select the desired port; when you access the file
directly, you get the
first port only.
If possible, you should use a program that can
access MIDI ports via the
ALSA library (the 8x8's ports would be named
"hw:1,x", x = 0..8).
If you want to access other MIDI ports than the
first with a device file,
you have to load the snd-virmidi driver, which give you some virtual
MIDI ports, and to connect these ports to the
8x8's
ports with aconnect.
HTH
Clemens
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
7854
days inactive
7856
days old
linux-audio-user@lists.linuxaudio.org
10 comments
2 participants
participants (2)
-
Clemens Ladisch -
R Parker