Skip to content
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

[BUG][App Compat] MidiOX "There is no driver installed" Errors on x64 Windows, and then bugcheck #516

Open
Psychlist1972 opened this issue Feb 5, 2025 · 2 comments
Assignees
Labels
area-transports 🚌 General transports like USB, BLE, Network, etc. area-windows-internal 🪟 Related to internal (not in the repo) Windows fixed-awaiting-public-release 🕙 Fixed in our internal builds. Waiting to make its way to a public release.

Comments

@Psychlist1972
Copy link
Contributor

Release
Customer Preview 1
Canary 27788

When starting up MIDI-OX, I receive the following:

Image

I clicked through 35 or so instances of that dialog, approximately corresponding to the number of Get Dev Caps errors reported by MidiDiag. It appears that MIDI-OX is throwing up the dialog on every failure return code in the non-contiguous WinMM Port indexes.

After that, when I clicked on number 36 or 37, my PC green screened with DPC_WATCHDOG_VIOLATION. I'm used to that from my old and failing MOTU 24 I/O.

I repeated this after restart, and had exactly the same thing happen, including the green screen.

The green screen does appear to be coming from the MOTU. Super odd that it's being triggered by this, though.

Image

Image

mididiag-2025-02-05.txt

@Psychlist1972 Psychlist1972 added area-transports 🚌 General transports like USB, BLE, Network, etc. area-windows-internal 🪟 Related to internal (not in the repo) Windows bug 🐞 Something isn't working labels Feb 5, 2025
@Psychlist1972 Psychlist1972 self-assigned this Feb 5, 2025
@Psychlist1972
Copy link
Contributor Author

Psychlist1972 commented Feb 9, 2025

Documenting this here, but for the dialogs to go away, MIDI-OX would need to change their code to not display an error for an inactive port number. There's no reason to display that for each port.

@Psychlist1972 Psychlist1972 added wontfix This will not be worked on. We hate doing this, but sometimes it's necessary. and removed bug 🐞 Something isn't working labels Feb 9, 2025
@Psychlist1972 Psychlist1972 changed the title [BUG][WinMM App Compat] MidiOX Errors on x64 Windows [BUG][WinMM App Compat] MidiOX "There is no driver installed" Errors on x64 Windows Feb 9, 2025
@Psychlist1972 Psychlist1972 changed the title [BUG][WinMM App Compat] MidiOX "There is no driver installed" Errors on x64 Windows [BUG][App Compat] MidiOX "There is no driver installed" Errors on x64 Windows Feb 9, 2025
@Psychlist1972 Psychlist1972 removed the wontfix This will not be worked on. We hate doing this, but sometimes it's necessary. label Feb 9, 2025
@Psychlist1972 Psychlist1972 changed the title [BUG][App Compat] MidiOX "There is no driver installed" Errors on x64 Windows [BUG][App Compat] MidiOX "There is no driver installed" Errors on x64 Windows, and then bugcheck Feb 9, 2025
@Psychlist1972
Copy link
Contributor Author

We are going to go back to using contiguous port numbering, which should fix the "no driver" errors during initial enumeration in MIDI-OX

@Psychlist1972 Psychlist1972 added the fixed-awaiting-public-release 🕙 Fixed in our internal builds. Waiting to make its way to a public release. label Feb 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-transports 🚌 General transports like USB, BLE, Network, etc. area-windows-internal 🪟 Related to internal (not in the repo) Windows fixed-awaiting-public-release 🕙 Fixed in our internal builds. Waiting to make its way to a public release.
Projects
Status: No status
Development

No branches or pull requests

1 participant