Operating system Windows 10 Pro
Gig-Performer 5.0.9/4.8.2
This issue is easily reproducible with the IK Multimedia Pianoverse VST3 (V1.0.4/V1.0.5/V1.0.6) plugin and also with the Toontrack EZKeys 2 (V2.0.5) Fazioli Piano, but not with all presets of the Fazioli. With the Fazioli, the issue shows up with the preset ‘RAW-Sounds->Close Room 1’, for example.
If I use ‘Save GP User Preset’/‘Load GP User Preset’ from Gig Performer in the preset management, the parameters are applied correctly and the plugin works without the workaround.
It’s probably an IK Multimedia thing. The same issue was occurring previously with their Sampletank macros resetting unless they were mapped to widgets.
So, try mapping those parameters in your screenshot to widgets, and see if the settings will save and recall properly then.
Thank you for your reply. Linking the parameters to the widgets works, just like setting the parameters via script. But not when loading a GIG file.
I also assumed that it was an IK Multimedia issue so far. But when the same issue occurred with the Toontrack VST3, I started to have doubts. When I tested the VSTs (IK Multimedia & Toontrack EZKeys) in Cantabile and there was no issues, my doubts grew.
By the way: the Pianoverse VST2 plugin works in Gig Performer.
It seems that the parameters are loaded correctly from the GIG file, but are not transferred to the Pianoverse/Toontrack plugin and my simple script takes over this task.
This does not make sense to me. Your script is querying the plugin for each parameter value and then sending it right back. If that works, then clearly the parameters are being correctly loaded into the plugin (otherwise how could you get the correct values into the script in the first place)
Are you having this issue with other VST3 plugins?
There’s something we’re missing - we will have to explore further.
I don’t have those particular plugins but I just tested with two other VST3 plugins, Legend Hz and M-Tron IV - and both of them load up with the previously saved state.
Yes, with the Toontrack EZkeys 2 Fazioli Piano. But unlike the Pianoverse, it depends on the preset. This is due to the fact that the number and type of parameters on the Toontrack piano differ depending on the preset.
Both VST3 plugins (Pianoverse/EZKeys 2) work in Cantabile 4.x and the Pianoverse VST2 plug-in also works in Gig Performer.
Further findings:
I tested 2 free VST hosts today. These were
AudioPluginHost from Juce (free VST development environment)
Element v0.46.6 from Kushview (free older version).
Both work fine with the Pianoverse and Toontrack VST3 plugins. With Cantabile 4.x there are now 3 hosts that work and I only have the issue in Gig Performer. This is of course not definite evidence that this issue is caused by Gig Perfomer, but it is strange.
This is how the issue appears with the Toontrack VST3. I have used the plugin 3 times with different presets. The parameters are set wrong after loading the GIG file. With Pianoverse VST3, however, all parameters are set to the minimum value.
I understand that the parameter controls visually display the wrong value (i.e, they are all at minimum) but if you actually play the instrument, is the sound correct?
In other words I’m trying to understand if this is simply a DISPLAY bug rather than actually wrong parameters.
The GUI display matches the parameter settings. The GUI works fine, the settings are wrong. I don’t hear any sound with Pianoverse VST3 because the mixer settings are also all set to minimum.
What is also strange is that when I save only the settings for the Pianoverse VST3 in the Preset Manager, all settings are set correctly when I use the associated load function for the plugin.
I don’t have Pianoverse but with the Toontrack pianos, it’s like I said in my first post-- unless those controls are mapped to widgets, the values don’t get recalled. I’ve encountered other plugins that also have this issue. My guess is they aren’t correctly stating the explicit values of each parameter upon saving. Other hosts may be taking a snapshot of an overall state instead of looking for each individual value and that’s why it recalls properly elsewhere. You can see with the Pianoverse screenshot that the volume and pan controls are all zeroed out (pan hard left is represented as zero) . I think that would be the default value given if that value wasn’t explicitly provided.
It’s a plugin issue if those individual values aren’t being saved properly. GP can’t properly recall what the plugin doesn’t save internally, which would help explain why when you assign those controls to widgets, GP does recall the values properly.
I also see with the Toontrack piano that if you change those Effects values, save it to an internal Toontrack preset, and save the gig file–upon loading Toontrack shows that its loaded your internal preset name, but it definitely hasn’t loaded the proper values associated with that preset. If you then manually load that same internal preset, the values will appear correctly.
Also, for Toontrack, it is the Effects parameters that aren’t being recalled properly. The Tuning parameters do get saved and recalled properly, so its a case of certain parameters of the plugin not being recalled properly as opposed to the whole plugin not recalling properly.
I found your explanation (older post) of the possible cause of the issue helpful. But this different behaviour (GIG file vs user preset) in Gig Performer contradicts your assumption.
The questions I can’t find an answer to are:
Why does saving and loading via the Gig Performer Preset Manager work with the VST3 plugins? And why does the Pianoverse VST2 plugin work and the VST3 not?
The GIG Performer parameter handling should be the same for VST2 and VST3, as well as for the GIG file and the user preset file.
The VST2 and VST3 of those plugins are clearly written differently. As it is with some plugins (sadly), one version works well while the other doesn’t. If you look through this forum (and other hosts forums too), you’ll find multiple instances of this kind of thing happening where one version of a plugin isn’t working as it should but another is fine. You should report to the individual developers about the versions that don’t. They might be able to provide an update down the road. Until then, use the version that works properly, or in the case of there only being one version, assign the parameters to widgets.
I have not been successful with IK Multimedia support. Reply: Gig Performer is to blame. I haven’t tried the Toontrack support yet. And I don’t know whether Deskew support is dealing with it based on my post. Probably not. Sadly, it’s an experience I’ve had more than once. Most of the time you don’t even get a replay from the support.
Reply: Gig Performer is to blame. I haven’t tried the Toontrack support yet. And I don’t know whether Deskew support is dealing with it based on my post. 
Probably not. Sadly, it’s an experience I’ve had more than once. Most of the time you don’t even get a replay from the support. 