I was using an Evolution UC-16 midi controller connected to a USB port with winXP and PD 0.36 without any problems. I started using PD 0.37-test 6 and get the following message when PD loads :
midi input enabled; warning, don't close the DOS window directly! could not open midi input device number 1: PortMidi:
Invalid device ID' could not open midi output device number -1: PortMidi:Invalid device ID' 12 audio buffers
with the following pd.bat :
@echo off cd bin pd -midiindev 1 -path ...
I still have 0.36 loaded, and I verified that the midi controller works fine, but using the same pd.bat, it doesn't work with 0.37. Is there something I'm missing here??
bradKLIGERMAN
Brad KLIGERMAN schrieb:
midi input enabled; warning, don't close the DOS window directly! could not open midi input device number 1: PortMidi:
Invalid device ID' could not open midi output device number -1: PortMidi:Invalid device ID' 12 audio buffersIs there something I'm missing here??
It seems the MIDI device IDs have changed. Try -listdev flag to find out which numbers your MIDI devices have. I think this is because Pd now uses PortMidi.
Olaf
I used the [-listdev] flag with PD 0.37 test 6 and received the expected :
audio input device #1: YAMAHA AC-XG WDM Audio audio output device #1: YAMAHA AC-XG WDM Audio 0: MMSystem, Mappeur MIDI Microsoft (output) 1: MMSystem, UC-16 USB MIDI In (input) 2: MMSystem, SynthĂ. SW table de sons GS Mic (output) 3: MMSystem, UC-16 USB MIDI Out (output)
Then on a whim, I added the [-midiindev 1] flag behind the [-listdev] : ( PD.bat):
@echo off cd bin pd -listdev -midiindev 1 -path...
and the midi device is working fine. I cannot say that I understand why, but --problem solved.
Thanks /brad.
Olaf Matthes wrote:
Brad KLIGERMAN schrieb:
midi input enabled; warning, don't close the DOS window directly! could not open midi input device number 1: PortMidi:
Invalid device ID' could not open midi output device number -1: PortMidi:Invalid device ID' 12 audio buffersIs there something I'm missing here??
It seems the MIDI device IDs have changed. Try -listdev flag to find out which numbers your MIDI devices have. I think this is because Pd now uses PortMidi.
Olaf
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
Last I checked .37 had problems with MIDI in Windows. So use .36
until they're fixed.
David
At 16:25 24/07/2003, Brad KLIGERMAN wrote:
I was using an Evolution UC-16 midi controller connected to a USB port with winXP and PD 0.36 without any problems. I started using PD 0.37-test 6 and get the following message when PD loads :
midi input enabled; warning, don't close the DOS window directly! could not open midi input device number 1: PortMidi:
Invalid device ID' could not open midi output device number -1: PortMidi:Invalid device ID' 12 audio bufferswith the following pd.bat :
@echo off cd bin pd -midiindev 1 -path ...
I still have 0.36 loaded, and I verified that the midi controller works fine, but using the same pd.bat, it doesn't work with 0.37. Is there something I'm missing here??
bradKLIGERMAN
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
. . David McCallum . Music wants to be free . http://mentalfloss.ca/sintheta .
-
Brad KLIGERMAN -
David McCallum -
Olaf Matthes