-
Set, Render, and Leave
I often have a large render batch that I leave to render overnight. Instead of coming in in the morning to a nice happily complete queue, there’s an error message that my “output module will overwrite an existing file; ok? or cancel”, or something to that effect.
Well darnit of course it’s ok.Does anyone have a script to answer yes to these annoying questions that will stop your render queue dead?
Andrea Stewart
Producer/Editor/Director – Owner
Germane Creative LLC -
3 Replies
-
You can also just tell AE that it’s alright to overwrite the files. Unless something was different before version 7, AE performs this check before it starts any rendering. So you might have to hit return a few times after you submit the queue, but then there should be no further interruptions (barring render errors!)
Darby Edelen
Designer
Left Coast Digital
Santa Cruz, CA -
Dave, great suggestions, of course. I do in fact set up a separate folder to render to and then resort the renders to other folders once they’re all completed. But I was/am still getting that message. And unfortunately, Darby, it doesn’t ask me that question until it hits that particular rnder request in the queue. So if it comes up in the middle of the night, I’m not there to answer yes to it.
What I’ve learned is that although I’m using Nucleo to do the render, something is happening at some point in the operation that is making Nucleo fail which then kicks it back out to the After effects renderer half way through a render. As a result, After Effects is seeing two files with the same name, since what Nucleo does is create two instances of your project and render them simultaneously. It has already created a file with that name, then AE says, “hey this file already exists, do you want me to render over it anyway?”
Nucleo has a Support Tool in the Nucleo pull down menu. I’ve run that but the problem is still happening. I’m in contact with support at Nucleo about this. The support tool can put together of “package” of vital information. But gridiron (Nucleo) can only tell me where it is failing, not what the problem is. Though they did suggest that there may be a conflict with some of the Knoll Light Factory plugin version. But I’ve had this sequence render before with Nucleo successfully, using the same plugins in the sequence. So I don’t see why it should be having a problem now.
Anyway I tell you all this in case someone searches for this kind of problem in the future and it is in anyway helpful. I will update the post again if I get the answer and it is a “gotcha” that can be educational to someone else.
Andrea Stewart
Producer/Editor/Director – Owner
Germane Creative LLC -
[Andrea Stewart] “And unfortunately, Darby, it doesn’t ask me that question until it hits that particular rnder request in the queue. So if it comes up in the middle of the night, I’m not there to answer yes to it.”
What version of AE are you using? Every version I’ve used (6.5-CS3) pre-flights the items in the render queue to check for the potential of files being overwritten.
[Andrea Stewart] “What I’ve learned is that although I’m using Nucleo to do the render”
After reading further down in your post, my suggestion would be to disable Nucleo for overnight renders. I’ve experienced more weird issues with Nucleo renders than I care to recall. It doesn’t always cause problems, but when it does it sets me back more than it speeds things up. The only really nice benefit I see in Nucleo when compared to CS3 is the background renderer, and if you’re rendering overnight you don’t need that anyway.
Darby Edelen
Designer
Left Coast Digital
Santa Cruz, CA
Reply to this Discussion! Login or Sign Up