Very useful thanks :) I've tried to use it to reset all my TOP custom parameters eg levels, gamma etc but it doesn't reset them if I add the custom parameter names to the list, is there anything else I need to do to allow this?
Heyo, it is not supposed to reset OP params to default (which is what you seem to want). The custom parameters list are relevant only if you have a COMP with a custom parameter whose purpose is to reset the internals of said COMP. For example you have a Reset pulse custom parameter that triggers running a script, or is simply linked to other pulse signals inside the COMP. A TOP OP params like Level's gamma is not a custom parameter. Only COMPs (and script ops) have custom params! And then again, all this component does is perform a "pulse()" on params it finds relevant to pulse(). Hope this clears it!
@@FunctionStore Ok I see thanks :) I wonder if there is also a way to reset all Op custom params to the default value remotely, with a button like this
@@NicholasCarn it could be possible - I like to say that in TD anything is possible -, but it's not really what this component was designed for so you'd need a lot of modifications. To re-iterate this comp only looks for TOP/CHOP/SOP/DAT parameters only in certain operator types that are called "reset" or "clear" or similar and pulses them. Furthermore with COMPs you can define custom parameters (when you right click a COMP you can edit/add the custom parameters in a separate menu) that you would want pulsed. - To return a parameter's value back to its default you'd call op('level1').par.opacity.val = op('level1').par.opacity.default for example. But your wish fails at the fact that this component ignores stuff like the level TOP since it doesn't have any reset pars it could pulse. I don't really see a use-case for what you want to achieve to be honest, I'd rather suggest you look into preset systems. One that I use frequently is AlphaMoonbase's TauCeti package, you can find it on olib.amb-service.net and there are also some explanatory videos.
@@FunctionStore Thanks for the info, I've seen and tried some of the custom preset systems created, but I'm hoping that Derivative creates a more permanent preset management system for components because they all seem to break easily and need maintenance in my experience.
@@NicholasCarn I've been using TauCeti for a long time without problem, and AlphaMoonbase is actively keeping it going as I am sure it is a tool he also uses daily
sick effect!
Very nice - thanks :-)
Great! Thank you for creating such amazing components!
My pleasure!
Ah so useful! Excellent work 😁
Cheers man!
Very useful thanks :) I've tried to use it to reset all my TOP custom parameters eg levels, gamma etc but it doesn't reset them if I add the custom parameter names to the list, is there anything else I need to do to allow this?
Heyo, it is not supposed to reset OP params to default (which is what you seem to want). The custom parameters list are relevant only if you have a COMP with a custom parameter whose purpose is to reset the internals of said COMP. For example you have a Reset pulse custom parameter that triggers running a script, or is simply linked to other pulse signals inside the COMP.
A TOP OP params like Level's gamma is not a custom parameter. Only COMPs (and script ops) have custom params!
And then again, all this component does is perform a "pulse()" on params it finds relevant to pulse().
Hope this clears it!
@@FunctionStore Ok I see thanks :) I wonder if there is also a way to reset all Op custom params to the default value remotely, with a button like this
@@NicholasCarn it could be possible - I like to say that in TD anything is possible -, but it's not really what this component was designed for so you'd need a lot of modifications.
To re-iterate this comp only looks for TOP/CHOP/SOP/DAT parameters only in certain operator types that are called "reset" or "clear" or similar and pulses them. Furthermore with COMPs you can define custom parameters (when you right click a COMP you can edit/add the custom parameters in a separate menu) that you would want pulsed.
-
To return a parameter's value back to its default you'd call op('level1').par.opacity.val = op('level1').par.opacity.default for example. But your wish fails at the fact that this component ignores stuff like the level TOP since it doesn't have any reset pars it could pulse.
I don't really see a use-case for what you want to achieve to be honest, I'd rather suggest you look into preset systems. One that I use frequently is AlphaMoonbase's TauCeti package, you can find it on olib.amb-service.net and there are also some explanatory videos.
@@FunctionStore Thanks for the info, I've seen and tried some of the custom preset systems created, but I'm hoping that Derivative creates a more permanent preset management system for components because they all seem to break easily and need maintenance in my experience.
@@NicholasCarn I've been using TauCeti for a long time without problem, and AlphaMoonbase is actively keeping it going as I am sure it is a tool he also uses daily