VST param help if possible ????

[tinkergnome]

ok ... i got this one schematic that is a slider that toggles/adjusts a text number. the problem is,.... when
i had it loaded up in my VST host.... then i saved the workspace file that the item was within, it didn't save
slider/numeric settings. what would i have to do in order for the slider value to be recorded as per a last/previous
(before saving the workspace in the VST host) adjustment ???? i know this question might have been asked many
times, i was having a slight bit of trouble figuring it out without thinking i'd have to build a whole slew of front
panel imagery/mechanical parts internally to make it happen. i understood by looking @ the library of widgets
that the VST param is a necessary item to use ... i'm just not sure of any other parts needed/or how to connect
wires to make it work correctly.

[tektoog]

Don't you have a bit of an OSM to visualize what you're talking about?

[tinkergnome]

tektoog: Don't you have a bit of an OSM to visualize what you're talking about?

well i could upload the *.osm? ..... i'm not really sure how to upload an image to this place so it
could immediately be seen.

[tektoog]

Try the knob collection there: viewtopic.php?f=7&t=10207
There are some sliders with preset recall... just add a read out on exit...it should display the correct value saved with preset... (add a preset manager in the collection schematic..you'll see all kknobs and sliders recall values per preset)

[tinkergnome]

ok .... perhaps my question wasn't quite clear.....

what i want to do is when this plugin is in a VST host and i adjust a slider that when
i save the workspace file in the VST host & then reopen the workspace file the slider
would have saved its last moved position.

[Mo]

what i want to do is when this plugin is in a VST host and i adjust a slider that when
i save the workspace file in the VST host & then reopen the workspace file the slider
would have saved its last moved position.

As tektoog mentioned, you need a preset manager and different preset names for all control parameters.

[infuzion]

We really need the OSM to see what is going on.

[tinkergnome]

very well..... i'll post it here, though, i've prolly wired it completely wrong. i was hoping someone could
possibly help me understand how to connect wires of inputs/outputs/etc in order for the control(s) to save
properly when i were to save a workspace file within the VST host and that the control(s) would have last
saved adjusted position.

[tektoog]

Hey,
I think you're seeing things way more complicated than they actually are.....
Try that:

~VSTparamsSAVE [FIX].osm

I guess this is what you want....Or I just didn't get it at all....

[tinkergnome]

one thing i remembered from my working with max/msp..... i was able to create a group of components
that when i were to adjust a certain control ... it would overwrite the previous setting/variable/etc within
a preset type object and the parameter would reflect accordingly when i were to relaunch the project if
needing any further editing. effectively within the max/msp project i would have the certain control tied to this conglomeration of "autosave" components,.... making a single adjustment had literally caused a save operation
to the whole project. i suppose that may be radically different in synthmaker.... i wondered if its possible to
have a control overwrite a certain singular preset/program & attempt to automatically save the project so
when the project is reloaded it would reflect the previous change to that control ????

[tinkergnome]

another idea i was thinking about,..... if the toggling of the control could somehow cause the *.OSM to save itself
without calling up the file dialog window, that was part of the autosave type componentry i developed in max/map.
i was wondering if that were ever possible in synthmaker. that would most certainly work, i would think.

[infuzion]

i wondered if its possible to have a control overwrite a certain singular preset/program & attempt to automatically save the project so when the project is reloaded it would reflect the previous change to that control ????

SM's Preset Manager has "Save Program" which saves only the current patch, not the entire bank (ALL).

[tinkergnome]

after careful consideration of using the preset manager aspect/suggested ideas... i've done some examining
of the behavior within a few of the components that are wired into this new project and i believe to have
accomplished my goal for the moment. this test model i've built seems to show potential in how i would
expect it to work. i'm not aware of any potential aberrant signal flow/disruption to compromise the project,
meaning, i don't know if by the connections wired the way it is will cause any catastrophic errors with
either the *.osm or the synthmaker program,.... the way i have the components connected seem to work
right for how i want it to behave. i have not tested in a VST host though it should act similarly.

[tektoog]

after careful consideration of using the preset manager aspect/suggested ideas...

Oh yes.... another thing to consider....
It's when someone spends some time for your matter, the less little thing to do is to thank him for the time he spent on it...
I don't wanna be rude.... but after 3 posts of personal outloud thinking of your part...I'm still waiting for a:
1)This is not what I want...just go f..K yourself you stupid A..H...
2)This is not what I want...BUT THANKS anyway for trying to help me out...
3) Yeah you got it.... THANKS for helping me.....
If you still want some help from this forum,or at least from me, try to apply the common rules of politness...which I guess are borderless...
I wish you success in your future projects....

[tinkergnome]

well ... i'm thankful for your help/assistance. don't think that my last response was anything disrespectful. it wasn't.
perhaps you've misunderstood my response as something insulting?, but i wasn't trying to do that. i was trying to figure out the wiring aspect of it, and i suspected i could find a work-around or a way that could lend simplicity as i am still a new person working in this VST authoring environment. i've also had discussions about similar problems in solving with patches in the past with the max/msp forum. some of the people there were contending that some things could not be possible/or only built a certain way, but i found a way or so around some of the things what they suggested. so i hope you won't think i had just ignored your advice to help me. i am thankful to you & for others who could lend me assistance.