Windows "default" Midi In port problem about nuked-sc55

[nukeykt]

Added command line option to specify midi port until config file support is added. See readme for details

[Kappa971]

I'm using Coolsoft MIDI Mapper with Loopmidi and it works as expected (the port is called Sound Canvas VA because I was using it for SCVA 😁) and I have a Sound Blaster X-Fi Titanium HD

Maybe it's not the same thing? I'm testing the emulator with Falcosoft MIDI Player.

[Falcosoft]

Maybe it's not the same thing? I'm testing the emulator with Falcosoft MIDI Player.

Coolsoft Midi Mapper has nothing to do with Midi In ports. It can only set the default Midi Out port.
It seems your first (0) Midi In port is a LoopMidi port. Somehow your hardware Midi in port is not the 1st one.
What does Falcosoft MIDI Player (x64) settings dialog show on the Midi In part? I mean this part:

Maybe your Sound Blaster's 64-bit Midi In port is not installed?

[Kappa971]

Coolsoft Midi Mapper has nothing to do with Midi In ports. It can only set the default Midi Out port. It seems your first (0) Midi In port is a LoopMidi port. Somehow your hardware Midi in port is not the 1st one. What does Falcosoft MIDI Player (x64) settings dialog show on the Midi In part? I mean this part:

Maybe your Sound Blaster's 64-bit Midi In port is not installed?

I only have Loopmidi as Midi IN port. The X-Fi Ti HD is from 2011, it plays midi but it doesn't seem to have midi input ports, only output ports:

Now I understand, you're probably using a Sound Blaster that's much older than mine.

[Falcosoft]

Added command line option to specify midi port until config file support is added. See readme for details

Hi,
Thanks for the fast update. I would like to report that the update works but it is somewhat misleading that it still always reports the name of port 0 as opened port regardless of the command line argument and the really opened (right) port.

[markanini]

Added command line option to specify midi port until config file support is added. See readme for details

Hi, Thanks for the fast update. I would like to report that the update works but it is somewhat misleading that it still always reports the name of port 0 as opened port regardless of the command line argument and the really opened (right) port.

Thanks for pointing out this quirk, it confused the heck out of me.