So after all it's fault on AA side. Obviously, changing SDK can cause a lot of issues. I suppose that bugfix is related to my first point from my post?dionenoid wrote: ↑Sat Apr 10, 2021 1:33 pmAA updated some plug-ins, they say it should fix the Cubase issues. Until now Sienna, Tan (free) and Coffee Pun (free) had this update.pixel85 wrote: ↑Mon Feb 22, 2021 5:38 pmCircuitEYE wrote: ↑Sun Feb 21, 2021 9:16 pm My biggest grip is that they tend to very often crash Cubase when closing a project.
This has been a known problem for a long time but still no fix.For AA the issue is on the Cubase side so they will do nothing about it (I got this info recently on their FB group). I also suppose that Steinberg doesn't care that much about AA to also fix it.
- crashing at exit (usually closing project then Cubase help to avoid it)
- crashing when there are several instances of the same AA plugin (when there's still a lot of CPU and RAM available so it's not the reason)
- very bad performance in comparison to eg. Reaper
These issues are here to stay
There are also some other Aquas updated recently (Magenta, Purple, Cream) but it's not sure if they contain the fix for Cubase.
First reports from some users are hopeful, i'll be testing as soon as they update Aquas that i own.
Simply put, the problem seems to be that the graphic engine of AA plug-ins is not released from memory (which was also stated by Steinberg multiple times). This is most probably due to AA using an older, rewritten sdk for their plug-ins which causes the hanging and freezing on modern Windows systems.
It's a shame that it took AA over a year to acknowledge their own mistakes and finally do something about it. But on the other hand, it's good that the AA devs are active on forums personally and despite their initial stubborness finally take action.
For me 'crashing at exit' is not an issue that I really care about. The second point from my previous post is the reason why I put on sale all their paid plugins that I have