presetmanager bug or normal behaviour?

[Nubeat7]

hi all,
i found out that when i enlarge the number of presets in presetmanager and i overwrite the plugin, that the plugin crashes when loading a song which was using the old version of this plugin.

thats really annoying when you want to offer more presets with an update because cubase crashes or renoise doesnt load the plugin...

so for me this is a bug.. or isn`t it?

[tester]

Theoretically it's normal, at least according to my understanding. Preset manager is outside the rest of FS boundaries (the P node), and it appears to work somewhat like mem primitive (must work with automation, so it's not exactly green inside perhaps). I bet there is some sort of caching done when changing these preset features.

You can even crash the FS if you change dynamically too often array sizes in preset parameter array.

[nix]

You are not experiencing something which is not normal to FS.
As soon as you add a preset param, remove a preset param, or change a preset name,
it breaks backward compatibility.
So essentially altering the preset format breaks backward compatibility,
which is a pain, but I think it's inevitable.

Cheers mate, no sales yet on 2SYN

[RJHollins]

as essential as the PreSet Manager is ... I too have found ANY changes made in the schematic, that has preset capability, messes with all settings.

I've had to work out a 'slide and replace' technique every time I change my plugin.

Due to the way this all works, I doubt that there is any 'easy' way to maintain backward compatibility [thus avoiding preset chaos . I've also experienced a type of crash that seems tied to the preset manager assignments being altered. Some DAWs seem more 'sensitive' to this issue. Fortunately, I've been able to 'reset' the VST scan and eventually get a good load in. Nerve-racking

[Nubeat7]

thx guys, yes RJ its true some daws react worse then others while cubase is really bad and crashes already at start up..
renoise just dont find it anymore..

@nix: never mind it was a good experience to participate on 2SYN guitarists don`t know what they miss
in general i think its difficult these times to find a place in the market as a small developer when dont do another mastering tool which makes your tracks sounds like all others sound..

[RJHollins]

there have been those times that a VST scan fails [for whatever reason] ... that I've had to re-save the plugin generated by FS just to force a re-scan.

I know that probably doesn't help much ... other than a sharing of misery

oh ... and speaking of the PreSet Manager ...

One thing that I started to look for ... is there a possible way to send a Reset to default setting globally ??

I know how to do this with knobs and sliders ... but things like pull-down menus and buttons.

I see in the pull-down menus a 'default' setting ... but I can't seem to get it to reset ??

[Nubeat7]

One thing that I started to look for ... is there a possible way to send a Reset to default setting globally ??

I know how to do this with knobs and sliders ... but things like pull-down menus and buttons.

I see in the pull-down menus a 'default' setting ... but I can't seem to get it to reset

you need to insert a last prim at the value input from the presetparameter prim and trigger the default value, this is the same with each kind of parameter...

like this you only need one trigger to reset all parameters to their defaults..
i prepared also the presetmanager`s menu and inckluded an init trigger there...

[RJHollins]

This works great !!

Thanks for the different examples too

[RJHollins]

Hi NuBeat ... me again

I'm testing that INIT reset feature ... works great ... except ...

in the 'multi-preset module' that you posted in another thread ... I've tried several ways to add this INIT reset feature, but can't get any of my attempts to work ... if you find a moment, sure could use your help ... again

[Nubeat7]

to init the presetparameterarray you have 2 ways:

1. if you want to set all to zero just use the reset trigger
2. if you want to set individual default values you need a table with the values at the array input

in both of them just use a single trigger at the entry and don`t forget to trigger also at the output to update the slider or knob (take care of the right trigger order - first push the values and then udate the slider)

like the second way you also can set any values from outside like random seq when used in a stepsequencer..