default in presetParameter primitiv ?

[Nubeat7]

hallo, anybody here knows what for the default input at the presetParameter primitiv is? i couldn`t find it in the component reference! if i send a default value to this input what can i do with it? or what does it do whit it? how can i recall it when there is a value at this input? because the only working way i found out is to put a lastSwitch before the value input where one is the value and the other is default so i can trigger the default value if i want to set it,i don`t need the default input for this! but it didn`t work with the default input of the presetParameter.....

[trogluddite]

AFAIK the only thing it is used for is when you edit the Preset Manager to have more presets in the bank. The default is used to create the new blank patches, so that they don't have silly values that bust your eardrums.

[Nubeat7]

ok, thats good to know, thanks trogluddite!

[RJHollins]

oh ... I very much tried to understand this ... but nahhh.

I'm using my first Preset Manager as, well a PM that can store preset. I have 14 slots available ...

But I noticed flipping through the preset [that I hadn't done anything to], my knobs, selectors, etc were jumping around to various settings ... it looked cool, kinda fun ... but quickly over that, I wanted a default value to be in each of these presets ... as a safe 'starting' point.

I ended up using a PM that had Copy/Paste feature [kinda nice] to default set all available slots ... but reading this thread indicates that I could have used a better method ?!?!

I sure could use more info on this ... would be useful for the next project.

Thanks!

[Nubeat7]

i normally have added an init trigger to the menu of the PM which sets the actual preset to default..

[kortezzzz]

Thanks for sharing this info, Trog. how exactly "default" works ? only with single presets? or with banks too? Another strange behavior of the PM: after compiling a dll. vst file, it loads the defaut presets as the lastest settings.
when i'm trying to load up some other banks i'v created, it freaks out. its like the default bank has conflicts with the new bank. the only way the preset manager acts correctly, is when using daw's internal fxb. load\save system.
so decided not to take any risks and guide the user to use this fxb. system, unless he wants to save a new single preset (i made a one click "save in place" button for that, with no other PM buttons or menus).
any better ideas?...

[Nubeat7]

never had troubles with loading a presetbank..

[kortezzzz]

mmm... must be something im doing wrong its like the PM doesn't clear the old bank completely, but loading the new one in to it or something and the all stuff get mixed. should i trigger something in the PM primitive to clear the already loaded bank before i load a new one?

[Nubeat7]

maybe, your presets are not right, if a preset parameters are named wrong or have wrong value ranges everything can get fucked up, i always have troubles with that when i update a plugin and i have renamed parameters or added new ones - that all makes troubles when using old preset banks.. maybe also the size of the bank could be different...

[kortezzzz]

thank you for your suggestions, nubeat7. i will check everything again. maybe i have some "double names" there, or some wrong names with unique Characters that can not be readden by the PM (?).
anyway, whats Encouraging me is the fact that the PM primitive acts correctly when you do things right
(you said so).

thanks.