-
Oy Vey. Why me? Another sweet FCP bug, produced by JeremyG.
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.
Jeremy
-
21 Replies
-
Well, easy thing’s first. Uninstalled and reinstall Kona drivers, and the problem now went away.
-
Just kidding. The problem is now back. I am a little lost on this one.
Jeremy
-
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.
Coll
-
I will try. Do you have scaled and retimed footage?
Jeremy
-
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.
Jeremy
-
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!
Shane
Littlefrog PostGETTING ORGANIZED WITH FINAL CUT PRO DVD now for sale!
http://www.lfhd.net -
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.
Submitting feedback soon.
-
Alright, more testing and it is not limited to ProRes or HQ. 10 bit uncompressed also messes up. This is so weird.
-
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).
I can’t reproduce this myself…
(bored, nothing to do…)
Shane
Littlefrog PostGETTING ORGANIZED WITH FINAL CUT PRO DVD now for sale!
http://www.lfhd.net -
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?
Jeremy
Reply to this Discussion! Login or Sign Up