Thanks, Rob, for bringing these core rendering issues to light.

BiaB RTs, RDs, and RCs are the best-kept secret from the DAW world. “Professional Studio Musician playing your song's tracks!”

The DAW market is expected to reach $16 Billion by 2026. Hopefully, PGM sees the plugin as a potential “Game Changer” gateway product to this massive DAW market.

The plugin as a gateway offers the crème de la crème of BiaB “Rendered Pros” with a very low learning curve compared to a 675+ page manual.

However, this new DAW generation expects it to be intuitive, and simply work as advertised.

Because the plugin is at its core a "Front end to BiaB’s rendering engine", why would anyone bother to use it if it cannot match the core rendering capabilities of BiaB?

I am sure PGM is aware of these dozen rendering issues, but it is frustrating to both wait 15 months for them to be addressed and hold off recommending it to the world.




Studio One (latest version), Win 11 23H2 , i9 -10940X 3.3 GHz, 32GB Mem, a 4K 40" monitor, PreSonus Studio Live III Console as interface/controller. secondarily test on Reaper, Cakewalk, and S1 on Surface Pro 3 Win 10 (latest versions).