Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Codec not found. You may be using a compression type without the corresponding hardware card.

  • Fredy Schwerdtner

    June 26, 2011 at 3:53 pm

    Looking for the same kind of problem when trying to render a prores sequence, I could solve the problem changing the compressor render settings for the sequence from “same as sequence codec” to “apple intermediate codec”. Doing that I could render and export it.

    iMac 2.7 GHz Intel 4 Core i5
    16 GB memory

    MacBook Pro 17″
    2.5 GHz Intel Core 2 Duo
    6GB 667 MHz DDR2 SDRAM

    OWC RAID 5 with 3TB
    (2) External HD LaCieMac (400/800 FW and USB)with 500GB -(2) USB External HD Western Digital (in cases) with 750GB
    OS X 10.6.5
    Final Cut Studio “3”

  • Alain Furcajg

    December 2, 2011 at 6:04 am

    Fixed it! Changed render settings of the sequence to HDV as opposed to Prores 422. Other codecs probably work but not Prores 422 apparently.

    Had this error message: “Codec not found. You may be using a compression type without the corresponding hardware card.” when was trying to export my sequence – or even just render. Been editing a project with multiple codecs and stills and thought it was because I was using jpegs – as opposed as png or tiff – in all different frame size. I isolated it and it was actually some vertically shot footage – on iPhone or Flip but converted to Prores 422 – that was creating the issue. SO i changed the settings of my sequence to render in HDV as opposed to Prores. Somehow the supposedly flawless Prores 422 codec is pretty fussy about vertically shot footage – and some jpegs in different frame sizes too I’ve read – and wouldn’t render. So rendered and exported to h264 just fine!

  • João Toscano

    June 21, 2012 at 4:44 pm

    I re opened the FCP and it allowed me to render…

  • Erg Into

    October 15, 2012 at 6:33 pm

    I had this problem, and I discovered that it was due to having CMYK graphics in my sequence. As soon as I converted them to RGB, everything worked perfectly.

    Hope this helps!

Page 2 of 2

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