Reuben Lara
Forum Replies Created
-
Hey Dan: why is the result of the expression cumulative to any values that may have already been in the orientation fields? For example, if I scrub either the x,y, or z values to anything other than 0,0,0 it seems to offset the expression’s calculation. Should any expression’s result override the property’s values by default? Are there any expression methods that will force an override?
-
Amazing, thank you!!
-
Thanks Trent. Yes this is what I ended up doing to get it out the door. But either this is a bug that hasn’t been fixed for a long time (there have been threads on the issue for several years now) or there is a switch (or a at least a reason) somewhere that I don’t know about!
-
Thanks for the response. It doesn’t happen often, but on expression heavy comps it’s happened to me at least three times. In this particular comp, i have a bunch of layers being driven by expressions at the same time (about 30). They are 2D layers that are following a 3D layer’s position and scale using toComp and some other complex math that creates a nice relationship between 2D and 3D. They all RAM preview and output render fine, except for two layers where the 3D nulls driving them also have other expressions of their own. This seems to be the only difference I can detect right now.
Either way, those two layers RAM preview quickly, perfectly and accurately every time, on any resolution level. But on render output, those two 2D layers just ignore the expressions that are assigned to them. I’m just using render queue, but same happens with AME.
-
After your comment about what exactly i wanted to convert I did some tinkering with the relationship between my 2D layer and my 3D layer and realised that there are too many arbitrary scenarios to be able to account for with a script. My client needs to export 2D AE layers as XML into Final Cut Pro in a way that mimics position, scale and rotation in FCP, accounting for custom eases etc. I’ve got a whole Script UI panel working surprisingly consistently for 90% of possible scenarios. But i think the “match 2D position and rotation to 3D path auto-orient orientation” might be asking too much for this kind of inter-app translation. Thanks for taking the time to respond either way!
-
yes good point. specifically, just grabbing the Z rotation would be enough in my case.
-
I have a 2D layer position set to get its world coordinates from a 3D layer’s (“Layer 1” in the example above) auto-oriented path animation. It tracks perfectly, but now I’d like it to also inherit rotation values. Since the the 2D layer doesn’t have an “orientation” property, how can I translate “Layer 1″s orientation into a 2D rotation? Or is that even possible? I’ve used your “Case Study: 2D Auto Orientation” expression to go from 2D to 2D, but I can’t figure out how to combine it with this scenario. Thanks!
-
excellent, thank you as always! your dedication to providing answers here is mesmerising, we all appreciate your commitment!
-
Thanks will look into that!
-
That was it, thanks so much! (And thank you for being some kind of omnipresent scripting genie that has helped so many people over the years… much appreciated!)
Reuben