Hi,
Zitat von derek holzer derek@x-i.net:
thomas gorbach wrote:
Following problem i have with midi and pd.
starting pd i get following midi information:
device -1: tried /dev/midi-01 READ/WRITE; returned -1 device -1: tried /dev/midi-1 READ/WRITE; returned -1 device -1: tried /dev/midi-01 READONLY; returned -1 device -1: tried /dev/midi-1 READONLY; returned -1 couldn't open MIDI input device -1 device -1: tried /dev/midi-01 WRITEONLY; returned -1 device -1: tried /dev/midi-1 WRITEONLY; returned -1 couldn't open MIDI output device -1 opened 0 MIDI input device(s) and 0 MIDI output device(s).
doing cat /proc/asound/cards i get:
0 [Digi9652 ]: RME9652 - RME Digi9652 RME Digi9652 at 0xe0000000, irq 9 1 [VirMIDI ]: VirMIDI - VirMIDI Virtual MIDI Card 1
with "aconnect -i" i get: client 0: 'System' [type=kernel] 0 'Timer ' 1 'Announce ' client 72: 'Virtual Raw MIDI 1-0' [type=kernel] 0 'VirMIDI 1-0 ' client 73: 'Virtual Raw MIDI 1-1' [type=kernel] 0 'VirMIDI 1-1 ' client 74: 'Virtual Raw MIDI 1-2' [type=kernel] 0 'VirMIDI 1-2 ' client 75: 'Virtual Raw MIDI 1-3' [type=kernel] 0 'VirMIDI 1-3 '
So the drivers seem to be ok.
No, they seem not. Your Soundblaster card doesn't show up at all, the only thing that's there is the Virmidi Card. There seems to be something messed up with the module configuration. Could you post your /etc/modules.conf (supposed you're running kernel 2.4)?
But how can i tell pd the aktiv midi Device ?
cat /dev/midi01
is the only device that is aktiv.
Well, it isn't active in ALSA. Still, to use /dev/midi01 in Pd, you probably have to start Pd with "pd -mididev 2". Pd uses the device one less than what was issued on the command line. So "-mididev 2" lets Pd use midi01 (because: 2 - 1 = 1)
ciao
Frank Barknecht _ ___footils.org_