OK, I can live with this solution because one stored preset in the custom bank is enough for playing back the sound I want to play with one instance of Warlock. But 1 MB additional memory for a bank is nothing compared to the memory one instance of Warlock uses.Markus Krause wrote: Fri Feb 12, 2021 4:31 pm @MorpherX:
The host only stores the current preset and not the complete bank when you save and re-load a project. This is intended. The reason for this is performance, host-compatibility and hard-disc usage.
Just imagine the patches of all banks would be saved with the song. Then 2 MB of discspace would be wasted for a single instance of Warlock. With 10 instaces your song then would be at least 20 MB large.
When the current bank (=128 patches) would be stored nearly 1 MB would be wasted for 10 instances of Warlock. While this may still be acceptable there are some hosts that automtically do backups. Your hard-disc would still be filled sillently in the background.
The current solution only stores the current patch. Only 7 KB is needed for a song with 10 instances. Furthermore your song loads instantly.
The reason for not saving a bank with the host is that you have here your own bank file extension (t2b) instead of .fxb. Reaper stores a bank in a VSTi with the project if it's fxb-bank compatible. Therefore the UserBank A-C are not saved with the project but loaded.
But if you mention memory usage, one instance of Warlock uses 90 MB here. Is this the last word or could there be optimations for less memory usage. On the other side if a user has 32 GB memory installed, then this is no problemo. But some users might have a small notebook with only 4 or 8 GB of memory.
