search

microsoft / MIDI

Windows MIDI Services
MIT License
313 stars 26 forks source link

Canary Insider Preview 27744.rs_prerelease.241101-1329 is not compatible (was MIDI ports are not displayed on midi.exe.) #434

Open sat-okada opened 3 days ago

sat-okada commented 3 days ago

Describe the bug MIDI ports are not displayed on midi.exe.

To Reproduce 1.Update to the following versions of the Windows Insider Program (latest version of Canary channel) Windows 11 Pro Insider Preview Build 27744.rs_prerelease.241101-1329 2.Reboot the OS 3.Start the monitor with midi.exe

midi endpoint monitor --verbose

4.No endpoints are displayed. Image

Expected behavior Endpoints are displayed.

Installer Name or Version ・Windows.MIDI.Services.In-Box.Service.-.1.0.1-preview.7.24305.1438-x64.exe ・Windows.MIDI.Services.Tools.and.SDKs.1.0.1-preview.7.24305.1438-x64.exe

Desktop (please complete the following information): Windows 11 Pro Insider Preview Build 27744.rs_prerelease.241101-1329

Psychlist1972 commented 3 days ago

This is a known issue. I forget that not everyone is on Discord, where I posted a not about this build.

https://discord.com/channels/980245825202552942/980246206779383848/1305589346891731065

That canary build is not compatible with Windows MIDI Services DP releases. It contains an early test deployment of the MIDI Service/API and plugins. Build numbers below that, including those in the dev channel, will work.

I'll leave this issue open in case others run into it. I don't have a date/build # yet for the version that is compatible with the SDK.

sat-okada commented 1 day ago

I checked the other versions. 27749.rs_prerelease_241108-1425 is no good as well. 27729.rs_prerelease.241011-1428 is OK.

MusicMaker commented 1 day ago

For me, everything seems fine on 27749.1000 with DP7 services installed from git release It was automatic on line update by Insider (not installed from ISO)

midi ep monitor --verbose. Getting UMP packed form UMP device.

Image

Psychlist1972 commented 1 day ago

It looks like you will need at least 27751.1000.rs_prerelease.241112-1359

I'm working on instructions to de-register the in-box components and allow the install to complete.

MusicMaker commented 19 hours ago

Image Not sure where is 27751...

Psychlist1972 commented 12 hours ago

Image Not sure where is 27751...

It's working in your case because somehow the midisrv abstraction/transport registered for the DP, and the service is running. Not sure what order of operations permits that.

A couple things to check

  1. From the command line issue

sc qc midisrv

If the results point to the midisrv.exe in Program Files, you are running the DP version. If it points to one in System32, you are running the older one from the Insider build.

  1. Then open regedit and look here

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows MIDI Services\Transport Plugins

Anything with "Abstraction" in the name came from the Insider build. Anything with "Transport" came from the DP. There are probably duplicates there. The one that wins is the one that was registered last

Right now, mididiag doesn't produce a list of file locations for which COM components are being loaded, which makes it difficult for us to know what someone is running when on an insider build. I'm looking into what I can do there and also in the service.