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.

  • Codec not found. You may be using a compression type without the corresponding hardware card.

    Posted by Biff Van cleve on July 16, 2009 at 4:25 pm

    I reviewed all of the threads and did not find an answer.

    I just updated FCP yesterday. I am working with ProRes 422 (HQ) with a frame size of 854×480. (We use this size to speed our graphic generation in FCP.) The files were converted from 720p to downsize the aspect ratio to 480p.

    The files playback beautifully, but will not accept any FX. The result is always “Codec not found. You may be using a compression type without the corresponding hardware card.” I also get the same result with standard ProRes 422.

    I am about to try it on a system that has not been upgraded, but wanted to get this post out.

    thanks

    Erg Into replied 13 years, 7 months ago 12 Members · 14 Replies
  • 14 Replies
  • Chris Poisson

    July 16, 2009 at 5:55 pm

    We had the exact same problem with some files out of AE this week. If you render to 854 it screws it up, but if you use 720×480 and stretch it with the distort tab it works fine.

    Have a wonderful day.

  • Jeremy Garchow

    July 16, 2009 at 6:21 pm

    In FCP and AE, you should work in a D1 or DV Widescreen composition. Pretty much any standard NTSC monitor will need 720×486 (blanking gets added to 480 material), and then you can use the montior to stretech it back out to 16×9.

    You are getting errors as it’s a non standard frame size for video codecs.

  • Jason Porthouse

    July 16, 2009 at 6:40 pm

    As a linked aside, I had this very message the other day trying to render a ProRes (non-HQ) sequence, as set from the easy setup (sequence presets). I got the message on render and export. Only way I could cure it was to turn rendering to 8-bit in the sequence settings. What gives??

    Jason

    _________________________________

    Before you criticise a man, walk a mile in his shoes.
    Then when you do criticise him, you’ll be a mile away. And have his shoes.

    *the artist formally known as Jaymags*

  • Jeremy Garchow

    July 16, 2009 at 7:03 pm

    Hmm. What were you rendering?

  • Jason Porthouse

    July 16, 2009 at 10:37 pm

    OK, it was a sequence cut in DV, from DVCam PAL source. I copied and pasted the sequence into a new sequence set up as ProRes using the preset, modifying it to playback using my Blackmagic Multibridge Pro. Tried to render (a mix of PinP over graphics produced to PAL size) and supers & rolling caps using Boris. A few light CCs and crops. Nothing heavy. Got the message, scratched head, switched rendering to 8-bit et voila, it worked fine. This was for render and export.

    Odd, no?

    Jason

    _________________________________

    Before you criticise a man, walk a mile in his shoes.
    Then when you do criticise him, you’ll be a mile away. And have his shoes.

    *the artist formally known as Jaymags*

  • Bob Fiori

    July 16, 2009 at 10:55 pm

    Same thing happened to me today. Have bin FC convert for 3 years now and this is the first time I have seen this. Turns out my problem was that a few stills I was trying to use on an Hd timeline were too large vertical axis. I resized and everything was good. Don’t know if this helps, but just a heads up.

    Bob Fiori
    Croma-Video Inc,
    Collegeville, PA 19426

  • Jeremy Garchow

    July 17, 2009 at 3:23 pm

    [Jason Porthouse] ” Got the message, scratched head, switched rendering to 8-bit et voila, it worked fine. This was for render and export. “

    Very odd. If you just cpoy and past a PAL clip into a ProRes timeline, does it work (basically, bypass all the effects).

    Jeremy

  • Patrick Kondelis

    March 25, 2010 at 3:54 pm

    I had the same problem and switching to 8 bit rendering fixed it. I have no idea why!

  • Noam Osband

    May 16, 2010 at 7:32 am

    Bob,

    I’m getting this problem now on a film with a few large stills. I ran rendering just on that section and I got the same error, so I’m wondering if I have your problem. I dont exactly understand what you did for the Y-axis. Can you explain it again?

    thanks,
    noam

  • Maureen Freichmann

    November 24, 2010 at 3:01 pm

    Hello Patrick,
    I just started working with FCP, and I got the same error. Could you please explain how to switch to 8-bit render?
    Thanks!

Page 1 of 2

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