Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe After Effects Exporting problem/question

  • Exporting problem/question

    Posted by Matt Wiebe on July 30, 2008 at 3:29 pm

    I have a 43 minute 10 gig NTSC dv quicktime file in after effects.

    I brought the file into a new composition of the same format and just put on about 15 little title effects in throughout the file. Then I try to export it to the same settings.

    Now for some reason, my file is over 60 gigs in size, and when I put it into FCP, it is no longer a NTSC DV format.

    I’d like to export the file so it stays relatively similar to it’s original size and keep its same format. Any tips?

    (sorry if this issue has been discussed, I’m in a bit of a hurry and tried looking for older topics, but didn’t find anything after 10 minutes and gave up)

    Matt Wiebe replied 17 years, 9 months ago 5 Members · 5 Replies
  • 5 Replies
  • Thad Ciechanowski

    July 30, 2008 at 3:40 pm

    It sounds like you are exporting a QT with the animation codec, an uncompreesed format that will yeild the size you are describing.

    If you want the same size file, then you need to use the same codec you brought the clip in at; using a DV codec. Check your render settings and under “format options” be sure to select DV.

    This method however will recompress your footage. DV is already compressed and you may introduce unwanted artifacts. If you are only making titles, then why not export the titles only to FCP, save yourself a lot of rendering and maintain the quality of the original video.

    Good Luck

  • Simon Bonner

    July 30, 2008 at 3:42 pm

    You need to change the output module settings in the render queue (don’t use the export command, add to the render queue – hit ctrl+m). Click on where it says ‘lossless’ and alter the settings to quicktime, etc. You’re planning to edit the footage further, so don’t compress it too much.

    I don’t use FCP, so I’m not sure if it’s interpreting the rendered footage incorrectly upon import, but make sure that AE is intrepreting it correctly to begin with. For example, my copy of AE routinely misinterprets my 1.42 assets as 1.07. You can check this by looking at the hop of the project panel with the asset selected. Hit ctrl+f to change the way the asset is interpreted. Drag the file over the make new comp button at the bottom of the project panel to make a comp with those settings.

    Simon Bonner

    youtube.com/simonsaysFX

  • Tim Garber

    July 30, 2008 at 4:45 pm

    I concur. There are many reasons why not to do what you’re trying to do. First, as Thad said, you will degrade the DV clip even if it’s only imperceptibly these things get slowly compounded. Second, you are wasting precious productive time waiting for a render that was not needed. Third, manipulating all that material in AE is cumbersome so in addition to the wasted render time you spent time wrangling a very large clip.

    The one thing of value I will add to this thread is the suggestion that you render your titles separately. Make each one the duration it will be on-screen in your finished show. Have no video behind it and render them QT, Compression Animation, RGB+Alpha, Millions+, Premultiplied. You’ll get a relatively small file with high quality.

  • Brendan Coots

    July 30, 2008 at 6:11 pm

    I would follow Tim’s advice for sure.

    As a side note, I have found that “straight” alpha channels tend to work better since there is no premultiplication with white or black (which could be an issue if you have white titles with black drop shadows, etc) and straight alpha usually results in cleaner edges. Just my two cents!

    Brendan Coots
    Splitvision Digital
    http://www.splitvisiondigital.com

  • Matt Wiebe

    July 30, 2008 at 8:38 pm

    you’re totally right, I’m doing that now (rendering each title individually). Thanks all for the suggestions! Very very helpful.

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