Plugin sandboxing in PatchWork?
-
- KVRian
- Topic Starter
- 710 posts since 20 Nov, 2000 from Valencia, Spain
Just curious... Is this feature on the roadmap for PatchWork? Is it technically feasible? I guess PatchWork, for its advanced hosting capabilities, would be a perfect candidate to have it as an extra layer of protection between the plugins and the DAW.
-
Blue Cat Audio Blue Cat Audio https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=39981 - KVRAF
- 5843 posts since 8 Sep, 2004 from Paris (France)
What do you exactly mean by "sandboxing"? Running the plug-ins in a separate process to acvoid crashing the DAW? That's definitely not optimal for DSP. If a plug-in is buggy, I'd rather not use it anyway, be it in a sandbox or not!
-
- KVRian
- Topic Starter
- 710 posts since 20 Nov, 2000 from Valencia, Spain
Yes, basically a way to avoid that a particular plugin inside of PatchWork could crash the DAW. I understand it would be at the expense of performance but, as an option, I thought it could be useful, as PatchWork has to wear so many different hats in completely unrelated DAWS and platforms.
-
- KVRer
- 1 posts since 8 May, 2022
Well, this is something Bitwig offers, and it doesn't seem to hit performance THAT hard... there are certain plugins, like Kontakt, that while *generally* stable can sometimes act up, and as someone who uses multiple DAWs, I always do feel "safer" in Bitwig due to its sandboxing. I have to imagine that would be a difficult feature to emulate in PatchWork, but it WOULD be pretty awesome in bringing that particular selling point of Bitwig to other DAWs...Blue Cat Audio wrote: ↑Wed Dec 14, 2022 9:13 am What do you exactly mean by "sandboxing"? Running the plug-ins in a separate process to acvoid crashing the DAW? That's definitely not optimal for DSP. If a plug-in is buggy, I'd rather not use it anyway, be it in a sandbox or not!
