Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy AIC render issue

  • AIC render issue

    Posted by Jay Fishback on March 24, 2011 at 7:29 pm

    Alright,

    I have a wedding edited out that was shot with both a 5d and 7d with the same recording settings. After encoding it to AIC (which I don’t always do, just wanted to try itwhich might be my first issue) I edited the video. Worked perfectly looks beautiful. However when I went to render the project the outcomes turns out extremely grainy, pixelated, wavy on transitions just to begin! I have tried various sequence settings and options and I just don’t know what I did wrong outside of being a novice… maybe next time I’ll go for 422. Please help. Muchas Gracias

    Jay Fishback replied 15 years, 1 month ago 3 Members · 8 Replies
  • 8 Replies
  • Kris Merkel

    March 24, 2011 at 8:15 pm

    My guess is that the OP is referring to the Apple Intermediate Codec. This codec was sort of a stopgap codec developed for HDV transcoding for those who did not want to jump through hoops to transcode their footage into an I frame codec such as DVCPro50.

    For now it is a lossy legacy codec and should not be used in lieu of ProRes.

    If you are using the EOS plugin for L&T you should set your prefs to transcode your files directly to your ProRes flavor of choice.



  • Jay Fishback

    March 24, 2011 at 8:24 pm

    Sorry Dave, I should have been more specific with my acronyms.

    Kris thanks for the info and for now I know not to use aic. Do you have any suggestions on what to do next instead of a re-edit?

  • Kris Merkel

    March 24, 2011 at 8:48 pm

    I’m a big fan of Pluraleyes to resync. I have not yet had the need to recapture footage using L&T so I don’t have a workflow handy. I’m doing a test now as I wait for compressor to pop my toast up.



  • Kris Merkel

    March 24, 2011 at 8:56 pm

    OK, try this.

    In your timeline, cmnd+a to select all the clips (assuming there is nothing in your timeline except video)

    right click or cmnd+click and select from the pulldown “Capture” this will open L&T and you will be prompted to make a choice. once you choose you will have to point L&T to the copy of the card you made before you started to capture your files.

    You didn’t make a copy of the card you say, well then use the original card. No original card either… well you could go re-shoot the wedding.

    All joking aside this should get you started. good luck



  • Michael Gissing

    March 24, 2011 at 10:30 pm

    [Kris Merkel] “right click or cmnd+click and select from the pulldown “Capture” this will open L&T”

    My understanding is that unless the original conversion to AIC was done with L&T, you can’t recapture this way. So if you used Compressor and chose AIC they you have lost the timecode reference and probably a reel number identifier necessary for L&T to recapture.

    AIC as has been stated is a porr quality legacy codec which should never be chosen over ProRes these days. Dave gave the link to Shane Ross’s tutorial. It explains the best workflow.

  • Kris Merkel

    March 25, 2011 at 1:07 am

    You bring up a good point. I didn’t think of the compressor workflow and assumed the OP had used the EOS utility in log and Transfer.



  • Jay Fishback

    March 25, 2011 at 3:32 pm

    so it sounds as if I need to just bite the bullet and capture the footage while using the old edit as a blueprint.

    thanks!

  • Jay Fishback

    March 30, 2011 at 3:45 pm

    Just wanted to post my way around this issue for the future people who are in this situation. But please keep in mind the work flow in the video Dave has posted. What I did to get around this issue without re-editing the whole project was in sequence settings. Clicking on render all YUV material in high-precision YUV with white as the process maximum and motion filtering quality set to normal. Also you must render the hole sequence at once. Rendering is also a long process this way and it may or may not be the situation you need. However at least it is a start to where you should be looking.

    Cheers and good luck,
    Jay

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