Hi @pennytron, this is possible.
this is a little confusing so I will try to explain it clearly.
when setting up a property in automation toolkit, every property have it’s type (number, text, layer, item, boolean, property) after selecting the property you want to set, automation toolkit gives you the option to select only properties with the same type(text can accept number and boolean) so if the property type is number the “name” property won’t show up because it’s type is text and number won’t accept text.
In your case the problem is the same, when looping on the properties of an effect, there is the “value” property that contains the value, because you are looping through the properties automation toolkit assumes that the “value” property type is by default “text” because it can’t know what is the real type,
so when you tried to set up the number variable “value” property the effect’s “value” text property didn’t show up for the same reason, number can’t accept text.
there are 2 solutions for this problem:
- change the variable type to text, then the effect’s “value” property will show up(but you won’t be able use this variable in other number properties or do math).
- there is a number variable action called “convert text to number”, the action takes a text and convert to a number and then sets the number as the value of the number variable so you can use this action instead of using the “set” automation line.
if there are keyframes the “value” property will return the value at frame 0, if you want the value at the current time you can set the “time” property to the comp time indicator. if you want the value of a specific keyframe you will need to loop on the “keyframes in property”.
example - FindSliderValue2.json (6.4 KB)
hope this all makes sense,