-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows "default" Midi In port problem #5
Comments
Coolsoft Midi Mapper has nothing to do with Midi In ports. It can only set the default Midi Out port. 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. |
Added command line option to specify midi port until config file support is added. See readme for details |
Hi, |
Thanks for pointing out this quirk, it confused the heck out of me. |
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:
So it would be helpful if the Midi In port to be opened could be set some way (config file etc.)
The text was updated successfully, but these errors were encountered: