Forum Replies Created

Page 243 of 277
  • Filip Vandueren

    July 26, 2005 at 1:10 pm in reply to: Piexelated Animated Text

    Hey Mike;

    [Rant]
    What’s happening is the crappy implementation of continuous rasterizing of vector-text.
    I remember the first time I used it: I was really angry!
    How could Adobe let this pass quality control: the first thing anyone would want to do with Cont. rasters is scale up text, right ?
    [/Rant]

    Anyways: enabling Motion Blur helps, but slows you down (esp. on 3D layers) and might not be the look you want if there’s faster motion too.
    A gaussian or fast blur as small as 0.3 pixels applied to the text layer, is enough to cure the problem and if you’re outputting to video, can never hurt.

  • Filip Vandueren

    July 26, 2005 at 1:00 pm in reply to: Piexelated Animated Text

    This animation looks fine:

    It is however interlaced footage (jagged edges!), so there are a couple of things that might be going wrong:

    – you have the wrong field order (that would cause jittery motion, not true blockyness)
    – you’re outputting only 1 field to beta.

    Solution to the first is simple. change your output settings to render in the correct fieldorder
    The second one:
    I don’t know how exactly you’re getting it out of the Blackmagic,
    But after effects usually throws away one field for displaying on the computer monitor.
    Most NLE’s like Final Cut Pro do the same on screen, and sometimes also to the realtime monitor (depending on what quality you’re working in)

    In effect these de-interlacing options are reducing the vertical resolution in half, so there come the blocks.

    So the problem is in how you’re outputting to tape.

  • Filip Vandueren

    July 26, 2005 at 12:45 pm in reply to: Fading Up and Down

    maybe this is handier:
    <code>
    fadeInTime=0.5; // in seconds
    fadeOutTime=0.5; // in seconds
    i=inPoint; o=outPoint; h=i+(o-i)/2;
    time < h ? linear(time, i, i+ fadeInTime,0,100) : linear(time, o-fadeOutTime, o,100,00);
    </code>
    just set fadeInTime=0
    also in the last line you can change the two occurences of “linear” to “ease” for a smoother fader.

  • Filip Vandueren

    July 26, 2005 at 12:45 pm in reply to: Fading Up and Down

    maybe this is handier:
    <code>
    fadeInTime=0.5; // in seconds
    fadeOutTime=0.5; // in seconds
    i=inPoint; o=outPoint; h=i+(o-i)/2;
    time < h ? linear(time, i, i+ fadeInTime,0,100) : linear(time, o-fadeOutTime, o,100,00);
    </code>
    just set fadeInTime=0
    also in the last line you can change the two occurences of “linear” to “ease” for a smoother fader.

  • Filip Vandueren

    July 25, 2005 at 9:27 pm in reply to: Fading Up and Down

    Oops, something went wrong.
    if you’re watching the e-mail it should be okay,
    but on the website there’s an error because there’s a < character in there, here it is again (for the website):
    fadeTime=0.5; // in seconds
    i=inPoint; o=outPoint; h=i+(o-i)/2;

    time < h ? linear(time, i, i+fadeTime,0,100) : linear(time, o-fadeTime, o,100,00);

  • Filip Vandueren

    July 25, 2005 at 9:27 pm in reply to: Fading Up and Down

    Oops, something went wrong.
    if you’re watching the e-mail it should be okay,
    but on the website there’s an error because there’s a < character in there, here it is again (for the website):
    fadeTime=0.5; // in seconds
    i=inPoint; o=outPoint; h=i+(o-i)/2;

    time < h ? linear(time, i, i+fadeTime,0,100) : linear(time, o-fadeTime, o,100,00);

  • Filip Vandueren

    July 25, 2005 at 8:44 pm in reply to: Fading Up and Down

    Here’s the expression for opacity:
    You can make an Animation Preset out of it.


    fadeTime=0.5; // in seconds
    i=inPoint; o=outPoint; h=i+(o-i)/2;
    time

    'cause it is an expression, it does slow down rendering:
    but hey: it fixes the laziness 😉

  • Filip Vandueren

    July 25, 2005 at 8:44 pm in reply to: Fading Up and Down

    Here’s the expression for opacity:
    You can make an Animation Preset out of it.


    fadeTime=0.5; // in seconds
    i=inPoint; o=outPoint; h=i+(o-i)/2;
    time

    'cause it is an expression, it does slow down rendering:
    but hey: it fixes the laziness 😉

  • Filip Vandueren

    July 25, 2005 at 1:49 pm in reply to: Does anyone out there ever have this problem?

    Where they audio-files that AE imported without problem in the first place ?

    Because sometimes I use .sd2 files, and AE won’t import them untill I tell it they’re quicktime movies, QT handles them fine.
    Then sometimes they won’t load aymore, and I have to re-import. Not sure if they ever crashed me though.

  • Filip Vandueren

    July 25, 2005 at 1:46 pm in reply to: Error’s Everywhere!

    hold down shift when you go into the preferences to get to the ‘secret’ prefs
    You can set an automatic RAM-purge every X frames during rendering there.

    Hopefully that helps.

Page 243 of 277

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