Forum Replies Created

  • Thomas Ginelli

    July 24, 2013 at 3:16 pm in reply to: Extending comp in AE

    Well that is not the case… to explain better:

    I’d need a script which literally speeds up or slows down a keyframed animation. Like at, say, 30fps, a keyframe at 300 is at the 10 second mark, and after standard AE conversion to 25 fps it gets to on frame 250, right? Still at 10 seconds.

    What I wished instead, is that the keyframe stayed at frame 300 after conversion, so effectively it was at the 12 second mark… slowed down.

    In some 3d apps like 3ds time there is a global time scale tool. Not in AE I think? I understand it’s different when working with video footages, but just for keyframes that would be helpful.

    The need for such conversion came from a newb animator, who did not realize he was working in 30fps instead of 25, and relied on frame numbers rather than time to get his parts matched with other sequences. Kinda complicated. Ended up rendering his comps to frames and importing them in different fps, to avoid slowing down final comp render.

    What do you mean by: “You can also change the time display to the corrected frame rate as well.” – maybe it’s something I overlooked?

  • Thomas Ginelli

    July 23, 2013 at 9:56 am in reply to: Extending comp in AE

    I can’t believe that nobody wrote a script to make that easier. I would surely pay for that!

    Several times I imported comps from colleagues that were right in timing – but in wrong FPS. And when I put them into my comp they were too slow or too fast! All I needed was an option to change fps while leaving the keyframes and layers where they were, like keyframe on frame 100 stays on 100 after fps change… no luck there.

    ALT-scaling keyframes is pretty out of the question when you have 50+ animated layers. AE Re-timing (or even Twixtor) slows things down and can cause problems.

  • Guess what… it got me right where I wanted to be!

    Thank you! (again;)

  • This worked! Even layer-specific stuff like seedRandom(index) is working as expected!

    Thank you Dan!

  • Indeed Copy Expression Only is a viable option, however not as automated as I’d like.

    Your suggestion about using a text layer and JS eval() is most interesting, however I’m not sure how that should work. I tried making a text layer with a simple “i=15;” statement in it and then tried to evaluate it from another layer’s rotate property:

    eval(thisComp.layer(“SCRIPT_LAYER”).text.sourceText)

    and AE says that “a Number, Array or Property is needed” while it gets TextProperty instead.

    Can you tell me how the line of code should look like?

    Regards,
    Thomas

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy