Oy Vey. Why me? Another sweet FCP bug, produced by JeremyG.
by JeremyG
on
Dec 10, 2007 at 6:12:45 pm
Alight. Using the latest 'greatest' FCP 6.0.2, QT 7.3, OSX.4.11. Sound familiar?
Using ProRes HQ material (in both 720p23.98 and 1080i29.97).
If you take a coupla three ProRes clips, scale them down, composite them into a three up split screen, change their speed (to say 50%), then render the whole timeline at once (render-all), everything renders wrong. Some clips become full screen, some clips become still frames, some clips render just fine. Awesome...right? Okay, maybe not.
The workaround? Render in pieces. I render for a minute, then hit cancel, render for a minute then hit cancel, render for a minute then hit cancel. Then and only then will the renders show up correctly. Why? I have no effing clue. Also, changing the sequence to 10bit uncompressed seems to fix it as well.
This only seems to happen on material with speed changes in a ProResHQ timeline, if there's no speed changes, everything renders properly.
Can anyone reproduce this or has my system gone haywire? I have not tried other codecs, but I can get it to constantly repeat. Maybe it's a Quicktime thing, maybe a ProRes thing, maybe it's a Kona thing. Maybe I am just imagining this whole thing and I need more coffee to bring me back to reality. What do you all think?
More tests coming and I will update as I know more.
Re: Oy Vey. Why me? Another sweet FCP bug? by collofthewild on Dec 10, 2007 at 7:27:43 pm
Have you tried this in a non HQ sequence? to see if it's really the HQ codec? I'd be interested to know, we work in Pro Res 1080i 29.97 (non HQ) and have never seen this problem.
Re: Oy Vey. Why me? Another sweet FCP bug? by Shane Ross on Dec 10, 2007 at 7:39:54 pm
Speed changes...the BANE of Apple and FCP. There are many bugs when it comes to speed changes. They all stem from the fact that Media Management and speed changes STINK!
Re: Oy Vey. Why me? Another sweet FCP bug? by JeremyG on Dec 10, 2007 at 7:46:59 pm
Oh yeah, I understand that, but I have never seen them render this wrong before. I have seen them not media manage properly, but this rendering thing is weird.
i wonder if it has to be with VBR nature of ProRes? I don't know.
Re: Oy Vey. Why me? Another sweet FCP bug? by JeremyG on Dec 10, 2007 at 7:39:01 pm
It happens with ProRes sequence as well as HQ. I have been able to repeat this across three machines now. It's not a KOna thing, it's an FCP thing at this point.
Re: Oy Vey. Why me? Another sweet FCP bug? by Shane Ross on Dec 10, 2007 at 9:08:12 pm
Try this...
Can you use the render manger to clear the renders and try rendering again? And try manually deleting the constant frames folder (that mysterious thing inside the render folder).
Re: Oy Vey. Why me? Another sweet FCP bug? by JeremyG on Dec 10, 2007 at 9:12:16 pm
Definitely deleted render files before (even rendered to a different media drive altogether). I will try constant frames. Since it happens across three machines, I am beginning to lose faith that it's my main desktop machine that's busted. It seems to be more a systemic FCP issue.
How long is your timeline and is your footage ProRes captured?
Re: Oy Vey. Why me? Another sweet FCP bug? by JeremyG on Dec 10, 2007 at 9:54:09 pm
I thought of that too thanks to your geneousity, but no, there aren't any plug in combos that are shared across all machines. Two of the machines are bare bones FCP, no plug ins installed.
In your test, you scaled and retimed the clips, then composited them, correct?
The timeline I have here is about a minute and consists of about 30 or so clips. I have been able to reproduce similar artifacts on other timelines with other media in far shorter of a run time.
Re: Oy Vey. Why me? Another sweet FCP bug? by Shane Ross on Dec 10, 2007 at 10:13:35 pm
I did just what you listed. I have 720p 23.98 clips that I converted to Pro Res (well, one that I converted) and I have HDV 1080i29.97 footage that I converted. Then mixed and resized and did the whole "24" thing...no problem with the render.
Hmmm...How about SINGLE plugins? You say two are bare bones? Curiouser and curiouser...
Re: Oy Vey. Why me? Another sweet FCP bug, produced by JeremyG. by Rafael Amador on Dec 11, 2007 at 10:15:54 am
Hi Jeremy,
I have the same conf than you (MaOX,QT,FC), and I'm having similar problems.
I'm just trying to put some DV clips in an "Upper-first" sequence at 50% speed.
The image jumps like crazy.
If I uncheck "Frame blending" is OK but with "Frame blending" on, the image jump like crazy.
The only way it works for me is nesting the clip and changing the speed after.
rafael
Re: Oy Vey. Why me? Another sweet FCP bug, produced by JeremyG. by Jeremy Garchow on Dec 11, 2007 at 9:41:24 pm
Nesting, Hmm. Actually, the trick of putting on a filter that doesn't do anything (desaturate with a value of 0 is what I have been using) seems to force FCP to render correctly. Thanks for that reminder, Mr Weaver. That has saved me in the past when FCP couldn't rendered scaled 10bit HD material without artifacting.
