Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Weird renders in FCP

  • Weird renders in FCP

    Posted by Berenger Capmany on January 14, 2008 at 6:22 pm

    Hello,

    Dear Forum, we have a problem… suddenly in long projects renders start to behave weirly..cross dissolves swaps (showing one field graphic on layer 2, field 2 video on layer 1) rendering the wrong graphic at the wrong place, etc.. (an assortement weird results).. or just not showing the image. As the problem gets worse there is no way to render a single graphic rigth on place.

    It’s happening ONLY with still images (sized at 1920×1080 RGB) and AE animations with alpha channel (the lower thirds).

    The more bizarre thing is when you have a complete rendered project, rendering still per still with Command+R when the Timeline is rendered and plays back fine.. If a Quicktime movie with current settings is exported.. the resulting movie have stills with problems or just not rendered.

    The Timeline without renders, with green preview bars, works fine!

    I tried to copy and paste the edit into a clean new project, on a fresh created user; do save as to refresh the project database, flush completely the renders and the render queue (this works for the first stills you render) and it’s still happening…

    I sincerely thing this is a bug on FCP 6.0.2 which it’s messing with the render cache..

    this is happening in 1920×1080 50i ProResHQ and in two different computers MacPro quadcore 2.66 and a G5 Quad.

    Anyone with similar problems?
    Clues to continue looking for a solution?

    thanks!

    Jeremy Garchow replied 18 years, 3 months ago 7 Members · 28 Replies
  • 28 Replies
  • Jeremy Garchow

    January 14, 2008 at 6:37 pm

    Does it sound anything like this?

    https://forums.creativecow.net/readpost/8/966491

    If so, then yes I have seen weird results.

    Jeremy

  • Matthew Nelson

    January 14, 2008 at 6:38 pm

    Having a similar issue. In my case it happens with footage that has an alpha generated by composite mode travel matte luma or by a keying filter. When I render a sequence in total I get all sorts of problems like some weird new composite mode was set, freeze frames and time shifts. When I render clip by clip I don’t have any problems.

    Apple pro video support suggests it’s corrupted media. Ok but it seems isolated to alpha composites. I was thinking it was a bandwidth issue with my XSan but knowing I am not alone in this I’ll be going back to Apple.

    Matt

  • Jeremy Garchow

    January 14, 2008 at 6:40 pm

    Oh man. I am starting to think that I am not crazy.

    Jeremy

  • Berenger Capmany

    January 14, 2008 at 6:54 pm

    Well at least, I’m not alone in this world!

    In my case it happens only with stills and also Alpha channel movies.
    The stills produce the effect on something as simple just have a video on L1.. and still on L2 with cross dissolves at the edges.

    Render still per still worked sometimes.. specially on the first render (on preview, everything plays back okay) a soon you start to re-render or modify and render.. event that workaround is not working.

    Another werid thing is, even having the complete Timeline rendered manually… if you export a quicktime movie, the resulting movie have the crazy renders.

    I have tried to render with the two 10 bit YUV modes.
    Also I have found that flushing the render queue on RenderManager.. resets the problem and you can, again, render the timeline still by still.

    Do you think it’s something related to Prores Codec?

  • Jeremy Garchow

    January 14, 2008 at 7:06 pm

    [Berenger Capmany] “Do you think it’s something related to Prores Codec? “

    I simply don’t know. It’s the only codec that I get these problems on, and it is intermittent and doesn’t happen all the time. I hate to spread bad rumors and false problems, but it seems that this might be a legit issue.

    Jeremy

  • Matthew Nelson

    January 14, 2008 at 7:09 pm

    Well Jeremy if you’re crazy you’re not alone.

    So we can compare notes, I’m working with a mix of 10bit SD and ProRes HQ 720P in a 10bit SD sequence. All media was captured using a Decklink HD Extreme 6.6.2. I am running FCP 6.0.2, QT 7.3, OSX 10.4.11, XSAN 1.4.2 all on Dual Quad Mac pros with 8GB RAM with the NVidia GeForce 7300 GT card. I am compositing footage using a mix of travel matte luma, chroma key and animation with embedded alpha.

    My render setting is set to Best with 100% on frame and size. My sequences range from 5min to 13min in length. I have 4 edit bays each are identical in setup, hardware and software and this issue has manifested itself on each system.

  • Berenger Capmany

    January 14, 2008 at 7:10 pm

    Well I have read the entire thread…

    In our systems we have Decklinlk HD extreme..
    Also reinstalled drivers with no difference…

    no retiming in my case… just still images at 100% (sized 1920×1080) with a simple cross dissolve.

    working in PAL frequencies 1080 50i, also ProResHQ

    Also deleted renders ans render queue, but not constant frames..

    Our Projects are ONE hour long.. with around 6 hours of captures. Project Size ranging from 17 Mb to 100 MB

    No plug-ins also.

    I will try the zero value plug-in trick.. and come back to you…

  • Chris Babbitt

    January 14, 2008 at 7:37 pm

    There is a limit in FCP to the size of images that it can accept. I’m not sure what that is, but you might try reducing the size of your stills and see what happens.

  • Berenger Capmany

    January 14, 2008 at 7:39 pm

    Matthew..

    I’m also with same setup on two macs (Quad G5 and QuadMacpro) and Decklink HD extreme, tried both 6.6.1 and 6.6.2.

    Have you experienced that the issue only happens of the video display (Decklink) and the video on the canvas works fine? then when the problem becomes worse it’s happening on both displays?

  • Berenger Capmany

    January 14, 2008 at 7:51 pm

    Images are already at minimun frame size! 1920×1080!!!!

    Was the first thing that came to my mind… since problems with oversized images are a “legacy” problem in FCP… also be sure that images are RGB not CMYK.

    but also happens with movies with alpha channel created in AE.. the Lower Thirds are animated.

Page 1 of 3

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