Bitwig - Plugin Crash Protection - Interesting and Projectsaver?

[Caine123]

i just got back from SUPERBOOTH in berlin and i checked out some DAWs there as well, FL STUDIO is for me still the best looking and no DAW could get my attention asap, but they seem to need a bit more time to get in their workflow, which is not bad could be nice but at a booth u cannot demo too much so back to topic:

-Bitwig emplees explained to me the "Plugin Crash Protection" will still load a projct EVEN if it has problems with some plugin/s, this would be GODSEND!

afaik FL Studio doesnt have something like that and sadly MANY projects crash on me and sometimes i dont have older versions from those projects to re-load correctly so projects are lost before sending to IL.

did you try it? is IL planning this?

and @BITWIG Users, is it really working? in theory it sounds fantastic and saving ours but theoretically

[tooneba]

is IL planning this?

FWIW FL's Bridged VST channels are processed in each processes. You can check 'ilbridge' in Task Manager You can do it through VST Wrapper Setting > Processing > Make Bridged. I don't know it is contributing to reducing host crash thought.

[pdxindy]

and @BITWIG Users, is it really working? in theory it sounds fantastic and saving ours but theoretically

Yes, it really works

[Reefius]

The question is: what is the point of it? It will not make crappy plugins run stable. If a plugin causes crashes, stop using it.

It also prevents some plugins to work properly, like plugins that need to communicate with each other.

I prefer Live's crash recovery system over sandboxed plugins.

[Caine123]

The question is: what is the point of it? It will not make crappy plugins run stable. If a plugin causes crashes, stop using it.

It also prevents some plugins to work properly, like plugins that need to communicate with each other.

I prefer Live's crash recovery system over sandboxed plugins.

in fl studio when a plugin crashes in the middle of a SAVED project you cannot reload the project anymore. if you didnt made many step saves and versions of this project you are pretty lost then

i check DAWs with the ability? to still load a project and reporting? the plugin which crashed it so you can find out which one crashed it in the first place and sort out or show the devs.

[pdxindy]

The question is: what is the point of it? It will not make crappy plugins run stable. If a plugin causes crashes, stop using it.

It also prevents some plugins to work properly, like plugins that need to communicate with each other.

I prefer Live's crash recovery system over sandboxed plugins.

For me, Bitwig rarely ever crashes. Sometimes an individual plug-in crashes and then I immediately know which one. No more hunting to figure out which plug-in is causing the problem. Sometimes a top quality plugin crashes. Sometimes I find a new bug with that plug-in. It is fast to keep trying things without crashing Bitwig and that particular project, so it is much easier to troubleshoot any specifics of why it is happening and then pass on that info to the developer.

I had one plugin that only had a problem with a specific feature and only at 96khz. Once I passed that info along to the plug-in developer, a fix was found fast and problem gone. I would never have figured that out if the DAW was crashing every time I tried some variation. It feels so smooth and elegant to just have that plugin softly disabled instead of the whole project and app gone.

The plug-in in crash protection in Bitwig is one of my favorite features. Also, you can designate individual plug-ins to not be sandboxed if they need to communicate with other instances of the same plug-in.