Closed EXEConsulting closed 6 months ago
VASTDynamics
commented
6 months ago Reloading only works within a session. If you save a project and load it again, the state of the plugin is retrieved from the plugin state that is saved with the project. It could even be that you load a project with a Vaporizer2 and you do not own the original prest file. In that case reloading could never work.
I tried to reproduce the "staccatio issue" in FL Studio but did not see it. I will continue to test.
EXEConsulting
commented
6 months ago Unfortunately, I don't understand your reply. Perhaps I did not explain the problem clearly enough?
I just tested FL Studio v. 21 and found the same behavior, playing legato when project loaded, changing to SY Init Patch when clicking on Reload to try and load the properly playing staccato preset, then correctly loading the original preset again from the browser, saving the project again, then failing to load the plugin and preset properly for the second time.
Clicking on Reload does neither load the parameters which are supposed to be stored with the project file nor loads the preset whose name is in the preset name box.
I also created a video showing all of this behavior with FL Studio 21:
Regards, Dave Clark (aka EXE Consulting)
AR Trance Gate Arp Preset behavior depends on the way in which the preset is loaded, reloaded, or restored while opening project.
When a new instrument track is created and AR Trance Gate Arp is chosen for the preset, the sound is staccato. When a project is stored in Cubase 13 Artist or Mixcraft Pro Studio 10, then opened again, the preset is significantly more legato. When this preset is Reloaded using the Reload preset button after opening the project, it switches to AR Synth Arp instead of reloading. When reloading using the preset browser, it loads and sounds again staccato like the initial loading. When this project is saved then re-opened, it goes back to legato and does not Reload from the Reload button correctly (again goes to AR Synth Arp). It is always necessary to manually reload the original preset using the Preset Browser.
I have not checked other similar presets to determine if they behave the same.
I took screenshots of Vaporizer 2 tabs such as MSEG, FX, Matrix, and others but could find no difference in parameter values in these two different modes. Nothing that has been visible to me so far is any different. I examined the entire interface while in the WT editor tab and again could see no visible difference.
When the preset is in staccato mode, it is possible to alter some of the knobs unrelated to legato and staccato such as Reverb and cause the preset to suddenly switch to the legato mode. Switching the Legato radio button On and Off does not change the behavior while the plugin is in either mode, staccato or legato.
I also saved the staccato version while it was active as my own personal preset. When I load this using the preset browser, it loads as the legato version. It is impossible to recover the staccato mode except going back to the original. I compared the files for presets (original versus my own personal one), but there were too many differences for me to consider without spending a lot more time learning about the parameters, etc. The answer may be in a diff of the files, but to someone more familiar with the parameters than I am.
It appears that some parameter that is not visible is being changed or that this change is not propagated to the interface. It also appears that the parameter value is not stored correctly or is ignored when saving or opening projects.
I have seen cases where I created a new version of a plugin with an additional parameter which causes loading of old projects to corrupt preset settings --- wrong values because the parameter integer reference values are incorrect . For troubleshooting this problem here, I created a new project with only one track and verified that storing and reloading projects still causes the preset to change its behavior.