2 Oct
2007
2 Oct
'07
2:23 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, Oct 02, 2007 at 08:00:47AM -0400, Dave Phillips wrote:
drew Roberts wrote:
OK, this is what is confusing me. When I do as above, I get this:
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
client 14: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
client 16: 'FastTrack Pro' [type=kernel]
0 'FastTrack Pro MIDI 1'
client 20: 'Virtual Raw MIDI 1-0' [type=kernel]
0 'VirMIDI 1-0 '
client 21: 'Virtual Raw MIDI 1-1' [type=kernel]
0 'VirMIDI 1-1 '
client 22: 'Virtual Raw MIDI 1-2' [type=kernel]
0 'VirMIDI 1-2 '
client 23: 'Virtual Raw MIDI 1-3' [type=kernel]
0 'VirMIDI 1-3 '
In /dev, udev gives me stuff like:
crw-rw---- 1 root audio 14, 30 2007-10-02 09:17 /dev/admmidi1
crw-rw---- 1 root audio 14, 29 2007-10-02 09:17 /dev/amidi1
crw-rw---- 1 root audio 14, 9 2007-10-02 09:00 /dev/dmmidi
crw-rw---- 1 root audio 14, 25 2007-10-02 09:17 /dev/dmmidi1
crw-rw---- 1 root audio 14, 2 2007-10-02 09:00 /dev/midi
crw-rw---- 1 root audio 14, 18 2007-10-02 09:17 /dev/midi1
And in /dev/snd:
crw-rw---- 1 root audio 116, 0 2007-10-02 09:00 controlC0
crw-rw---- 1 root audio 116, 32 2007-10-02 09:17 controlC1
crw-rw---- 1 root audio 116, 8 2007-10-02 09:00 midiC0D0
crw-rw---- 1 root audio 116, 40 2007-10-02 09:17 midiC1D0
crw-rw---- 1 root audio 116, 41 2007-10-02 09:17 midiC1D1
crw-rw---- 1 root audio 116, 42 2007-10-02 09:17 midiC1D2
crw-rw---- 1 root audio 116, 43 2007-10-02 09:17 midiC1D3
crw-rw---- 1 root audio 116, 16 2007-10-02 09:00 pcmC0D0p
crw-rw---- 1 root audio 116, 25 2007-10-02 09:00 pcmC0D1c
crw-rw---- 1 root audio 116, 17 2007-10-02 09:00 pcmC0D1p
crw-rw---- 1 root audio 116, 1 2007-09-28 23:37 seq
crw-rw---- 1 root audio 116, 33 2007-09-28 23:37 timer
I can't make sense out of which of those ALSA (QJACKCtl) ports maps to which device in
the /dev tree! And, specifically, which one is /dev/midi, to which the Atari/steem is
connected? That's really the only missing peice for me: where do those wires lead to
exactly?
- -ken
On Monday 01 October 2007 10:19 pm, Ken Restivo
wrote:
Hi drew, hi Ken,
Here's how I do it:
Start Xsteem.
Open the Options/Ports dialog.
Select MIDI Port Device from the drop-down Connect-to menu.
Manually add /dev/midi or click on the Choose button and add whatever
device you like (this isn't working correctly, so I just write in the
portname).
I have three sound devices in my JAD system, including virmidi in card
slot #2 (from base #0). Thus, I connect to /dev/snd/midiC2D0. Make sure
you check the input/output boxes and the Open button (it doesn't look
like a button) in the Xsteem Options/Ports window.
drew was right, just do 'modprobe snd-virmidi' and that should add four
virtual MIDI ports that will instantly appear in the MIDI Connections
panel of QJackCtl.
Let me know if you need further help with Xsteem. And be sure to check
out the loads of cool apps at TAMW.
It looks like steem will access /dev/midi or any
OSS-style /dev/something
MIDI port, however. So I'm almost there. I just need to figure out how to
get a /dev/midi kind of device to show up in aconnect, then I can play the
song on EditTrack in the virtual Atari, and use aseqdump to capture it on
Linux.
I've messed around with virmidi, etc, but haven't figured out how to do
this though. Is there any way to create a bridge between a /dev/device
that
will show up as an ALSA sequencer port in aconnect/QjackCtl?
On some of my boxes, I run this way:
modprobe snd-seq-oss
modprobe snd-virmidi
qjackctl
make sure Connect is selected
choose the midid tab
You should see the virmidi devices even before actuallt starting jack in
qjackctl. Do the ports from the Atari program show up there?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHAnA8e8HF+6xeOIcRArvvAKC0hFUAPTFtvIpoptTIQu0jrjhtNwCg3I9v
X8G9JtCDechLGavHBcUkmXo=
=KzfJ
-----END PGP SIGNATURE-----