Why I have rolled back to Previous WIndows build - away from MIDI 2, a warning

Cubase
1

I have been having multiple MIDI issues with the latest WIN 11 build,
Expression maps not working, Automation not working, Linked groups not working, Loosing ports. It’s been so bad that I almost gave up entirely. So I range Steinberg. They advised that i rolled back to previous Windows build. They have said that a lot of people have contacted them with these types of issues, so I rolled back and set my system not to update for 5 weeks.
I asked Steinberg if they were issuing a fix, they said yes, but not in the next fix, the one after.

FYI

1 Like
2

Hello

I did the same, but I think Microsoft is also at fault and needs to release a fix, but not right away.

see this discussion

Loop MIDI Windows 11 25H2

3

Sadly all my problems are back

Z

4

Yes, that’s because your issues are not related to Midi 2.0.

There are several other threads going on in the forum right now about Midi 2.0 so if you have anything to say about it, go there.

Posting like this is just creating confusion where it’s really not needed at the moment.

2 Likes
5

I have 30 hardware midi synths in my studio and am only having issues with one app from one vendor (the synths work just fine).

Not only am I not having issues, everything is working far better than it used to.

Stuff that would only work properly if you stood on yout left middle toe while reciting the alphabet backwards now work perfect (im looking at you korg).

Microsoft folks have already stated that the one issue im having is known about and they were working on a fix before I even complained.

Overall everything is working a million times better for me….

So it sounds like you might have other issues, but your post is very short on specifics/details..

4 Likes
6

I think these crticism are fair. I posted with a solution, then found it was not. I shall sak to have this post taken down.
Z