Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy codecs & colorspace upon exporting

  • codecs & colorspace upon exporting

    Posted by Byron Caplan on October 11, 2013 at 3:06 pm

    to any and all,

    i am using FCP 6.0.6 and editing video shot with my canon xf300 at 50Mbps with a 4:2:2 colorspace. during log and transfer i used the “native” compressor setting which (i’m told) re-wraps the video, in this case to xdcam hd422 1080p24 cbr (i shot the video at 24p) without loss. so far so good.

    so i edit my video and then go to export it as a quicktime movie with the same codec (xdcam hd422 1080p24 cbr). after it’s been exported, it looks a little washed out, so i right click the file to get information… and lo and behold… it says that the video has a 1:1:1 colorspace. i exported it again to make sure all my settings were the same… but with the same result.

    so my question to anybody is… what happened to my 4:2:2 colorspace? i thought exporting the video in it’s native form would retain the quality, but obviously it hasn’t. so how does one export to get the same quality?

    inquiring minds want to know…

    thanx in advance,
    -byron

    Byron Caplan replied 12 years, 11 months ago 1 Member · 1 Reply
  • 1 Reply
  • Byron Caplan

    October 11, 2013 at 3:59 pm

    dear dave,

    thank you for your swift and sensible suggestion. please correct me if i’m wrong, but it sounds like you are saying that if i want to retain the original quality of the video, i have to bump it up to ProRes 422 at 3X the file size.

    forgive my questioning and hopefully someone can explain… but i just can’t wrap my head around why a video can’t export at the same quality as it was imported in (from 4:2:2 down to 1:1:1 is a huge loss)… unless that is just the way that FCP handles the .mxf format. the degradation of colorspace is unacceptable, but the incredible jump in file size when converting to ProRes 422 is problematic for reasons of storage space.

    new question: would this happen on premiere pro or avid (which i hear accepts .mxf format)?

    thanx again,
    -byron

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