Here is the screenshot:
okâŚbut did you try and raise in/out fade, for instance 0.25 to see if it makes a difference?
I just tried that, but it did not make a difference. Actually, it clicks every time when it changes parts without restarting VST
I have a similar issue in one of my setlists when going from one part to another. It did not have the issue a few version of VS Live ago (or maybe the issue is because my stacks got more complicated in the meantime, I do not know).
Looks like we found the problem, pls try again with the next version and let us know if it works out for you.
So I upgraded to 2.2.24, but the problem is still there.
I also upgraded to 2.2.24 and still have the issue.
Eg. within a song when I am in a part and selects the next part which has the same VST effect (Tone X with an amp) and same volume as the previous, I have a small silence gap followed by a small increase of volume then back to normal. This defeats the whole point of VST live for me which was to smoothly switch between preloaded presets.
On the Stacks preferences I have :
- Sustains seconds : 0
- Input Fade in Seconds : 0.01
- Input Fade out Seconds : 0.01
Am I doing something wrong ?
No, this is intentional. We are working on improvement for this special case, to omit fade out/in when the target is the same. It is difficult, because Stacks are closed entities.
If you always use the same input for a Stack, you should activate the Global Part (âPartâ menu), Stacks (and Layers) in there are kept alive during the entire project. You can change settings for those âGlobal Stacksâ using automation and/or virtual MIDI too.
We suspect this is a different issue from Shiroryus one, which is also about Stacks, not Layers. Still looking into it, but it is very hard to reproduce. Will check your project once again.
Using global parts is not appropriate for me because the very reason I use VST Live is song parts that map the song structure so I do not have to create an automation track. This the best feature of VST Live for me : it greatly simplified effects programming. Actually, I do not have an automation track at all : only parts with one and sometime multiple stacks in a part.
On specific songs where I want to control effects myself, I have only one part with multiple stacks and I change stacks with a MIDI foot controller (e.g. Clean, Drive, Solo staks).
I understand that going from one part to another one containing the exact same stack creates the gap issue. What should I do in order to avoid this issue ? If I use the same VST but with a different preset, will the issue still arise ? Or do I need to have a different VST when going from one part to another ? And what about creating different stacks (different stack names) with the same VST inside ?
@musicullum - does this make a good case for shared stacks? Is that possible?
1 Like
Currently you cannot avoid it. We are working on checking to avoid the x-fade when target is the same.
With a different preset, it currently does fade as well, but in that case it might even be beneficial - which it would not be when we make that change. We cannot see which preset a plugin has loaded.
Yes, good point, we have that on our list already and will give it a push.
3 Likes
I already mentioned this in another post, but I think itâs something similar to what is being discussed here âAfter a few hours of testing backward versions, one by one, I think Iâve found the problem with the crackling when changing parts of the STACKS. In version 2.2.16 and earlier, the change works perfectly, without crackling. The problem is that after that version (I donât understand why) the Preload Parts function was removed. When you apply preload parts, the noises between part changes do not exist. It is a fundamental function for those of us who work with piecemeal stack structures. Obviously it is not a question of what plugins you use, because up to this version, with this function, everything works as it should.â
1 Like
As posted in another thread (cannot keep track of multiple threads) pls. try again with the next version, we found and fixed an issue.
I upgraded to 2.2.32 and I am getting a big spike in volume when the parts change and now VST is using almost 9GB of memory instead of the 2 to 3GB that it was using for the same project. I have 3 setlists in the project and when I activate a different setlist VST does not offload the previous setlist from memory before loading the new one, thus consuming a tremendous amount of memory.
We didnât change loading setlists, but will check what it could be. Did you change setlists before (what you compare to)?
Unfortunately I donât have a comparison before or after, I do know VST preloads different after I selected File>Preload Parts. It runs through every song and preloads every part in every song when I activate a setlist. I tried that to see if the problem with part changes would go away (which it didnât).
So all that to say, Preload Parts is probably doing what it should, however when a new setlist is activated the old setlist should be unloaded from memory to save on resources. Just my 2 cents on the matter.
There is no âunloadâ per se.
Each Song is a project, even when residing in a setlist Song that isnât active. What gets âloadedâ is only what plugins do. So weâll try and remove all plugins, and load them back in their âvirginâ state when a Song is no longer in the active Song list.
Note this may take a significant amount of time when changing a setlist, so it would have to be a preference. Not all plugs allocate loads of memory.
That sounds like a good option to put it in the preferences
We started trying this, but it doesnât help much.
If you have a Song âOnly Set 2â which is only present in setlist 2, and you switch to setlist 1, the plugin would loose all of its settings.
As often explained, plugins are blackboxes seen from the host. We can open and close those, request which parameters they have and change those, tell them to give us a block of data (another blackbox) to save, and provide that saved block of data back to the plugin when activating it.
We can save and then remove the plugin instance (object), but in most cases, that doesnât help. The plugin itself is not doing anything when not activated (as is the case when it is nowhere in the active setlist), but it keeps its data in memory. However that is usually just the same data as what it supplied when saving, so nothing is gained.
Weâll try to remove the plugin instances (with said preference) but it will take a while to implement and as pointed out, it may not help much.
Are you sure to not have changed or added plugins etc? We didnât change anything with the setlists, so if there is a bug it must be something else. Best to try again first with todaysâ new version coming tonight (we hope).