Hi Tom,
I am CCing the PD list, although I think your problem is in the soundcard configuration.
thomas gorbach wrote:
Hi List,
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.
But how can i tell pd the aktiv midi Device ?
cat /dev/midi01
is the only device that is aktiv.
derek holzer schrieb:
Thomas,
try using the Media --> Midi Settings menu in the main PD window.
You should be able to use your RME after that. I get the same startup messages [almost], but can use my HDSP just fine after using the dialog.
good luck, D.
thomas gorbach wrote:
The RME card doesn't have midi. I use the soundblastercard for it. Configuration seems to be ok.
cat /proc/asound/cards 0 [Digi9652 ]: RME9652 - RME Digi9652 RME Digi9652 at 0xe0000000, irq 9 1 [VirMIDI ]: VirMIDI - VirMIDI Virtual MIDI Card 1
Sorry, I assumed that your RME card had MIDI because my HDSP card does...
But, if you are using a soundblaster for the MIDU, why does it not show up with cat /proc/asound/cards?
I see that you are using OSS for the MIDI... That's OK because PD hasn't been behaving at all with ALSA lately. But did you do any ALSA configuration to emulate OSS? If so, can you post your modules.conf file? I have a feeling you will need to set up the SoundBlaster as a soundcard in your modules.conf in order to use it as a MIDI device, and that you will need to properly emulate the OSS with ALSA to get it running. Just a guess, however...
If i do Media --> Midi Settings menu midiindev and midioutdev on OSS MIDI DEVICE #1 the configuration seems to be ok. pd message:
device -2: tried /dev/midi-02 READONLY; returned -1 device -2: tried /dev/midi-2 READONLY; returned -1 couldn't open MIDI input device -2 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). input channels = 2, output channels = 8 device 1: tried /dev/midi READ/WRITE; returned -1 device 0: tried /dev/midi00 READ/WRITE; returned -1 device 0: tried /dev/midi0 READ/WRITE; returned 11 opened 1 MIDI input device(s) and 1 MIDI output device(s).
But now with ctlin/ctlout midi is still not working.
What happens when you just use a [midiin] object? Do you get channel, controller of note numbers in?
best, derek