Using QuteCsound 0.6.0-beta in Windows 7, I select my machine's MIDI I/O
driver (which is known to work) as the input device, and on attempting to
run the .csd I get this error in the Console:

PortMIDI: Activated input device 8: 'FW 410 MIDI' (MMSystem)
 *** PortMIDI: error opening input device 8: PortMidi: `Invalid device ID'
 *** error opening MIDI in device: -1 (Unknown MIDI error)

I'm pretty sure this input device was working a couple of weeks ago with
Csound, as I built a mapper program in QuteCsound to route MIDI input via
MIDI Yoke to a DAW.

Since then I had some of those nasty Windows problems, which required some
system diagnostics and stuff, but nothing that should affect a MIDI device,
especially given that the same device is still working with other software.

Can anyone suggest how I might be able to fix the problem?

Thanks!

--Jim Aikin

I get this problem with QuteCsound a bit on windows too. I usually
have to unplug my MIDI device and restart. In the end I just use
QuteCsound as an editor and work from the command line to run my
instruments, note that's not 'run in terminal' but a separate DOS
terminal. I don't know why the solution above even works as QuteCsound
is merely calling Csound, in just the same way I do from the command
line, but for some reason it works fine from the command line.

Rory.

On 4 July 2010 04:19, Jim Aikin  wrote:
>
> Using QuteCsound 0.6.0-beta in Windows 7, I select my machine's MIDI I/O
> driver (which is known to work) as the input device, and on attempting to
> run the .csd I get this error in the Console:
>
> PortMIDI: Activated input device 8: 'FW 410 MIDI' (MMSystem)
>  *** PortMIDI: error opening input device 8: PortMidi: `Invalid device ID'
>  *** error opening MIDI in device: -1 (Unknown MIDI error)
>
> I'm pretty sure this input device was working a couple of weeks ago with
> Csound, as I built a mapper program in QuteCsound to route MIDI input via
> MIDI Yoke to a DAW.
>
> Since then I had some of those nasty Windows problems, which required some
> system diagnostics and stuff, but nothing that should affect a MIDI device,
> especially given that the same device is still working with other software.
>
> Can anyone suggest how I might be able to fix the problem?
>
> Thanks!
>
> --Jim Aikin
>
> --
> View this message in context: http://old.nabble.com/PortMIDI-Error-tp29067194p29067194.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"