Preset management tutorial

[lalalandsynth]

I realize this whole preset system will be changed in the Alpha but I am not sure if it will solve this particular issue.
This whole loading of sounds currently is setting FS plugs apart from other plugins and something you dont expect , you expect your presets to be there when you load the plugin.

It seems to me that an autoload should be possible , looking into this.

[billv]

I made a Custom Preset manager that does what you need
It saves every preset to file, so the user presets are there on reload.
It works great. Took me ages to work out how to do it.
Scroll down the thread and use version 3...Hope you enjoy it
http://www.dsprobotics.com/support/viewtopic.php?f=3&t=2294

[lalalandsynth]

Yes, I saw that one , I am now trying to implement this into Ernst Hot preset manager and adding a save dialog.
Thanks a lot , this might just work for what I need.

The "Name" thing and then saving is also unusual compared to other plugins, so what I am trying to achieve is to open a dialog, name the preset and then its in the list.
This should be doable with combining the two preset managers.

[wlangfor@uoguelph.ca]

When I'm done making the universal knob/slider tooltip/help blurb/touchscreen input/keyboard input thingy I will make
this preset thing to spec. I will also make it do the following:

- load from a .txt file or .ini a list of newly made presets that automatically adds it to the default fruity preset list
- provide simple save preset options for programmers which automatically saves the new preset to a text file or .fxb, .fxp;
- Have it so the file options can be turned on or off;
- make sure there is a nested tree style like serum

[lalalandsynth]

Excellent, looking forward to it!

[Spogg]

I’ve reviewed the tutorial and made a lot of changes. There are several new additions included, so it might be worth a re-read.

Thank you to Martin Vicanek for raising and solving one of the new points.

The new zip v1.21 is in the original post too.

[R&R]

Thanks Spogg!


So I should just be able to connect the most crucial parameters first... to bump them up the parameter list inside the daw then?

[RJHollins]

Something I use to do was EXPORT a TXT file from the PreSet Manager.

That allowed me to review all the assignments [and any missed, duplicates].

[Spogg]

Thanks Spogg!


So I should just be able to connect the most crucial parameters first... to bump them up the parameter list inside the daw then?

Martin came up with the method in the tutorial. He told me the only way was to have unique names for all the “P” wireless preset connectors, then the order those were connected would be reflected in the text file. I didn’t try it myself, but I trust Martin!
I must admit I personally wouldn’t do this because, in Reaper, you can just touch a knob and it can be recorded. But Martin made the point that he wanted to have some parameters which don’t have UI controls, so he could use the generic sliders in the DAW to “trim” certain parameters, like in an “expert” mode.

[R&R]

I didn’t try it myself, but I trust Martin!

I don't trust neither of you two... You both create suspiciously advanced things in FS. Too advanced.
Aliens from outer space

Have to try this later. Common parameters like Cutoff, Reso etc... or grouping of them at the top of the list seems like a great thing.

Something I use to do was EXPORT a TXT file from the PreSet Manager.

That allowed me to review all the assignments [and any missed, duplicates].

You mean the parameter naming?
I noticed it can become a nightmare keeping track of naming...