Solution to crashes by plugins - Sandboxing (Crash protection)

I hear ya, and I support your vote however you choose. I do have a slight intuition that building a sandboxing system may not provide the stability we’d like to see. As I mentioned, the plugins on my system that sometimes cause Cubase to crash run fine in Bitwig - even with sandboxing turned off. And that’s why I doubt said plugins were the actual problem given they work just fine in Bitwig. So using precious dev time to build a sandboxing system could actually be counter productive as that system itself will undoubtedly have bugs initially. Shoring up Cubase itself is where my vote goes :slight_smile:

Still old yet extremely relevant issue. Let’s get these votes going or something…

Of course not every plugin is crafted the same, but the main issue is the way Cubase handles plugins in general. Yes their dev time is precious and this is still a major issue that they need to figure out. Other DAWs are coming out of the woodworks, and have sandboxing by DEFAULT…as it should be. Sure, it might not work perfectly right off with Cubase…what new software does?? That is kind of silly argument to say you are worried new software won’t run right. They need to work on it. It’s why I am here complaining about it…again. And its still top 5 in votes.

After trying out MorningDAW recently which is VERY new…guess what… NO CRASHES(for me at least). It’s sandboxing works great on plugins with issues. It’s lacking a lot of things, but it’s looking very promising so far, and they (two Bros) are literally releasing updates every day.

72 and counting!

Well that’s because any ‘new’ DAW was written with it in mind from the start. Cubase wasn’t and has been around for a long time.

For all you armchair developers with no clue, this isn’t something you just tack on and may likely require rewriting whole parts of the code to implement. Sorry, but with everybody nowadays constantly needing ‘new updates’ just for the sake of it, I doubt the team has time to stop and completely rewrite Cubase. God forbid all the people that would cry if Steinberg stayed quiet for a year and just got to work.

And for all you and I know, they may already have a branch they are working on that is just not ready for primetime yet and may show up at Cubase 20, who knows.

There’s a slight performance hit when you host VSTs out of process because cross-process communication will always be slower than in-process communication. I can’t speak for audio, but for MIDI, that’s something like 40 microseconds to get from one end to the other with a cross-process queue. I’ve measured that with the new MIDI Service. We felt that is worth it to get multi-client and other features, however.

And as Monotremata said, it’s a LOT of work to retrofit into an existing audio engine. You have to write the data to shared memory (a memory-mapped file) and read from the same. Because there are two separate processes now, this is not a synchronized exchange by default – you have to provide all the synchronization.

It is interesting. I’ve been loosely following the work. But ask yourself how much testing is going on when there’s a release every day from a two-person team that is also running a web site and a business. Even with the agents running constant unit and integration tests, there are things, especially UI-related, that just don’t get caught without dedicated human testing. You are effectively getting nightlies. For MIDI now, with agents doing the bulk of the work for the past couple months, it takes a lot to get a tested release out even weekly.

Pete
Microsoft

Yeah, I get that, but I think you missed the point. It’s just DEFAULT now because of exactly what is going on with Cubase.

I’m no armchair developer, but I also have not coded an audio engine from scratch. You assume it would take a total rewrite.

Maybe…who knows? No one, except Steinberg. And that is also an issue with communication that they are not very good at. At least tell us some major features being developed with hints, teasers etc.

Have you ever been to Germany? Teasing things is just not in their nature :smiley:

Pete
Microsoft

Pete, I really appreciate your response and I follow everything you are working on with MIDI on your discord, BUT…BUT

I will take a few extra microseconds, over multiple crashes a day and even hours. Tell me how much time it takes an average computer to recover from a Cubase crash…compared to 100+ extra microseconds on the engine.

Cubase crashes is so many awkward ways which makes it even more annoying. There are times I think I get a clean, just regular quit and Cubase already crashed in the background and is just sitting there laughing at me. A CLEAN “QUIT”…not even a project trying to load plugins. If I did not keep system informer constantly open I would not have a clue about Steinberg’s shenanigans.

Besides, everything is delay compensated on playback when you are not trying to play back something live… I can live with 96+ ms delay when trying to play my drum pads, live. live…live

I should also say, yes you are correct with the added delay. After chatting a little with the devs of MorningDAW, (they are very responsive in their discord BTW) there is a microsecond hit, and I forget the actual numbers, but per instance of a plugin, or sandbox, adds only a few microseconds, which is obviously, extremely negligible. And then you have various methods, which add various latencies to the mix. So, it’s nothing that anyone is even going to notice.

All good. I wasn’t saying it’s impossible or not a good idea.

I personally think it’s worth the hit, but I’m not the one trying to retrofit it into an existing audio engine while keeping compatibility with X years of projects. I’m also not the kind of customer who is going to measure every microsecond in a product I use :slight_smile:

Pete
Microsoft