DSP Robotics Support

The preset manager should work,
so keep trying IMO
I second checking your parameters are in 0-1 range.
You have to divide in, then multiply out of the 'preset parameter',
if the values are going out of this range.
VST spec demands only 0-1
Let us know if u find any clues

thanks guys! Appreciated!

Ive checked the ranges, all 0-1.

Im using the preset manager with 1 preset in the bank , locked and set to all knobs defaults.Saved init preset.

Double checked the knobs and preset names. . . also I noticed in Cubase you can "switch to generic editor" for a vst.

Now it represents parameters in a simple gui.

There were a few "Preset 1" . . . "Preset 2" . . . . ect, parameters for automation.

So i investigated into all the preset link connections (Thank GOD for the TAB feature on wireless links )

There I changed all the params I dont want automatable.... I think its helped.

Before I noticed that when there is like more than 5-6 instances of my plug, same thing happens but BIGTIME!!!

Drnkhobo wrote: locked and set to all knobs defaults

I don't think the preset manager should be on "locked" if you want the host to recall the last values recorded before closing the project... Otherwise when you re-open the project, "default" values (the ones you froze before rendering to VST) will be recalled everytime...
Unless it's what you're looking for to achieve...

hmm, yep,
I don't have the manager locked and it works.
Another good way to check your parameter names
is save the preset as text,
and open it in notepad.
Here you can find all the doubles,
and chase them down in ur schematic.

I thought that the "locked" option box was to make it so that you can only save a preset by clicking the save button in the Preset Manager properties?

Also, doesnt Cubase or any DAW save the parameters with the project itself?

Drnkhobo wrote:I thought that the "locked" option box was to make it so that you can only save a preset by clicking the save button in the Preset Manager properties?

Also, doesnt Cubase or any DAW save the parameters with the project itself?

yes, thats interesting i thought the same, so i have it generally unlocked! and never had probs like this

nix wrote:VST spec demands only 0-1

Ohhh... So, I guess that would be important to know when making plugins, huh?

(This sounds like one of those things that should be handled automatically.)

To be more precise...
VST handles only values from zero to one for parameters that you want to automate. All of the hosts that I've tried will handle any float value for parameters which are not automated. I think that's just a matter of the host having a standard scale for drawing automation curves etc.
I think that's partly why it's not automatic - rescaling values can lead to problems with maths precision in some cases, so unscaled values do have their uses sometimes. But min/max/scaleOn/Off inputs on the preset param would be rather handy, as 0.-1 does tend to be easier to handle - not just for automation, but also hosts that allow assignment of MIDI controllers direct to patameters etc.

I also wonder whether some of the problems here might be to do with parameter order - some hosts are funny about having automatable parameters first in the preset list. This is something that has always been very awkward to sort out - there are some threads at the SM forum about it, though I've never really sussed it out myself. It would be good if that were made far easier to do.

I also wonder whether some of the problems here might be to do with parameter order - some hosts are funny about having automatable parameters first in the preset list. This is something that has always been very awkward to sort out - there are some threads at the SM forum about it, though I've never really sussed it out myself. It would be good if that were made far easier to do.

hmmm . . . maybe Support can give us more info here???



Once I had cleaned up params I wanted to be auto & preset, it seemed to be ok (no changes between projects)
Maybe it was that? (Also "unlocked' the preset in PSManager)

In my opinion, this should ALREADY be something that users of FS doesn't have to deal with.
SM & the new FS programs shud have sorted this for stable release. . . ?

It would be nice to see "stock" modules that users have created which are more stable/optimized than the FS ones... like the dev toolkit in SM forums. How about it DSPR? Can you create a sub-forum for customers & we can start adding files? Get things going? I think there are still quite a few VST-specific FS users.

found out that in my last version of my presetmanager i used it in locked mode and it worked well, (using cubase) the presetmanager is basicly the stock one, i just changed a few things:

i changed the way for renaming presets a little bit to finish renaming with the enter key and added a function to limit the shown lenght of presetnames to a number of characters (properties->short preset names)
i also added an "init program" - trigger in the menu to set an init presetparametervalue via trigger, which you have to prepare inside your knobs or presetparameter modules (like in this example)

think thats it..

for me this one worked always well