i seem to have some issues with an AE 2014 CC file.
Somehow I can submit the job etc, but there’s no output generated.
The in/output is local and therefor I set it to use only 1 machine.
It tells me it’s rendering, but there’s nothing written to disk… and the renders are instantly done.
When I merge that same scene into a new fresh AE project… it all works fine with the same (but imported) render queue.
any idea how that could happen?
Besides that I was wondering if it’s possible to lock the Automatic Draft generation to the same machine limit that has been give to the AE submission itself.
As it’s a local job my other slaves are useless when using for the draft auto submit
Could you provide log reports for the old and new job so we could compare for differences here?
What exact version of Deadline are you using here?
re: Draft job on same machine
There are a number of settings within the Draft Event Plugin to control which pool, group, limit are applied to these types of job. Would that work for you? docs.thinkboxsoftware.com/produc … html#setup
@ draft. I looked at these options, but the option I am actually missing is something like " limit submitted draft to machine limit of parent job"
As the limit can be different depending on which machine I work on (work on 2 workstation).
For me it was actually strange to notice that the machine limit set in the AE submit dialogue wasn’t applied to the draft setting set in that same dialogue.
For me it would make sense to have a checkbox in the AE submit Draft section that says “apply machine limit from job submission”.
In this case i need the limit to stick to one machine, but normally I only render AE files on half my farm as it quickly reaches the limit of my NAS speeds if I use the full farm which actually slows down the render. So also in that case a limit on the draft creation is preferred.
ok, thanks for the logs. So, the only difference is we are not providing a startFrame, endFrame or compName to the “bad” AE job. By default, (I just re-read the AE docs to make sure nothing has changed), then aerender.exe should render ALL the render queue for that project for all frames, if none of these args are provided. So…can you try executing the same AE command in a command prompt window:
"C:\software\Adobe\Adobe After Effects CC 2014\Support Files\aerender.exe" -project "D:\Projects\Celebrity_Cruises\AE\All_in_One_RNDR's_v05.aep" -close DO_NOT_SAVE_CHANGES
I’d like to know if it does anything other than print the following and then exit this time around for you?
re: Draft job
Currently, we don’t respect white/blacklisting, limits or MachineLimits (all as designed) as it was felt if Draft is used for either image sequence generation or movie generation, then generally, any previous “job” related restrictions here in it’s settings wouldn’t be appropriate. I understand your situation. Now that Draft/QuickDraft UI code is unified in the next major version of Deadline, I think we can make improvements here. I will log it for dev team.
I think there’s just something that went haywire in that AE comp for some reason.
I’m not sure, but in the last days AE did crash at some point… I generally make it my policy to not continue with recovery-save-files… but perhaps there was something that was transferred in this one … no clue
Last Draft related question:
I’ve been looking through the repository (and help) but can’t seem to find a way to change the default quick settings of the Draft submission script?
It’s on JPG default and when switching to MOV it goes first to mjpeg compression and 85 as quality.
I’d like that to be on MOV - h264 100% by default… is this a changeable preset or do I need then always need a custom template?
Thanks for confirming the issue is something outside of Deadline and within the AE install. Yeah, I suspect either a bad one-off AE proj file here for some reason or maybe oyu have a rogue 3rd party *.jsx script/plugin misbehaving? One thing you could do is try opening this exact AE proj file in the AE gui on this machine and enable the javascript debugger to see what comes up when it hits this jsx error message. The message part: “Expected: )” is indicating a jsx script which is missing or perhaps has one too many “)” characters in its script. Obviously a bit of an educated guess here.
Here’s a snippet from online on how to enable the debugger if required:
re: Draft default values
We have now fixed an issue with the Draft default values not being remembered between sessions. This will be fixed in the next major release of Deadline.
