• Hi and welcome to the Studio One & Studio Pro User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by Fender. Learn more in the Welcome thread!

Win Midi 2 and updates in Device Manager

sintil8

Well-known member
Hiya all,
Just recently I have been seeing some minor glitches on my system that I couldn't catch or see what might be causing them.
These were minor things every now and then something would seem...well just off or judder then snap back.

I had a ferret around and ran some checks, anyway I have noticed a new entry in Device Manager which I assume is related to windows Midi 2 update!
I can recall reading somewhere that a forced update to windows was about to happen, in order to get the Midi 2 tools out.
I have updates on hold but did get an update???


midi 2 endpoints.png


A number of the ports are also listed in Sound, video and Game controllers lower down in the Device Manager tree.
I have found that if I disable LoopBe, virtual midi port tool my system is running a lot smoother.

Any of you folk using LoopBe or other virtual port software noticed anything similar?

Regards to all
 
I had a ferret around and ran some checks, anyway I have noticed a new entry in Device Manager which I assume is related to windows Midi 2 update!
I can recall reading somewhere that a forced update to windows was about to happen, in order to get the Midi 2 tools out.
I have updates on hold but did get an update???


View attachment 3862
This appeared with the MIDI 2.0 update in Feb 2026 - Build 10.0.26100/26200.8328.

It's all good here:

1786107204878.png


You say you have updates off - what do you see when you click Start and then type:

Winver

?

VP
 
Hiya VP,

I do have updates suspended, but have chosen not to use the registry hack, and yes I did roll back at one point.

This last one I have let live, as support for 24H2 is stopping in October.

Have you any info if those endpoints are active and grabbing the same ports listed in "Sound, Video and game controllers?

I have been playing with a small Video app by Imaginando called "Visual Studio" that runs some Lfo's etc. some glitching started with them resetting, whilst set to free running. The upshot is, if I exit LoopBe all runs as it should. I was also getting the play head in FSP on the odd occasion being a bit erratic?
As it seemed to be a very random thing I started taking bits of hardware and software off line. Exiting LoopBe seems to have solved it.

Oh, about the Win Vers. I'm way beyond that, now showing at .8875

I'm all good also. least I know how to work around this now.

Best of regards.
 
Hiya VP,

I do have updates suspended, but have chosen not to use the registry hack, and yes I did roll back at one point.

This last one I have let live, as support for 24H2 is stopping in October.

Have you any info if those endpoints are active and grabbing the same ports listed in "Sound, Video and game controllers?

I have been playing with a small Video app by Imaginando called "Visual Studio" that runs some Lfo's etc. some glitching started with them resetting, whilst set to free running. The upshot is, if I exit LoopBe all runs as it should. I was also getting the play head in FSP on the odd occasion being a bit erratic?
As it seemed to be a very random thing I started taking bits of hardware and software off line. Exiting LoopBe seems to have solved it.

Oh, about the Win Vers. I'm way beyond that, now showing at .8875

I'm all good also. least I know how to work around this now.

Best of regards.
This is the be-all and know-all thread about MIDI2 constantly monitored by Microsoft's Pete Brown who's in charge of MIDI at MS:


More recent entries discuss MIDI2, you can skip most of the humongous thread. Also search for Pete Brown elsewhere, he has a discord where he monitors people's experience with the new rollout and offers workarounds.

I can't give you a personal report on how the latest version of Win11 handles MIDI2 (though from scanning that thread it seems to have "cured" a lot of the growing pains from a few months ago) cause I'm a Win10 holdout.

I have been following Pete Brown forever and these days it's fairly incredible for a big corporation to allow a guy to speak so freely about products in development. MS gets a lot of grief and plenty of people can't wait to defect to Linux, but I have a lot of faith in Pete Brown to get it all sorted out. MS is also in the MIDI Association which Fender is conspicuously not a member of meaning FSP users will have a tougher go of things than, say, Cubase users since Steinberg is an active participant in the MIDI Association (as is , Apple, Google, Roland, Yamaha, Korg, Ableton, and so on).
 
Last edited:
Hiya MisterE,

I share similar thoughts you have, re Fender not being part of the Midi Association?
It is understandable tho' as the history of SO1 was a symbiosis with Presonus H/Ware mixers and sound cards. When you look at the long game it's understandable that Midi was not a top priority. SO1 had a built in control structure (control link) that was far simpler to use than the Midi protocol implementation used by CBase and others at that time. It's one of the things that pulled me into SO1, also drag and drop was dope at that time, (gettin down with the kids now:-)

Pete Brown, I get the announcements from his Discord server in my mail, so I also get to read what the Dev's are being supplied with.
If you know your way around Win's Terminal Server you can get info's/data output from both Midi1 and Midi2 endpoints and all sorts of jazzy features like feeding multiple outputs from a single source either Midi 1 or 2 output being understood/translated.
That last one for me says Midi inserts should be a no brainer, but then I'm no dev, so what do I know. :cautious:

At some point FSP may get dragged into the Midi 2 implementation or lose a lot of ground to the competitors that are on point or perhaps FSP gets Control Link Ver 2.0, maybe AI is the option for managing control mapping.

Anyway kindest regards.
 
Back
Top