What does 'Default value' do?

[nix]

Hi! I was wondering what do 'Default value' and 'Send automation value to host' on the 'Preset Parameter' primitive do?- do they do anything? I'm not new but still, was wondering. It's not in the Component Reference. I'm having some funny behaviour with the default toolbox knob
cheers, and enjoy the tek

edit,oh- I sussed the default value, when you create blank presets, it populates,
what about 'Send automation value to host'?, can we just leave it true?

[nix]

u can leave it true(the send automation recording), no need to switch it afai can tell
edit- hmm, it can be false too
indeed it can have no input and still u can record automation, and it will animate ur knob

[Spogg]

Hi Nix

On most knobs the Default value is also what is set when you cntrl-click on the knob.

Regarding Automation I think it depends on the DAW. In Reaper the automation is recorded when a preset parameter value is changed. You enable automation in the DAW and it seems to ignore the Automation setting on the knob. I always leave it set to true. Of course you need to enable "preset" for that to work.
I'm not sure about how this relates to the VST spec.

Cheers

Spogg

[nix]

thanks!
Maybe it matters in different DAWS.
The automation recording is pretty easy in FL20, which I am using,
I should be fine to use Orion too.
hmm, on the Ruby stock knob the reset to default cntrl click seems not working,
I'll keep testing

[tulamide]

I always thought that specific send automation option was for "the other way round". Normally, this is what a plugin does (from the specs manual):

Parameters are the individual parameter settings the user can adjust.
A VST host can automate these parameters.
Programs are a complete set of parameters that refer to the current state of the plug-in.
Banks are a collection of Program objects.

From the host application’s point of view, a VST Plug-In is a black box with an arbitrary number of
inputs, outputs, and associated parameters. The Host needs no knowledge of the plug-in process to
be able to use it.
The plug-in process can use whatever parameters it wishes, internally to the process, but it can
choose to allow the changes to user parameters to be automated by the host, if the host application
wishes to do so.

...In this case the parameter directly reflects the ‘value’ used in our processing method. When the
user ‘turns the dial’ on a generic plug interface it is this value that gets swept between 0.0 & 1.0
as the
setParameter()
function gets called. If you want a different relationship between the
parameters that are automated by the host and what is actually used in your processing method,
then that’s up to you to do the mapping.

(Flowstone does not support this mapping. We are on the "direct" path.)

Sraight forward. We set parameters, but also allow the host to send us a value that we then use for our knob or whatever else. That would be "receive".
So "send automation" in my mind is meant to control other things that are outside of the plugin, maybe a DAWs track automation. Something like this. But I never bothered with it or test anything.

Btw., just by reading through the specs I found something I wasn't aware about yet (as sad as it is). We all name our presets properly, at latest after you read Spogg's preset guide. Now, the preset strings are special! Didn't know that! Again, from the specs manual, regarding parameter's name, display and label:

Please be aware that the string lengths supported by the default VST interface are normally
limited to 24 characters. If you copy too much data into the buffers provided, you will break the
host application. Don’t do it.

The default interface is what the DAW uses if it can't open the GUI (or if there is no GUI defined). In Reaper, you can switch to the default interface at any time by the click of a button.
In other words: Using more than 24 chars is undefined and may or may not work.

[nix]

hey thanks on the long preset names,
that could be a problem.
In this test->

3081knob example_0.fsm

(127.59 KiB) Downloaded 928 times

-is it plain that 'send automation recording to host' may not do anything?

The default in the old knob Mr.Spogg was set by a key command, I looked at it
IMO- the default value is cool, minor thing but, I like it now, can use it

[tulamide]

hey thanks on the long preset names,
that could be a problem.
In this test->

3081knob example_0.fsm

-is it plain that 'send automation recording to host' may not do anything?

The default in the old knob Mr.Spogg was set by a key command, I looked at it
IMO- the default value is cool, minor thing but, I like it now, can use it

That's what I'm talking about in my last post. You don't see an effect, since you'd need something on the DAW side to receive those parameter recordings.

[nix]

I'm using FL20->

knobbo test90.png (97.58 KiB) Viewed 17136 times

The animated knob is still playing back atm without any bool on the send recording pin

[tulamide]

I'm using FL20->

knobbo test90.png

The animated knob is still playing back atm without any bool on the send recording pin

You still haven't understood. What you are showing is the receiving part of my post, not the sending part. The sending part would be, that you enable send automation recording, and in your DAW you enable, say your mixer's volume slider to receive these values and move up and down accordingly.

[nix]

oh really
that would be amazing
the plug itself is sending and receiving the automation clip

edit-hmmm- so how do I send to mixer slider?