Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums AJA Video Systems “Codec not found. You may be using a compression type without the corresponding hardware card.”

  • Jonathan Lawrence

    May 31, 2011 at 5:16 am

    THIS worked for me re: the same codec error issue THANKS!!!

    Changing my stills in PhotoShop from CYMK to RGB (and also remembering my old school learning of changing the dpi to from 300 to 72 then upping the image size ) did the trick —Ahhhhhhhhh THANKS

    Jonathan Lawrence

  • Fredy Schwerdtner

    June 26, 2011 at 3:51 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”

  • Martin Sautter

    August 23, 2011 at 9:27 am

    Hi everybody,

    I just encountered the same problem after applying twixtor to my timeline. The problem was solved by changing the sequence video processing settings from 10 bit to 8 bit. Maybe that helps to solve your problems with other issues.

    cheers martin

    http://www.martin-sautter.com

  • Jeremy Salig

    September 27, 2011 at 3:06 pm

    Changing from 10 bit to 8 bit worked like a charm for me. I got this message when trying to render simple ProRes sequence. Still not sure why it happened but this works around it nicely.

  • Alain Furcajg

    December 2, 2011 at 6:03 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!

  • Sai Kelly

    March 14, 2012 at 11:50 pm

    So there i was, still editing a 23:30 from 12:00 this afternoon, fully intending on continuing until the birds sing and i decide to hit RENDER to survey some recently clipped clips. BAM. “Codec not found. You may be using a compression type without the corresponding hardware card.” and then shortly following “fxscript error : unknown error”. How helpful.

    (Would it be too much to ask for a computer to say, “Error. Fix it with the following…”)

    Now before i melted down the mouse to use as a sharp projectile-able device to insert between my eyes, or reached for a trusty flat blade, i did a little error search and found a few suggestions. Also that this error comes up for a few different reasons. I realise this post is old but i found it and it was relevant to me in the distant future of 2012. So, as im sure all involved up until now have either solved the issue, died waiting for another more helpful answer or just moved on with their lives, this post is aimed at any future ‘me-type’ people who need this solution.

    ‘Bucky420’ on MAC-FORUMS spurned the brain juices on with his helpful but at first illusive comment, “It’s a framerate problem.” After shouting obscenities at the screen, i got to thinking; what was the last thing i did before this error started…? I imported a previously exported company sting into the project and, deciding to go for full quality instead, dropped it’s source Template into the timeline from the Master Templates folder in Effects…

    I found that this error was caused by placing 29.92fps Motion template into a timeline in FCP which was 25fps. Why it was 29.97fps are for reasons known only to itself, so i opened the template in Motion, copied the layers into a new project (set at 25fps) saved the new template with the name ‘Saiko Sting 25fps’ jumped back into FCP and then just dragged the new one over the old one in the timeline…Bingo. Rendering was re-enabled. All joy. No poo. My overnight editing session can resume.

    Good luck folks, Keep fighting the good fight.

    Saimurai

  • Howie Chin

    May 8, 2012 at 1:57 am

    thank u…an age old problem… *phew*

  • Richard Van harderwijk

    August 28, 2012 at 5:32 pm

    Age old problem indeed, but freaked me to dead today…
    Codec not found, with ProRes all over the place…

    FCP 7.0.3, ProRes HQ in a timeline and with the rotate 180 filter the timeline didn’t render anymore. I thought, well I don’t care, I just need to export the thing…. Grumbl, the same message. Exporting in HDV went well.

    My solution: In sequence settings->video processing I had put the options on ‘render in high-precision yuv’. Putting it back to ‘render in 8-bit yuv‘ did the thing 😀 Happy!!! Deadline tomorrow. Still strange, ProRes is 10 bit…

    Google was a big help, and mostly this tread (as always on the cow 😉 It seems that sometimes fiddeling the render settings gives this error (and the solution;-).

    Hope this helps other people.

  • Fred Duffer

    December 4, 2012 at 7:38 pm

    the easiest solution is to use the animation codec to re-compress any photo jpegs you may need to use…prores 422 doesn’t seem to like photo jpeg…also has something to do with quartermaster for all you smart people out there…(I am not smart, I just want things to work)

Page 3 of 3

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