Stuttery Renders

[Joey Burnham]

Hi Dave,
Thanks for the speedy response. I will give prores a shot. I’m not trying to toot 10 Bit 4:2:2’s horn by any means, but we’ve been using it for about 3 years now with no major hiccups. Actually this is the first.
Wish me luck,
Joey

[Joey Burnham]

No dice. Actually prores is worse. And I’ve just now isolated it to FCP. Plays fine in QT.

Bye, bye AE forum!
Thanks

[Joey Burnham]

If you shot 24p, then interpreted or rendered improperly, it would look pretty grim.

I shot nothing. The footage is spot on. We’ve done numerous spots for this same feature and I really don’t think it’s the footage.

FCP is just not liking the footage from AE. Footage before it goes through AE is fine, and after is fine too, just not to FCP.

Stumped.

[Troy Murison]

Hi Joey,

This sounds very similar to a problem I had a few months back. My AE renders looked ‘stuttery’ in FCP but fine in QT. There were repeated frames in the render file when stepped through or played back in FCP, but not in QT player. They were also repeat frames in AE if we imported them back in. If we then re-rendered to new QTs using those imported files, THEN those renders were ALSO stuttery in QT or any other app, so the problem was passed on (that’s how we actually discovered it- we were pre-rendering).

The only thing I found that solved the problem was to clean the database and cache and reboot the computer before rendering from AE. And hold my breath and do a dance on one foot while thinking positive thoughts….. 🙂 This seemed to solve the problem for us. This was happening across multiple machines too. I have not seen it since so it may not appear to happen on every project (?). I was at a loss at the time but that reboot thing worked for us and so haven’t thought too much about it since. Our QT has been updated a couple of times since then too. I seem to recall being on QT 7.3.? at the time as well as 8.0.1 in AE, but I’m not positive. I just figured it had been solved with 7.4.1 or AE 8.0.2 since I hadn’t seen it since. I can’t help but think it is or was a QT implementation thing within individual apps that’s reading something in error in those rendered QTs, but that’s my own un-educated guess.

Best of luck,

-Troy Murison
Seattle, WA

[Joey Burnham]

Your “uneducated” guess is the same as mine. I was able to pull the files in question into another edit bay and presto! Fine. But I still have the bad bay to deal with.

What exactly to you mean by “clean the database and cache”? I know about ctrl+clear for the cache, but what database?

Thanks!
Joey

[Troy Murison]

Sorry, been out of touch here…

I mean in the AE prefs: Memory & Cache, there’s a button there to clear the database and cache. So cntrl + clear empties the cache? I learn something new every day…

-t.

[Joey Burnham]

Thanks for getting back to me. We’ve tried almost everything, but no real fix yet. And the problem isn’t consistent, so I’m thinking it’s a FCP/Quicktime thing.
A quick fix which works though is just to apply the shift fields filter in FCP. Doesn’t really address the problem, but it works as a solution for now.
Best,
Joey