Question

Dear PreSonus team,

Only one wish that will have huge impact on producer’s happiness:

Plugin sandboxing, so no plug-in is able to crash the whole project, or even stop the project’s audio.

Best,

Marko

Answer 1

Bump. I've just spent the last week trying to troubleshoot, diagnose, and fix an issue with a project refusing to open due to a plugin crash. I wouldn't have had to do that if S1 had some kind of plugin sandboxing or crash protection - or at the very least, a crash log somewhere that could indicate which plugin crashed.

Bitwig Studio has an excellent implementation of this, with the ability to decide to what extent plugins will be hosted separately from one another - whether by manufacturer, by plugin, or even by individual instance. PreSonus devs, please consider adding something like this!

Answer 2

Please for the love of god add this feature.

It's easily the best DAW feature I've ever found in any DAW so far, and Bitwig is the only one that does it properly.

Follow their lead.  It makes life so much better.

Answer 3

i would love this feature

Answer 4

This is the most important feature. People don't upvote because they don't know how darn important it is.
"It's not studio one crashing, it's 3rd party plugs" .... Nah.

Studio One watches plugin jump off a cliff
Studio One jumps off a cliff
Studio One support - ... PLUGINS FAULT!!!

Answer 5

Bump. This is a much needed QoL improvement.

Answer 6

I upgraded from Studio One 4 to version 6, hoping it would behave more stable. Negative.

I don't have that many plugins, but from time to time one decides to crash. Sometimes the AU version of the same plugin would crash, and the VST would work or the other way around. Sometimes I mis-click the wrong version and... session gone...

Might have to give Bitwig a try.