Bitwig

Echoes in the Attic · Post by **Echoes in the Attic** » Thu Dec 16, 2021 2:44 pm

Still happening 4.1.2

neverbeeninariot · Post by **neverbeeninariot** » Fri Dec 17, 2021 2:38 pm

Yep, same issue here - Win 10 Bitwig 4.1.2 - first noticed it with Triple Cheese (for the KVR OSC), but not during the last NoiseMaker OSC, and now it's happening with other random plugins too

FatHedonist · Post by **FatHedonist** » Mon Dec 20, 2021 5:47 pm

I keep getting this error as well and I am on 4.1.2, last night I had 3 instrument tracks in session view with Serum basic patches and error was present for about 30 seconds then went away. Computer is a beast and the issue started with 4.1.1.

jkez · Post by **jkez** » Wed Dec 22, 2021 1:05 pm

I also get this error occasionaly. 4.1.1. and 4.1.2. Windows 11

duanosforde · Post by **duanosforde** » Fri Dec 24, 2021 10:36 pm

i get the error as well, I hit save and it goes away.

MegaPixel · Post by **MegaPixel** » Sat Dec 25, 2021 7:25 pm

4.1.2 still getting it.

Tested with new project created, single instance of kontakt even when not playing anything it pops up, kontaks still works fine but bitwig thinks otherwise. No issue on Studio One 5.x and FLStdio.

Greenstorm33 · Post by **Greenstorm33** » Sat Dec 25, 2021 9:07 pm

Seems like it's happening to almost everyone. They obviously borked something with the way the audio engine works and I imagine it will be fixed in the next minor release.

pdxindy · Post by **pdxindy** » Sat Dec 25, 2021 11:32 pm

Greenstorm33 wrote: Sat Dec 25, 2021 9:07 pm Seems like it's happening to almost everyone. They obviously borked something with the way the audio engine works and I imagine it will be fixed in the next minor release.

Yeah... lots of people getting it... windows only. Not happening on Mac.

moss · Post by **moss** » Sun Dec 26, 2021 1:46 pm

I asked about this: it will be fixed in the next update. The error reports are correct but actually triggered by a so far hidden bug in the audio engine.
And yes, only happens on Windows.

tshear23 · Post by **tshear23** » Mon Dec 27, 2021 3:38 am

Weird, because I'm on a Mac and I'm getting it.

pdxindy · Post by **pdxindy** » Mon Dec 27, 2021 5:18 am

tshear23 wrote: Mon Dec 27, 2021 3:38 am Weird, because I'm on a Mac and I'm getting it.

Interesting... what OS version?

bite_me · Post by **bite_me** » Mon Dec 27, 2021 7:48 am

When I disabled and then enabled the audioengine, every 3rd party synthplugin was initialized. Bad - after some hours of editing... Bitwig 4.1.0 Win10

MegaPixel · Post by **MegaPixel** » Mon Dec 27, 2021 8:05 am

bite_me wrote: Mon Dec 27, 2021 7:48 am When I disabled and then enabled the audioengine, every 3rd party synthplugin was initialized. Bad - after some hours of editing... Bitwig 4.1.0 Win10

Ye, same happened to me. It crashed every plugin that was open, not just the supposed "un-named" one that had stopped responding, and then on restarting them it restored them to their original states...

Just ignore the message, keep using things, it often goes away from doing various things and comes back, just keep saving often just encase...

tshear23 · Post by **tshear23** » Mon Dec 27, 2021 3:10 pm

I'm on Big Sur (11.6)

pdxindy · Post by **pdxindy** » Mon Dec 27, 2021 3:28 pm

tshear23 wrote: Mon Dec 27, 2021 3:10 pm I'm on Big Sur (11.6)

Monterey and Apple Silicon Mac... I have not had that message and the people who have reported it have been on Windows.

Have you been getting that message a lot? With different plugins?

Bitwig

KVR Audio

Why do I keep getting "Plug-in host is not responding" message