search

nukeykt / Nuked-SC55

Roland SC-55 series emulation
Other
286 stars 33 forks source link

Windows "default" Midi In port problem #5

Closed Falcosoft closed 3 months ago

Falcosoft commented 3 months ago

Hi, Actually on Windows there is no such thing as "default" Midi In port in the sense that you can select one in any way. Contrary to Midi Out ports where originally there was a built-in Midi mapper until Win 8 (and Coolsoft Midi Mapper on Win8+) to select the default Midi Out port there is no way (and never was) to select default Midi In port. Currently Nuked-SC55 always opens port 0 that can be a hardware port if you have a soundcard with hardware Midi In capabilities. It does not matter if you install LoopMidi or any other software loopback cables in such a system Midi In port 0 remains a hardware port. In such systems this recommendation from the Readme does not work:

to use it with the other applications use external MIDI pipe software (e.g. loopMIDI).

So it would be helpful if the Midi In port to be opened could be set some way (config file etc.)

image

Kappa971 commented 3 months ago

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

immagine

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

Falcosoft commented 3 months ago

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:

image

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

Kappa971 commented 3 months ago

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:

image

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:

immagine

immagine

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

nukeykt commented 3 months ago

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

Falcosoft commented 3 months ago

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.

image

markanini commented 2 months ago

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.

image

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