PlanetZ forums @ scopeusers.com

Hi,
Following (not sure what, new install or forced window update), the XITE MIDI is not showing up anymore in DAWs or Midi Ox. It is like it does n't exist. All worked fine a couple of days ago.

Not sure what happened, except that I had a forced windows 11 update that I can't seem to reverse, it is possible that this caused the bug ? I can't see what else could have done this.

I changed the modules in the project (midi seq source/dest) and I had a windows message about needing to add Midi Drivers and reboot (start xite/sdk in admin mode) but it did not change anything. Reinstalled the drivers from scratch, tried various things.

So in a way, the seq midi source in the project are seen by windows because it tells me that I have to add more drivers in the system (after deleting the drivers and reinstalling them), but they still don't show anywhere in any software (I have only studio one and midi Ox).

Any idea what to do ? I think it was discussed here previously but can't find the thread for a solution.

so I found that sonic core is listed in this page https://devblogs.microsoft.com/windows- ... rkarounds/

apparently I have this new midi stack as seen byt the checker found here https://aka.ms/midi (what is crazy is that all updates etc are off, so it shouldn't have updated itself....)

still not midi seq source/dest (or any other scope midi)

ok i give the solution that worked for me, as the published solution did not change anything.
this solution may have to be done once per session (ie at each reboot).

with Scope project loaded.
run service.msc
find Windows midi service, put it to manual start, then property "stop" (check on midi ox that all midi is off, ie not only scope)
then restart the window midi service manually: restart midi ox , all your midi stufdf should be here, including scope.

this is the only method that worked for me.
any way to make this permanent ?

win11 is really catastrophic...

You'll want to review the thread I am linking below that sites in the "Tech Talk" subforum.

Short version: Any device that can allocate MIDI Devices (rather than having a fixed number on instantiation by the API) was not correctly addressed as the MS team used PORTS rather than DEVICE to instantiate, and devices that are dynamic instantiate with 0 so they simply skip them by accident). Fix coming in April.

This issue is best handled in this thread, though interesting to note that the Xite does this too (I'm stuck on a previous version of Win11 due to an older CPU that they dropped compatibility for):

Midi 2.0 - Patch: KB5077181 (Wind0 and 26100.7840 for versions 25H2 and 24H2)

If this is really affecting all Xite users on a current Win11 build, I will move this thread into the Xite forum with confirmation so people can reference the above link to solve it until MS publishes a fix.

You can use this bat file to end and restart the midi service (change the .txt extension to .bat).

thanks guppy ! i wanted to do that but did not find the time.... so you saved me time.
the script works if the Window Midi Service is not off by default (and sekect "run as an admin).

@valis, I think it concerns.ed any Scope driver (basically xite and scope pci seq-source/dest work more or less the same).
I think windows rolled back the Midi 2 update but just in case it is needed in the future, I would search in "problem solving" first personnally.