Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy FCP not recognizing its own renders- please help!

  • FCP not recognizing its own renders- please help!

    Posted by Samuel Frazier on December 19, 2005 at 10:43 pm

    I’m working on a film-originated project that I have ‘offline’ DV25 clips and ‘online’ uncompressed digibeta clips for and am editing on a 23.98 timeline. I just substituted the online clips for the offline ones and everything looks fine during playback.
    However, the first time I quit the project and opened it back up FCP gave me the standard warning about that the renders I made of the online clips were not optimized for FCP. Weird, I thought, since FCP made the renders. Still, everything looked good from the timeline so I exported to Compressor and made a 24p mpeg2 file of the movie. It looks very aliased along edges and most text looks crappy. The aliasing is especially noticeable compared to 24p mpeg2 clips made from the offline DV25 clips.
    The general rule when something makes no sense is that the user did something wrong. I’m trying to figure out what that can be, but it’s escaping me at the moment. I know that renders can get fouled up over time and after a number of changes, but as I made the online version on a new sequence I wouldn’t think that would be the problem. Still, that’s the only thing I can think to try.
    So, does anyone have any advice here, or has FCP just taken leave of its senses? Thanks ahead of time for any help!

    Samuel Frazier replied 20 years, 5 months ago 1 Member · 1 Reply
  • 1 Reply
  • Samuel Frazier

    December 20, 2005 at 12:36 am

    Just exported a self contained version of the online movie (keeping the settings unchanged as 23.98 10 bit uncompressed) then opened that file in Compressor. This time, no aliasing. I’m still a bit confused though. Does this make sense to anyone?

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