Speaking generally, I could see setting a maximum memory limit - but apart from that, an application can generally manage its memory automatically, and only purge when more space is needed. It’s generally faster and more efficient than performing the task manually, because the application can predict its future memory accurately - especially if it’s a linear system like a set list. Therefore, the system can retain in memory the maximum amount of data, at all times, maximising the responsiveness of the system should you diverge from the linear path.
speaking simple: in many vst instruments you can set the amount of memory charge.
In kontact player, for every instrument you load you can set how or if you want to pre-load ALL the samples, and there is a PURGE botton to discharge memory.
So … Why is too strange my request? Maybe automatic? yes please.
Make a project, erase the song on the list: memory is still here, no auto purge.
Change something. History empty, change project, memory still here,…
Add and discard songs, 'cause i am live performer with a dynamic show, i am adding songs in my project, and discard, and add…
WHY memory will be saturated for song USED and ERASED from my “service live show” project?
Not a show with pre-program a project with the songs., there are others kind of show.
Maybe others software is running with vstlive, as obs for a streaming and others for example.
Why, in order to purge the ram, I need to go out, close and re.open vst live?
Hello Frank, I certainly agree the issue you have described is salient. It’s generally possible to have a better solution than having to manually purge your memory – though in the specific case of this application, it remains to be seen what the best angle is. Thank you for your suggestion.
The host (VST Live, or any other) has no access to that function, it is maintained by the plugin.
Because it needs to be kept for undo.
a) we will add a purge function for undo
b) you are correct that VST Live “forgets” to purge undo memory when closing a project (like “new”), that is fixed with the next version
c) we will add a purge function as of your request, which is kind of the opposite to “Preload”.