DSP Robotics Support

Here I have a topic, which could be a VERY IMPORTANT question for EVERYONE here:

HOW can I create VST's the way that DAWs do recognize them as duplicates and don't create always NEW memory for a copied VST-instance???

So I made a plugIn with 30mb and I use it 60+ times (which happens really often in orchestral mixing) in Cubase then it takes +1800MB !!! of RAM.

With C++ -made PlugIns there isn't that problem: One has 28MB RAM and if I use many of it then Cubase stays at +28MB.

Is there any way to accomplish that important issue in Flowstone?

Thanks!!!

This is a very hard question. Most memory data is expected to be specific for each plugin (for example each delay plugin needs its own buffer to store audio). You could save certain data types in class variables or as constants in ruby and they should be shared among individual instances of the plugin. That may be harder to implement than it seems. For example you could store wavetables in frames in ruby, but it's hard to use them (I tried to make custom wave array module but it has proven to be very unstable).

Ok I have an Idea now: EXTERNAL DLL's

If I separate those RAM-consuming segments into an external dll, then maybe it could work, that I save RAM while duplicating.
Bitmaps could be stored in a external flowstone-created dll which then could be accessed on demand (audioprocessing modules or bitmaps, whatever). I don't care if I would create a dozen dll's for that - performance wins.

Has anyone maybe tried that out?