Skip to main content
babichfx
babichfx
Inspiring
October 28, 2022
Answered

Arbitrary and Standard parameter connection

  • October 28, 2022
  • 1 reply
  • 608 views

Thanks gods I sorted it out - how the Hue/Saturation works.

Video is attached.

So the sliders "Saturation" and "Lightness" just creating a key through USER_CHANGED_PARAM.

The keys added just to arbitrary param - "Channel Control".

After playing or randomly choosing frames on timeline you can see how arb param "Channel Control" is updating but not the sliders.

Sliders takes their updated values just on updating the whole Effects panel through UI_UPDATE hook.

Advantage of this approach is obvious - you can use the standard assets like sliders/color picker/checkbox....

Disadvantages are also clear - not interactive updates values and - more important for animation - inability to change or animate just one slider -- the key will be added for both ones. The one key for the whole arb data. And you are not able to freely change the Lightness, for example, if Saturation is already animated.

 

The way to solve that isues could be attempt to create the custom sliders in arb param scope and separate the animations. Like attach the different streams or so.... Not sure it is possible.

 

Is there any other ways/ideas?

This topic has been closed for replies.
Correct answer shachar carmi

err... i'm not sure what the question is, exactly.

adobe ship AE with 2 "Levels" effects, one where all values are concatenated to one keyframe stream, and another (Levels (Individual Controls)) where the params are independent. the user chooses the one or the other.

the choice to concat all params to one keyframe stream is delibarate (and not to my likings, btw...).

sooo... it's tather a design choice and not a technical constraint.

i'm probably missing the point here, so can you please clarify what's the problem you're facing?

1 reply

S
Community Expert
shachar carmiCommunity ExpertCorrect answer
Community Expert
October 28, 2022

err... i'm not sure what the question is, exactly.

adobe ship AE with 2 "Levels" effects, one where all values are concatenated to one keyframe stream, and another (Levels (Individual Controls)) where the params are independent. the user chooses the one or the other.

the choice to concat all params to one keyframe stream is delibarate (and not to my likings, btw...).

sooo... it's tather a design choice and not a technical constraint.

i'm probably missing the point here, so can you please clarify what's the problem you're facing?

    babichfx
    babichfxAuthor
    Inspiring
    October 28, 2022

    Yep, sorry for that, I was not clear.

    I have an Arb Aata on Arb Parameter which is the result of calculations and this result is changing the final picture during Render event. I have a bunch of independent sliders to control the calculations and I want to be able to key some of them, wire with another ones and etc.

    The Arb Parameter UI reflect the data to show the User how the picture will change. So it should be up to date, because the lag in UI update is confusing.

     

    As I see the Levels you meaning is working like I want. I can change the effect and on Arb Parameter and via the sliders. It is interesting, why Adobe didnt make a Hue/Saturation on the same way?
    Maybe the reason the Levels doesnt have any ArbData and the Histogam have just a visual purpose? All the calculations is happens during the Render event for every pixel and no need to interpolate any ArbData.

    Does this assumption is right? If so, this could mean I have to calculate the effect on the fly and not to store anything in ArbData.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices