Weird renders in FCP

[Matthew Nelson]

For me the issue is all or nothing. I have not seen it manifest in the video display (Decklink) only.

Out of curiosity do you have any issues with kernel panics or FCP crashed while rendering?

[Berenger Capmany]

nope.. (lucky me!) only a couple of “out of memory” errors..

[Stacy Formby]

6.02 plus Pro Res plus embedded Motion files = horrible render problems for me, no one is alone in this. You’re lucky you are at least getting renders. FCP bombs in the middle of all renders. If I leave it to auto-render, when I come back it has bombed. I have to sit and babysit a render, cancelling after it has completed 2 or 3 percent. If I lose concentration and wait until status bar is at 20% or so, hitting cancel will bomb Final Cut Pro (losing the renders) I will add that I have an Intensity Pro as well. So I don’t know where to point the finger, but that’s my setup. (Mac Pro, Tiger, 4GB RAM). Any ideas appreciated, I trash Constant Frames and reset Prefs several times a day at this point…

[Berenger Capmany]

Jesus! this remenbers me the old days of Premiere 3 on Macos 8! your case it’s worse! I’m Sorry.

What I realize here it is that it’s not related to the duration of the project. I tougth that being long projects (1 hour) was the key to blossom the problem…but it’s not.

Have you tried to delete all renders (including render queue) under Render Manager.. is not solving the project but it’s a littl ebi better..

Tomorrow I will try the plug-in trick to force a software render…

Cheers! (and sorry for my english!)

[Jim Dodson]

Yish! Every problem described above we’re having too!!!

We have a Kona 3 and an 8 core and it’s a ProRes sequence.

The sequence plays fine, BUT when I try to export out a quicktime FCP either (a) bombs or (b) renders crazy (like previously describes — especially shots with Basic motion (crop – reposition etc.) and picture-in-picture’s — big problems with those — tried trashing preferences — that stopped the bombing (for a second) but the export were still wacky bad.

Now it’s back to bombing on “Export Quicktime Move”…

Jim Dodson

8 Core Intel — Mac – OSX

[Jim Dodson]

** A FIX / WORKAROUND** !!!

Sean Findley — our resident genius tried exporting the sequence out with the Codec set to “8 Bit Uncompressed” — And all anomalies went away!!!!!

Then using QuickTime we exported the 8 Bit HiDef file (which was 24 gig’s for 5 minutes) to ProRes

MAKE SURE: When you make the 8 bit file that you use “Custom Settings” (under export QuickTime Movie) as the 1st time I exported using “8 Bit Uncompressed” it exported to Standard Def and 29.97 eventhough we are 23.98 and 1920×1080 — so make sure you export out at the proper settings for your file!!

Jim Dodson

8 Core Intel — Mac – OSX

[Jeremy Garchow]

Yeah, I found the same thing in my orig thread. If you switch codecs it’s okay, it’s only Prores and hq that’s affected.

[Jordi J recort]

Nice,

Yesterday I left Final Cut rendering the sequence in DVCPROHD and also worked.
I’ts a pain because all the ratios are mess up (because of the 1440×1080 size) but has been good for the test because all the weird renders went away.

So this points to ProRes+Hardware render engine as the origin of the problem

I will try uncompressed but I need to free up 300 GB!

If the Computers are free tonigth (this issue is delaying us the delivery of the Programs to the Broadcaster!!) we will try the trick of forcing the software render engine with a Plug-in adjusted to zero value!

Jordi J. Recort

Composer & Editor

[Jordi J recort]

So, in ProRes – not HQ, also works fine?

Jordi J. Recort

Composer & Editor

[Jeremy Garchow]

Everything BUT ProRes and ProResHQ.