Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Green frames after Cinema Tools reverse telecine with ProResHQ

  • Green frames after Cinema Tools reverse telecine with ProResHQ

    Posted by Ted Griffis on June 27, 2008 at 6:09 pm

    Hello all,

    I recently up-converted some film archives material to 1080i 29.97 ProResHQ from Digibeta through an AJA ioHD. When I went into Cinema Tools to do a reverse telecine some strange things happen.

    I find the A frame properly on the 60i file and commence. The result is a Green frame every 4th frame of the new 23.98 clip. I had never seen this before, so I converted the original clip to Uncompressed 8bit to see if it was a ProRes issue. When I did reverse telecine on that clip it worked just fine, completely clean and perfect 23.98 file. Still curious, I exported the UN8 clip I made back to ProRes and ProResHQ, and both of those worked fine.

    So it seems that only the QT ProResHQ file generated from the ioHD creates a problem in cinema tools.
    Has anyone else encountered this green frame issue in cinema tools with ProResHQ or any other format?
    Any ideas, suggestions or work-arounds?

    Thanks so much,
    Ted

    Ted Griffis
    GriffisART
    https://www.griffisart.com

    Ted Griffis replied 17 years, 10 months ago 5 Members · 10 Replies
  • 10 Replies
  • Jeremy Garchow

    June 27, 2008 at 6:24 pm

    Have you tried the Rev telecine feature in Compressor3?

  • Ted Griffis

    June 27, 2008 at 6:46 pm

    Hi Jeremy,

    Yes, I have tried Compressor and though it does not introduce green frames its results are lack-luster. Cinema Tools is much cleaner in removing the pulldown, albeit when it doesn’t add green frames.

    After running through compressor with the same “in” point in the clip (the “A” frame) the resulting 23.98 file has visible interlaced lines whereas the ones from a “successful” trip through Cinema tools do not.

    If you have any suggestions on making compressor work correctly for this workflow, I’m all ears as compressor might be a faster engine anyway with an 8 core, just doesn’t seem to have the same flexibility in the settings to achieve the right result.

    Thanks for your help,
    Ted

    Ted Griffis
    GriffisART
    https://www.griffisart.com

  • Jeremy Garchow

    June 27, 2008 at 7:03 pm

    THere is a reverse telecine feature in Compressor and you don’t have to choose an A frame. As long as you don’t have any cadence breaks, you should be fine.

    You can find it in the frame controls tab under deinterlace. Every time I have used it, it’s been spot on and you can do everything in a batch.

  • Ted Griffis

    June 27, 2008 at 7:15 pm

    Yup, that the setting I’ve been trying. So does compressor analyze and find the right frames on its own?I’ll keep doing some more testing with compressor but still a bit confused as to why Cinema Tools would produce Green frames. Hmmm.

    Oh by the way, here’s a more detailed config:
    OSX 10.5.2 FCP Studio 2, Compressor 3.0.3, QT 7.4.5, Cinema Tools 4.0.1

    Thanks,
    Ted

    Ted Griffis
    GriffisART
    https://www.griffisart.com

  • Jeremy Garchow

    June 27, 2008 at 7:23 pm

    [Ted Griffis] “So does compressor analyze and find the right frames on its own?”

    Yes. No A frame searching necessary.

    [Ted Griffis] “I’ll keep doing some more testing with compressor but still a bit confused as to why Cinema Tools would produce Green frames. Hmmm. “

    Hmmm is right.

  • Jason Mann

    June 27, 2008 at 9:29 pm

    I get bright green artifacts (usually big rectangles on one side of the frame) when I have embedded Motion clips in the timeline.

    For example – if I send a clip to Motion to stabilize it, then render in FCP (in a ProResHQ, 1080p 23.98 timeline) I get green stuff. Every time. So I have to export a QT file from Motion and import that into FCP. It’s a pain.

    Details:
    10.5.3, FCS 2, 2×3.2Ghz Quad-core MacPro, Kona 3


    Jason Mann
    Compass Light, Inc.

  • Jimmy Spangler

    June 27, 2008 at 11:25 pm

    I have had issues with Motion Projects rendering as solid green clips in my timeline. This has happened with ProRes 422. I have not tested this with other Codecs.

    It was driving me crazy though trying to fix it. Was never able to resolve it.

  • Gary Adcock

    June 27, 2008 at 11:28 pm

    [Ted Griffis] “So it seems that only the QT ProResHQ file generated from the ioHD creates a problem in cinema tools. Has anyone else encountered this green frame issue in cinema tools with ProResHQ or any other format? “

    Yeah, and my testing indicated that it was a ProRes issue, I did the same thing you did and I was unable to remove the pulldown from any file I tried in the ProResHQ codec. I have had differing results in the SQ versions. Live captures seem to be OK for Pulldown removal, but software conversions show the same green results.

    still testing however, One file I used was from a sony EX1 and the cadence was not 3:2 but 2:2:2:4, and CT does not remove that cadence very well at all.

    gary adcock
    Studio37
    HD & Film Consultation
    Post and Production Workflows
    Inside look at the IoHD

  • Gary Adcock

    June 27, 2008 at 11:31 pm

    [Ted Griffis] “Oh by the way, here’s a more detailed config:
    OSX 10.5.2 FCP Studio 2, Compressor 3.0.3, QT 7.4.5, Cinema Tools 4.0.1 “

    What Camera is the footage from and Exactly how did you handle it.

    Start at the source – like I said in my post -one of my issues was camera specific.

    gary adcock
    Studio37
    HD & Film Consultation
    Post and Production Workflows
    Inside look at the IoHD

  • Ted Griffis

    June 27, 2008 at 11:54 pm

    Thanks for the input Gary.

    [gary adcock] “What Camera is the footage from and Exactly how did you handle it. “

    Well actually it was not from a Camera. The footage was a Digibeta telecine of a film from the Nation Archives. I captured it via SDI from a Sony J-30 into the ioHD as 1080 29.97 (Zoom Wide).

    The odd thing is that the only the original ProResHQ file(s) cause the problem (anything captured directly from ioHD), though an exported section of that file(s) still in ProResHQ works flawlessly when run through CT.

    Does it sound like time to move this to ioHD forum?

    Thanks
    Ted

    Ted Griffis
    GriffisART
    https://www.griffisart.com

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