Codec not found. You may be using a compression type…

[Paul Dickin]

[kyler boudreau] “This is crazy. Is there any FCP codec that will let me bring in weird sizes… “
Hi
Its a legacy QuickTime thing – codecs use macroblocks of like 16×16 or 4×4 pixels to do their data compression, so 851 0r 823 doesn’t ‘compute’.
Computer says No! (UK TV show joke…)

Roll on a QT built with resolution independence and vector analysis 😉

[Kyler Boudreau]

Now that’s the info that clears the fog! Thanks for that! So am I safer keeping them at both even dimensions? Like 854×644 as opposed to 853×644? Is there some type of calculation I can perform before recording these?

_______________________
kyler boudreau
http://www.theatereleven.com
ph.310.425.2231

[Jeremy Garchow]

[kyler boudreau] “So am I safer keeping them at both even dimensions? Like 854×644 as opposed to 853×644? Is there some type of calculation I can perform before recording these? “

Just use a video frame size and FCP will be happy. Why chance it?

[Kyler Boudreau]

I don’t have that luxury. I’m recording calls with multiple presenters and each of them shares their screen at different sizes.

_______________________
kyler boudreau
http://www.theatereleven.com
ph.310.425.2231

[Jeremy Garchow]

Then I would transcode it down to the closest denominator like 1280×720 and be done with it.

Your problems will virutally go away. FCP touts independent resolutions, but has always done weird things when working at non standard video sizes. Animation is a codec that is pretty good at whatever the raster, but your file sizes will be huge. I’d stick to the outlined method, or something similar to it.

Jeremy

[Jason Bach]

i had this problem too. Turns out the footage that I imported automatically set my sequence settings to render in YCbCR, not RGB. I went to Sequence settings -> Video Processing Tab, and selected “Always Render in RGB”. I was then able to render my transitions and effects.

[Fredy Schwerdtner]

I agree with Kevin up there and 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”

[Karen La]

YES! Thank you for the tip! Out of a 9:30 minute documentary I had only 1 CMWK still and was struggling for the past 5 hrs to render.

[Chris Hankins]

Tips like this are why I LOVE this forum. Had the same issue, checked here, and BANG. I did indeed have my file saved in CMYK format, that was the issue. Thanks guys! Saved me yet another headache while editing!

[Gavin Turnbull]

Hi All,

So, I have another issue that caused this ‘error’ while I was attempting to render a very short sequence of iPhone clips and stills.

I’d imported some iPhone footage that I’d converted to Pro Res LT. Only after I’d cut it I’d forgotten it was 29.97fps!!

I did check the stills were RGB and they were, so they weren’t the problem.

So re-transcoded the clips to Pro Res LT 25fps synced the clips up to the previous clips… forgetting that the timeline was still 29.97 fps…

So, after a few goes and eventually twigging my mistake I created a new time line in 25fps, copied-cut-pasted the clips from the 29.97fps into the 25fps timeline… solved! I rendered without issue.

As with other FCP7 complaints, it’s often down to not having the correct or mixed codecs in your project, preparation preparation preparation !

Hope that’s useful for someone.

Best,
Gavin