Bitwig seems to be immune to the "Win 11 KB5077241 Update dread"

[pboy]

Hi,
I'm glad that Bitwig doesn't go down with the current Windows update, like Cubase and Nuendo. Does someone have an idea what makes Bitwig stay clear? Must be something code-related, I guess?

[Milkman]

Ahhhhh what?? I havent allowed any updates in about 2 weeks, and at the moment my C15 works.....
Im not seeing media coverage of this, and I keep finding the same issue... from 2023, lol. Do you have any other info on this? Thanks.

Edit: is it the "makes all MIDI devices disappear" thing?

[pboy]

Ahhhhh what?? I havent allowed any updates in about 2 weeks, and at the moment my C15 works.....
Im not seeing media coverage of this, and I keep finding the same issue... from 2023, lol. Do you have any other info on this? Thanks.

Edit: is it the "makes all MIDI devices disappear" thing?

Yes, I guess so. For me Cubase and Nuendo do graphically display that external MIDI input is received but that MIDI never reaches the selected/record enabled track. The data stream is broken somewhere in the DAW. Below is a link to a long VI forum discussion:
https://vi-control.net/community/thread ... ar.170478/

[Milkman]

I have had at least one event where I started BWS (beta 6 and retail 6) where I started up a working project, and I immediately got the cascade of "midi device not available" for ALL midi devices. I just closed the program, reopened it and the issue was resolved. Ill test C15 later.

[drsyncenstein]

there are issues with some drivers for midi hardware (akai, korg) and virtual loopback devices like loopmidi and rtpmidi. if you have one of those issues it should affect al daws.
Issue list: https://devblogs.microsoft.com/windows- ... rkarounds/

Not sure if that is the right kb number btw