New Windows insider update

[beatpete]

New Windows (insider) update screwed up all my virtual midi ports! 25H2 26220.7653

[Alan-Russell]

NEVER get involved with the Window insider betas when having CB 15 pro as your DAW..

[beatpete]

I agree but too late now!

[fese]

Roll back the update?

[beatpete]

Not possible unfortunately

[MrSoundman]

Something to do with this perhaps?

Cubase and MIDI 2.0

I’ve got a new Native Instruments Kontrol S49 Mk3, and I use Cubase Pro 15 on a MacBook Pro running OS 26.2. Cubase is supposed to be MIDI 2.0 compatible, but when I switched the Kontrol S49 Mk3 to MIDI 2.0, Cubase didn’t seem to want to behave. Is it too soon? Is Cubase not really ready? Or have I just failed to do something crucial in settings?

[beatpete]

I don’t think so. Fortunately, I managed to remove the Windows update came yesterday and everything’s back to normal.

[MrSoundman]

In what way did it screw up your virtual MIDI ports?

See this post:

Cubase and MIDI 2.0

Yep. Apple has had it for a while now. We had to rewrite our whole midi stack, so it took a bit longer. It’s going into retail Windows 11 releases starting the week after NAMM. It’ll take around 30 days to finish the rollout. Pete Microsoft

[beatpete]

Loop Midi disappeared completely and LoopBe30 had to be reinstalled and had less ports and completely different names. A real PITA!