Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Color shift; HDV export to QT from FCP (5)

  • Color shift; HDV export to QT from FCP (5)

    Posted by David Mcgiffert on July 3, 2007 at 10:03 am

    When I export to either a self-contained or a reference QT movie,
    my HDV footage is extremely washed out in the resulting QuickTime.

    Any suggestions?

    Exporting HDV footage from a Canon XH-A1 in FCP 5
    with a single chip G-5. (and yes it is a long render time…lol)

    Thank you.

    David

    David Mcgiffert replied 18 years, 10 months ago 2 Members · 2 Replies
  • 2 Replies
  • Chris Poisson

    July 3, 2007 at 11:06 am

    Hi David,

    I have the same camera, and a G5 dual 2.0. My rendered movies look great, you can see a couple at Revostock, or here: https://www.fisheyeedit.com/newstuff.html

    What is your workflow? What kind of movie are you rendering to? What is your final delivery to be?

    Most of my work is for SD delivery, or HD for the Web stuff as referenced above.

    This is what I’m doing:

    Capture native HDV (shot 30F BTW) work in ProRes timeline, render, and either scale or nest for SD, and for HD movies I render to either photo jpeg (for stock) ProRes or 8bit.

    I have been having great success with the ProRes timelines, color correction, effects text with alphas, everything works great. Never caused a crash, sometimes I’ll get dropped frames, but usually an audio mixdown fixes that.

    Perhaps your washed out look is resulting from a setup issue somewhere along the way. Check all your settings, including your video card if you have one.

  • David Mcgiffert

    July 4, 2007 at 7:05 am

    Hi Chris,

    Nice reply – informative too.
    I have been in the HDV timeline when I export to QuickTime, and this may be the problem. I do not have a ProRes timeline available yet, I have
    FCS 2 but have not installed it yet…waiting for the first line of pro’s to shake the bugs out before I dive in, for obvious reasons, my knowledge is not deep enough to be able to understand fully when things may not turn out as expected.

    Thanks for the workflow tips, I will try them.

    All the best,

    David

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