Acustica Audio plugins crashes cubase

[vncvr]

@User131231

First there are more than 6, second we talk here about up to date plugins. For example Spire 1.1.16(i think) was up to date back than and it hangs on exit on up to date Cubase only! -luckily devs released 1.5 where hanging doesn’t manifest (i don’t know if they are actually aware of that with previous version or they fixed it on its own by optimizing changing framework or whatever )

So, the devs released 1.5 and then it worked? How is this supporting your argument?

@User131231

Comparing 32bit with hang on exit has no point. Since 64bit platform is beneficial on many ways and its logical that devs should jump on 64x since users have benefit out of it and that’s only matter BENEFIT! - fixing hang on exit by developers thats only happens in cubase and because of cubase is waste of resources, I would stand opposite if that happens at least on one more DAW.

irrelevant to my point. My point was, there are thousands of plugins that no longer work in Cubase because the developers didn’t bother to update their plugins from 32bit to 64bit. Tha’ts not Steinbergs fault, nor their responsibility. The benefit of 32bit vs 64bit is not the point.

@User131231

And we had FLS slot limit limited by Microsoft(which respectfully to the apple owns 80% of desktop OS share ) and yet they rises that limit in 1903 update. Blaming Steinberg for that limitation is absurd why? Cause it happens on all other DAWS, and again we comes to what is benefitial for the users which I repeat is only matter. I am far from apple ecosystem but I know that some nice devs (melda,u-he, and few more that i cannot recall atm) has some negative statements of apple’s way of doing. On the other hand I applaud apple for “injecting” intel instructions on hardware level in their new silicon chip instead of emulating it on software level like they did when they switched from motorola CPU to intel. It turns out that all works good on new chip and that is beneficial! So its not that “everyone needs to rewrite their software” just like that. Again apple users can comment on this better.

Apple sucks, every time they release something everything is broken. It’s not an engineering platform and it’s a travesty it became popular with audio engineering. Again, you’re not negating my point with apple regardless of their development ethics.

@User131231

This stands right, but also Steinberg could say same for Eucon and S series that is AVID fault (Oh wait ) or things regarding HiDPI or ARA or every other topic that has countless pages here where users could have benefit but they don’t at all or to full extend as advertised. And the same users knows to reward those devs who stands behind their product and willing to quickly react on issues that are known or introduced, also the same users will punish the ones who doing opposite.

Not really sure what you’re getting at here. These are all false equivalencies. HiDPI is resolutions pushed by consumer standards - Steinberg have adjusted to it. Not really sure what you’re getting at with ARA and Eucon.

[User131231]

I think i put enough arguments based on previous practice and experience.
The whole point is that someone has to get down and fix the issue.
The topic issue (hanging on exit) is steinberg’s fault and majority agrees on that. Fixing by devs ONLY because of cubase i see as generosity and total care from devs.
The fact that steinberg doesn’t like to get down and fix their issues (even new introduced ones) is well known by everyone who using cubase more than 5 years.
Thats it.

[fese]

@vncvr

they can’t write/fix Acusticas plugins for them…

the solution is following the SDK rules and standards for VST up to todays revision. Not last years, not 2 years ago, not from VST2 days, not even yesterdays. Todays.

Again, this has nothing, nothing to do with VST standards or SDK rules, be it VST2 or 3. Nada.

As I wrote, the problem with the Acustica plugins is that they use an old version of VSTGUI (a graphics and user interface library for VST written bei Steinberg) that has a known regarding DirectX bug that produces the hang-on-exit error in Cubase (and weirdly, only in Cubase). This bug was definetely Steinberg’s fault, and they fixed it years ago. Acustica can’t or won’t update and decide to go JUCE. This will most likely take months or years.

The question still remains why Cubase is so finicky about this when all other DAWs aren’t.

[vncvr]

how does that not have to do with VST standards or the SDK rules? lmfao

[fese]

Because it is an issue with the graphics library DirectX from Microsoft that is used by VSTGUI, the bug is in the graphi routines, see the code here, especially the newly added use()/unuse() methods: fix too early unload of the D2D libraries when multiple frame objects… · steinbergmedia/vstgui@55d14da · GitHub
VSTGUI is not the VST SDK. You can create VST Plugins without ever touching it.

[vncvr]

it’s an old issue… that is resolved by the latest VST SDK standard.

Are you saying that Steinberg needs to fix an old issue by making Acustica work on the broken previous SDK despite it already being patched in the more recent SDK?

[Bobby_L_039_Avenir]

Trust me, without Jbridge I’d be using Bitwig exclusively because of the constant crashing. Try Jbridge and do what i said in the last post.

[garethk]

Well problem solved for me in the latest AA updates. However new problem started. RIP and export audio causes the FREEZE (as I should specify, it’s not a crash) unless I deactivate and reactivate all my AA plugins in a newly opened project first. Weird. But a lesser evil compared to the original nightmare. If I’m the only user with this new problem then I guess I’m King S##tluck.

[MrVinz]

Hi,
Problem is solved for me since the last acustica update !!
Greaaaat !!

Thanks you

[Puma0382]

All that bashing/finger pointing on Steinberg.

I think @vncvr nailed it a while back.

Ok, for those who haven’t already seen it:-
Major bug warning for Acustica Acqua users - Page 2 - Effects Forum - KVR Audio

[ADWolpert]

The advice to use JBridge and bridge the VST2 versions of the Acustica plug-ins worked beautifully! I was having the same problems mentioned in this thread – plus, when I tried to freeze any tracks that had Acustica Aqua plugins on them, Cubase would just crash or quit spontaneously. Using JBridge – which luckily, I already owned – solved ALL of those problems. It’s kind of ridiculous that I should have to resort to a workaround like this – the plugins shouldn’t need to be bridged to function properly, after all – but this solution really did the trick, so thanks for the advice!

Best

Alan

[Pablin_Drummer]

You need to update your Aqua Plugins,with the latest version of Cubase,works fine!!

[ADWolpert]

Actually, I had been using all of the most current updates of the Acustica plug-ins, and that didn’t help at all. In fact, the newest updates only made things worse, and I had to roll back to earlier versions.

There’s a lot of finger-pointing going on about the cause of the problems, with Steinberg blaming Acustica, Acustica blaming Steinberg… All I know is that the only thing that solved my freezes, crashes on exit, inability to freeze tracks – all of this occurring only with Acustica plug-ins – was JBridging the VST2 versions.
Note to anyone who wants to do this: It has to be the VST2 versions since JBridge doesn’t work with VST3 plug-ins.

Best,

Alan

[Alexis_Sorbas]

Hi guys I just stumbled upon this thread, since I had the same problem. After trying jBridge which somehow didn’t work for me ( no nebula gfx ) I put the 3 Nebula files (N4.dll, N4.ENG, N4.xml ) into its own folder in my VST-Folder ( in my case it was …VSTPlugins/N4/ ). Somehow Cubase didn’t crash after that. I hope I could help!
All the Best
Alex