-
Keyframes not working properly when using the Expression Slider Effect
Hi guys
I have a nested comp in a master comp. The nested comp has many other comps. In the master comp, i have 4 null objects. each has 10 expression sliders. Many of the comps in the job require a blur at certain times in the project, and as such, i have a blur effect to each. However i have used the expression pick whip to link each blur to the respective expression slider in the master comp.
This is where it starts to go strange. When i apply two keyframes from 0 – 100, the blur does not animate and no matter where i place my timeline needle in the comp, it always holds the value of the first keyframe. So if it should animate from 100 – 0 over 3 secs and i place my timeline marker at 5 seconds, it still holds the value of 100.
What could cause this?
Cheers
Chris -
5 Replies
-
strange.
only a quick suggestion, need to leave right now.how about:
valueAtTime (t)
[cant check the syntax right now]
this should fix it. or not?
payton -
Make sure your relative temporal placement is synchronous in each comp. Ideally each comp should have he exact same length to avoid any confusion. If you are offsetting in- and out points in relation to the main comp, sliders will actually work, but at a different time in th sub-comp. To compensate, subtract the in-point values from offset layers ort use the valueAtTime() method where appropriate like Tobias said.
Mylenium
[Pour Myl
-
Thanks for the replies guys. How would i write this into my expression if my expression looks like this?
comp(“MASTER DEPTH OF FIELD”).layer(“Shot 1 DOF”).effect(“S1 – Shot 2 behind Martha”)(“Slider”)
Cheers
Chris -
I think i understand now… i need to set t- “the number of frames” that each is delayed by. Thing is, everything is so burried, comps in comps in comps. Its a massive HD job and my computer isnt the fastest. It takes forever to open a comp. Is there not a way, where the time in the master comp can ripple down into the subcomps without the “- number of frames” code?
Thanks
Chris -
Nope. Time is a composition property unique to each one of them (as evident by the fact that each comp can have its own framerate, start time and a few other things). You have to take that bitter pill unfortunately.
Mylenium
[Pour Myl
Reply to this Discussion! Login or Sign Up