Preset management

I'm going to implement preset functionality in my plug. After reading through some threads and suggestions i guess the best way to go would be using chunks. So i fiddled a bit with the IPlugChunks example. I could successfully create some presets but got some issues too. Since i don't fully understand what exactly some preset related IPlugBase methods, do i'd like to ask if someone could assist me with that. Most important is that i've no clue what (Un)SerializePresets/Params actually does. Same goes for ModifyCurrentPreset. One issue i couldn't fix so far is that the VST version in Reaper always names the first preset "-" while e.g. Cubase or the AU build shows the right name. Maybe someone could enlighten me?

I'm working on my own preset system right now, so hopefully I can give you some advice on stuff that has worked for me. I wanted presets that people could pass around to each other, and presets that would work in VST and RTAS/AAX. What I'm doing is saving the parameter number and it's value in a file. When the plugin loads, it scans all the preset files and saves them to a "Preset" object, which basically just has all the parameters and values that each preset file stores. Then to recall the parameters in the preset, just go through each paramID and load the param value with GetParam(paramID)->Set(value)

Hi bozmillar, thanks for your kind offer (at least i'm not feeling so lonely and totally lost anymore ;) ) . Seems we have the same goal. I'm still stuck with my trials. I just tried to leave chunks and instead using 'mPlug->DumpPresetSrcCode(presetFilePath.Get(),EParams) ;' But i get this error when it comes to EParams: 'illegal use of this type as an expression'. If i understand DumpPresetSrcCode correctly it should crawl thru each name of the EParams names and save the name and the appropriate value. Why does that error occur? Do i have to cast the Enum int values to the parameter name somehow?

Hi random_id, thanks for that example. This works pretty well! Moves me a big step ahead. I'll try to customize this method to make it suitable for my needs.