parapente,
Please don't see my post as I am defending PGM. I try to stay neutral. I agree that more needs to be done to address a loud chorus of requests that fall under 3 main topics: Previous bugs fixed, Complete existing features, UI / Workflow. In my opinion, 2025 fell short on most of these requests.

Having said that, for the most part BIAB is a stable program, especially considering how many different "moving parts" it has. The $59 it costs to just update the core programs during this promotion is not a lot of money by any means. It has enough new features to justify this very reasonable price tag. If you want to wait until most known issues with release are addressed, you can purchase the software while on sale and wait a few weeks until PGM irons out known issues. Some people do that.

Please don't view this particular thread as a deal breaker. VST3 for the most part is very stable. There are a few things PGM has to address that are described in these posts, but most likely they will not affect you.

Three items that I feel where "unresolved" in this threads are:
1) Initial scanning for VST3 plugins crash BIAB for some people - I believe some safeguards are needed. For example continue the scan despite errors and upon finish produce a list of those plugins that failed scanning, so a user or PGM can investigate. ( I think most crashes happening because people try to scan their whole computer for DLL files, instead of specific folders).
2) Halion 7 crashing.
3)Halion7/Sonic7 doesn't do Program Changes.

Since Sonic/Halion is considered to be kind of a gold standard VST for General Midi / program change playback, and many people use that plugin with BIAB it is very important that PGM finds a solution.