ahlstromcj/sequencer64

PortMidi host error: [4]

Merthurian opened this issue · 9 comments

Merthurian commented

Getting this error when opening the program on Win10:

"PortMidi host error: [4] 'The specified device is already in use. Wait until it is free, and then try again.' "

When I acknowledge the error dialog, the program crashes.

No other programs are running that could be tying up my midi devices. Which are a UMX-49 Keyboard and a Yamaha Motif Rack.

ahlstromcj commented
Merthurian commented

Thanks for the advice. I generated the log file as described in the PDF and here is the result:

qpseq64 
C:/Users/Dan/AppData/Local/sequencer64/virtualmidi.log 
2019-09-19 00:36:08 
PortMidi host error: [4] 'The specified device is already in use.  Wait until it is free, and then try again.'
PortMidi MMSystem 0: Microsoft MIDI Mapper output opened
PortMidi MMSystem 1: 2- Fast Track Ultra External input closed
PortMidi MMSystem 2: Yamaha MOTIF-R-1 input closed
PortMidi MMSystem 3: UMX 49 input closed
PortMidi MMSystem 4: Microsoft GS Wavetable Synth output closed
PortMidi MMSystem 5: 2- Fast Track Ultra External output opened
PortMidi MMSystem 6: Yamaha MOTIF-R-1 output opened
PortMidi MMSystem 7: Yamaha MOTIF-R-2 output opened
PortMidi MMSystem 8: Yamaha MOTIF-R-3 output opened
PortMidi MMSystem 9: Yamaha MOTIF-R-4 output opened
PortMidi MMSystem 10: Yamaha MOTIF-R-5 output opened
PortMidi MMSystem 11: Yamaha MOTIF-R-6 output opened
PortMidi MMSystem 12: Yamaha MOTIF-R-7 output opened
PortMidi MMSystem 13: Yamaha MOTIF-R-8 output opened
PortMidi MMSystem 14: UMX 49 output opened
[Writing rc configuration C:\Users\Dan\AppData\Local\sequencer64\erroneous.rc]
[Writing user configuration C:\Users\Dan\AppData\Local\sequencer64\erroneous.usr]

I think I'm stuck now as the next step is to disable the "closed" devices in qpseq24.rc. I don't have this .rc file. If I'm understanding this correctly, the rc file will be generated the first time the program is run. Could the crash be happening before the file is created?

ahlstromcj commented
ahlstromcj commented
arpeggio1234 commented

I had the same issue.
I now use the 95.2 zipped one and it is working. But i see no midi-clock menu.
Hiw can i solve this.
Thanks for making this great seq64
Dian from the Netherlands

wallacewinfrey commented

I ran through the instructions in sequencer-64-manual.pdf, and am running v.0.96.6 on Windows 10 Build 2004 (OS Build 19041.264).

Prior to installation of VirtualMIDISynth, I got the message "PortMidi host error: [4] 'The specified device is already in use. Wait until it is free, and then try again.' "

After the installation of VirtualMIDISynth, I get the message "PortMidi host error: [5] 'The specified device is already in use. Wait until it is free, and then try again.' "

Attempting to set the bus from the command line doesn't change the behavior. Here's my log, which was run before and after installing VirtualMIDISynth:

qpseq64 
C:/Users/wwinfrey/AppData/Local/sequencer64/virtualmidi.log 
2020-05-29 18:58:42 
PortMidi host error: [0] 'Undefined external error.'
PortMidi host error: [3] 'Undefined external error.'
PortMidi MMSystem 0: Microsoft MIDI Mapper output closed
PortMidi MMSystem 1: Multiface Midi input closed
PortMidi MMSystem 2: loopMIDI Port input closed
PortMidi MMSystem 3: Microsoft GS Wavetable Synth output closed
PortMidi MMSystem 4: Multiface Midi output opened
PortMidi MMSystem 5: loopMIDI Port output opened
[Writing rc configuration C:\Users\wwinfrey\AppData\Local\sequencer64\erroneous.rc]
[Writing user configuration C:\Users\wwinfrey\AppData\Local\sequencer64\erroneous.usr]

qpseq64 
C:/Users/wwinfrey/AppData/Local/sequencer64/virtualmidi.log 
2020-05-31 03:31:55 
PortMidi host error: [3] 'The specified device is already in use.  Wait until it is free, and then try again.'
PortMidi host error: [5] 'The specified device is already in use.  Wait until it is free, and then try again.'
PortMidi MMSystem 0: Microsoft MIDI Mapper output opened
PortMidi MMSystem 1: Multiface Midi input closed
PortMidi MMSystem 2: loopMIDI Port input closed
PortMidi MMSystem 3: CoolSoft MIDIMapper output closed
PortMidi MMSystem 4: Microsoft GS Wavetable Synth output opened
PortMidi MMSystem 5: VirtualMIDISynth #1 output closed
PortMidi MMSystem 6: Multiface Midi output opened
PortMidi MMSystem 7: loopMIDI Port output opened
[Writing rc configuration C:\Users\wwinfrey\AppData\Local\sequencer64\erroneous.rc]
[Writing user configuration C:\Users\wwinfrey\AppData\Local\sequencer64\erroneous.usr]
CliffRoberson commented

Having the same issue using 0.96.6 windows:
qpseq64 C:/Users/cliff/AppData/Local/sequencer64/virtualmidi.log 2020-08-09 19:16:24 pm_winmm_general_inputs(): no input devices PortMidi host error: [1] 'The specified device is already in use. Wait until it is free, and then try again.' PortMidi MMSystem 0: Microsoft MIDI Mapper output opened PortMidi MMSystem 1: Microsoft GS Wavetable Synth output closed [Writing rc configuration C:\Users\cliff\AppData\Local\sequencer64\erroneous.rc] [Writing user configuration C:\Users\cliff\AppData\Local\sequencer64\erroneous.usr]

CliffRoberson commented

@Merthurian @wallacewinfrey @ahlstromcj @arpeggio1234 As Merthurian was finding, I was not able to alter the qpseq64.rc file because it never got written when the app crashed before it opened. A hacky workaround I just figured out was to copy the qpseq64.rc and qpseq64.usr (not sure if the second one was necessary) from the data folder in the install to my C:\Users\cliff\AppData\Local\sequencer64\ directory. After copying those files the app at least launches without crashing and now I can hopefully do any configuration changes needed to get it working all the way.

ahlstromcj commented