-
using movs to spped up a render
Okay so there’s a tiny mistake with a dissolve in my .mov export that took 35 minutes to render. In order to avoid rendering the entire thing all over again, I drop the finished movie in the comp,, cut out a hole where the mistake was and fix it in the layers beneath.
Usually this cuts my render time into nothing. I figure it’s cos AE is just rendering an already made movie with a tiny bit of a composition. But this time my render actually took 10 minutes longer, 45 minutes total. WTF!
The only explanation I could come up with is that it took longer cos AE has to render the mov AND the comps beneath it…but that doesn’t make sense I’ve done this trick in so many other projects that would prove otherwise. Maybe render times slow down the longer the program is on? or CS5 is still kinda batty? IDK but it’s driving me insane, any explanations appreciated!
-
4 Replies
-
did you trim the underlying comps to be only as long as the hole?
Kevin Camp
Senior Designer
KCPQ, KMYQ & KRCW -
No i didn’t trim the beneath layers,, I was under the impression AE didn’t process layers not shown on the screen,, was that the issue?
-
Wow, I just facepalmed myself so hard that I think I got a concussion. That is SO much simpler and I totally could’ve done it from the start! In fact, b and n are some of my favorite hot keys (right up there with u, i & o)
Dunno why I haven’t been doing it like that, I guess I subconsciously just wanted to do the whole thing in one render. But this works much better cos now I won’t have to risk AE processing the entirety of the layers beneath my movie.
PS: It’s been just about a year since you answered my first AE question (and every silly question I’ve had since) Thanks for all your help Dave! <3 <3 <3!
-
yep, that was probably the problem. ae will still process stuff even if it is not visible in the frame.
Kevin Camp
Senior Designer
KCPQ, KMYQ & KRCW
Reply to this Discussion! Login or Sign Up