Mastrcode, I think we are diverting the topic.All this that you comment is fine. ButI commented an idea to improve the load VST to compose faster, be more selective, advance. It’s very simple.I still think there is no problem in implementing this idea.Another thing is that developers do not want to implement it.But you have to open your mind.
There is no problem loading a VST after another, and Renoise do it automatically after one drag an drop selected, because Renoise is already able to do it (the operation load multiple VST automatically).
…and initializing a 50+ GB library during startup of Omnisphere needs it’s time. Fast harddisk or not.
Omnisphere not load 50GB, only the sounds selected (only are 8 buses or channels). Load Omnisphere in a free slot first only takes 4 seconds in a fast computer. After load each patch (of variable size, 8 patch in total, 8 buses).Never load an entire library of 50GB.
…You have either way to tweak your VST’s and their tracks one after another.
This is the problem! Load various different VST is tedious.This is to make things go faster while you compose.The problem is not that the VST takes time to load.The problem is that the user takes to load.You have to do various steps to load a single VSTi!
Creating a template makes no sense. You’re missing the same time and no good. The issue is to load multiple VST, and delete, and load, and delete, and load again for proving.And if you can do as a group or more groups, it’s better!
If you do not want to use it, do not use it. Others could use. It would be a more function, it does not bother to nobody.And people do not use it because it is not programmed.Do it, and people use it.
However, this will not be added in this version 3.1 and I doubt it done in the future. “The Detail 1” has been ignored (memorize selected tab (plugin tab) in Instrument Editor). Therefore, the “Detail 2” (drag and drop VSTi in Instrument Box), is ignored also. It is not a priority issue like many in these forums.