Zynewave's Forum Page

Hi Mika,

I feel bad that I haven’t solved this issue yet. I started making some changes to how plugins are loaded into memory, but I haven’t finished my work yet. I got preoccupied with the new zynewave.com website, which you can read about in the VIP lounge. The website redesign started as a small sideproject, but it has taken up most of my time recently. The new website is hopefully finished within a month, at which point I’ll return to Podium coding.

I think I’ve identified the issue, and I’m working on a fix.

Meanwhile, you should be able to avoid the rampant memory allocation by switching to realtime bounce recording instead of offline rendering.

Another thing to check: If you are using the 64-bit engine option, you can halve the memory usage by switching to the 32-bit engine.

Do VSTs have a function that reports to the host that parameters have changed in their setup?

The parameter name, no. Some hosts may request the parameter names from the plugin after e.g. a preset change or before showing a menu with available parameters.

Request noted. I can probably implement an optional automatic system, like i’ve done with ReWire devices.