I have a problem with the Alias function in the instrument settings tab.
It’s most likely not a bug.
When i create an alias of a VSampler instrument, i set the program to the next bank instrument loaded into that particular version of VSampler (3.0).
Problem is, it also changes this in the original host instrument.
Is it the purpose of the Alias to exactly keep EVERY vsti state identical to the original or was the alias the purpose of pointing to the existing vsti project so you wouldn’t require to reload the (VSampler) vsti into the memory-slot again?
What is the true purpose of the alias function when you can’t change programs or banks independibly of it’s originate host?
What also bugs me very terribly is that for everytime i select the VSampler vsti (or any other large VSTI that has a lot of samples) it reloads the vsti and this can take an awfull lot of time. (This is when the instrument settings tab is selected)
And it does not only do this when selecting the vsti instrument slots but anything that relates to it when it comes to e.g. connecting it to a VstiAutomation Meta device (it loads up each stinking vsti you have to browse through to get to the actual vsti you want the vstiautomation device attach to)
Can’t there be any better handling of loading vsti’s into memory once and then just store it’s parameters somewhere you can quickly retreive until they are really changed?
Currently this situation seems worse than it was with 1.281
This is one of the reasons i want more sample-slots in the instruments, besides the fact that vsti has almost no or bulky sample manipulation facilities, and i’m not talking about dsp effects or any other kind of vst effect, but pure sample offset, cut, delay and retrig.
It’s not my memory or harddisk space as i have 1GB Ram en 10 GB of free hd-space.