From the original SynthMaker forum (2004–2014), with its members’ names and dates.
Zyxoas ·
Hi people.
I'm creating a complex dynamics processor in FL Studio Synthmaker (1.1.1) with VST automation. I used stock knobs and inserted a PresetManager component, thus enabling automation and recording of the parameters (this is the usual way to do this, right?).
Now, for those of you who don't know, in the latest versions FL Studio provides a "Browse parameters" option in the plugin window menu. When you click this, you can see all the parameters of the selected plugin (doesn't work for DX) and right click them for remote control, editing automation events, etc.
In my little project, when I browse the parameters, I see the buttons, but there are two problems
*I also see a bunch of parameters named "<deleted>"
*Tweaking the plugin's knobs results in the incorrect parameter being highlighted (FL Studio highlights the last tweaked parameter).
Strangely, if I add up an effect such as the compressor into my schematic then the <deleted> slots get filled up with the names of the compressor (while the problem of the incorrect parameters being highlighted remains), but deleting it results in them reverting to <deleted>.
Saving the project and reloading FL Studio does not work, and neither does saving and reloading the schematic in FL SM.
malc ·
Hi Zyxoas,
If you delete something from your schematic that contains one or more preset parameters then these show as "<deleted>" in the parameter list that gets passed to FL Studio. The reason they are not completely removed is to preserve any automation of the parameters which you may have in your project. So this behaviour is correct.
What isn't correct is the tweaking feedback showing the wrong parameter. Also adding new elements that contain preset parameters shouldn't take up the <deleted> slots. I think that this second issue causes the first one so something for us to look into there.
To get rid of <deleted> slots you just need to reorder the parameter list. Go to the Schematic menu and select "Reorder Preset Parameters". That should get everything back on an even keel.
All the best,
Malc.
Zyxoas ·
Thanks a lot Malc. I guess I should've just Read The Friendly Manual.
One strange thing is that although FL Studio highlights the wrong parameters, if you right click the right parameters and remote control them then FL Studio sends data to the correct knob. So it seems this problem only occurs in one direction (SM -> FL, not FL -> SM).
I'm not conversant with the FLSDK, but I do know that in the VSTSDK one needs to be careful to ensure that you consistently use the same parameter ID for the same parameter. So that's the first thing that popped in my head when I understood this problem.
Your solution worked. Too bad I couldn't export to VST to see if the problem persisted.
Here's how to replicate the problem. My intuition told me it's caused by deleting knobs in certain orders.
1. Load up Synthmaker. You should get the default delay schematic.
2. At the top level, insert a PresetManager and connect it to a wireless output. You should now see the delay's four parameters when you browse for them and tweaking them should give the expected behaviour.
3. Enter the delay schematic, and delete the delay time knob. The second parameter should be <deleted>.
4. Now tweak the feedback, mix, and switch and note that FL Studio highlights the first three parameters in succession, even though the second parameter has been deleted.
My model is that Synthmaker re-enumerater the parameters but does not match them up with the names. So it tells FL Studio that the names are [0 feedback, 1 <deleted>, 2 mix, 3 on] but internally it skips the second parameter when sending events to FL Studio [0 feedback, 1 mix, 2 on], though when FL Studio sends automation to it Synthmaker takes care to take the second parameter into consideration.
Was the idea of deleted parameters added specifically for the FL Studio version? Then I think we know where the logic error lies...
Wrote something here? To have a post removed or your name hidden, write to [email protected].