Currently Being ModeratedOct 27, 2011 7:12 AM (in response to EpicSummerMovie)
Well, first troubleshooting step is always
If that doesn't work
Try this. Make your sequence active, go to sequence settings (command-zero) change the compressor to something different and hit OK. Then repeat and change it back to ProRes.
If that doesn't work, try copying the contents of the sequence to a new sequence with the same settings. Sometimes a sequence can get corrupted.
I also seem to remember other people having this problem so you might do a search here for "codec not found."
Currently Being ModeratedNov 3, 2011 6:10 PM (in response to Michael Grenadier)
I went to the sequence settings and changed my compressor. I tried changing it back to ProRes 422, and that didn't work, but if I left it in a different compression, I could edit fine. Thanks!
Currently Being ModeratedNov 5, 2011 10:59 PM (in response to EpicSummerMovie)
Thank you for asking the question... and giving the solutions. It happened to me today for the first time "codec not found... "
This was after getting rid of my FCP preferences files due to another error message..
For me, copying everything into a new sequence solved it.
Thanks again! Ben
I'm on a 3 year old mac pro running Leopard 10.5.8 and Final Cut Pro 6.0.6
and it's the first time I have encountered this.
When setting up the easy setup after tossing the preferences.. I believe i chose the wrong settings then...
Model Name: Mac Pro
Model Identifier: MacPro3,1
Processor Name: Quad-Core Intel Xeon
Processor Speed: 3.2 GHz
Number Of Processors: 2
Total Number Of Cores: 8
L2 Cache (per processor): 12 MB
Memory: 6 GB
Currently Being ModeratedNov 6, 2011 9:19 AM (in response to EpicSummerMovie)
Well it looks like we've got the same OS running, which helps troubleshoot. Are you running fcp7.03?
Try creating a new user (system preferences: accounts) and log in as that user and load the same fcp project. Same problem?
Take a look in your startup drive: library: quicktime and make sure you have the following files:
Do you have any 3rd party video things installed like Perian?
Currently Being ModeratedNov 8, 2011 3:26 PM (in response to Michael Grenadier)
I do have the AppleProResCodec.component, but not the AppleProRes422.component, what do I do? I am also having trouble with audio sync in one clip, if I go directly to the file it plays fine, but when I play it in Final Cut, the video and audio are way off. Could this be a problem caused by the lack of the AppleProRes422.component?
Currently Being ModeratedNov 11, 2011 10:22 AM (in response to EpicSummerMovie)
The same thing happened to me a few years back just after I had upgraded my OS and Quicktime. All of my ProRes 422 codecs had "disappeared" from the "Library/QT" folder. I found the following solution:
Insert the original FCP install disk
Go to the "Extras" folder on the disk
Install "QmasterNode" (it evidently contains all of the codecs).
After doing that I checked the Library/QT Folder again and found that all of the ProRes 422 codecs were now there. I then reopened my original FCP video project and guess what...problem solved--no more message!!
Hope this helps.
I have much the same problem. The message has popped up on random projects and won't let me render. I trashed the preferences, copied the clips to new sequences and tried resetting the compressor. I checked my Library/Quicktime folder and am indeed missing the AppleProRes422.component, so I tried reinstalling QmasterNode like CaptainS just said. But somehow I still don't have the AppleProRes422.component. Could someone send it to me, or give me another suggesetion?
Currently Being ModeratedNov 17, 2011 7:39 AM (in response to Michael Grenadier)
Will do, because I still need the component, but I thought I'd post that I found something that worked.
I found in another thread a suggestion to check Sequence Settings and switch "Render 10 bit material" to "Render in 8-bit YUV". I did, and it worked.
Does anyone know why that works? I'm not super technical, so I don't know the advantages of having it in 8-bit rather than 10-bit. How did it get switched before and stop working?