Taken from a previous post (seemed more appropriate to start a new thread).
Is there a way to create a post-job script (or any script, really) that will execute on the repository server?
Currently, this is not possible through Deadline. The main reason is that unless you’re running Pulse on the repository machine, there is no actual Deadline application running to execute the scripts, and in the case of the post-job script, it will run on the machine that dequeues the corresponding task.
Depending on the OS you have the repository on, you might be able to set up a scheduled task to execute scripts. Out of curiosity, what functionality would these scripts be performing?
Cheers,
- Ryan
Well, I need to compress sequences to preview-quality Quicktime clips post-render, but all our render nodes are 64 bit, and I was hoping to avoid installing 32-bit Nuke on every single render node (though that looks to be the easiest way at this point, unfortunately).
Just offhand, I don’t suppose anyone knows whether or not Quicktime Pro has command-line encoding functionality on Windows… So far I’ve come up empty-handed.
Why do you need to install nuke on every machine? Couldn’t you just pick one machine to handle this. Create a nuke group with that one machine. Then run the compression as a dependant job assigned to the nuke group as opposed to a post task?
Well, automation is a big part of it. I think it’ll be easier to do a mass-silent install of Nuke x86 across the whole farm than to set up dependent jobs for every sequence we render.
We ship a command line QT tool with Deadline that is used by the Quicktime plugin:
franticfilms.com/software/su … cktime.php
The app is installed to the Deadline bin folder, and you can run it from the command line without any arguments to get the usage instructions.
Wow… Don’t know how I missed that one before. 
Thanks, this is better than perfect!
Hmm… so after looking at that executable, it seems the only ways to actually specify the encoder options are to submit a job using Fusion to encode, or submit a job and then manually set the codec options in the popup dialog after submission.
This is a problem for automation, however, as I would like to simply call the executable directly without submitting a Deadline job. What kind of settings file/template does Deadline pass to this .exe when an encoding job is submitted? And is there way I could get ahold of one so as to duplicate the formatting?
The command line QT app doesn’t depend on anything from Fusion. If you’re using the same encoding settings, you could just run the QT app once with the -ExportSettings option to set up the xml settings file. Then just put this file on the network somewhere and reference it when you run the QT app with the -CreateMovie option.
The settings file is an xml file, but most of it is just binary data between a couple of xml tags, so duplicating it manually could be difficult.
Got it, thanks. One more small question. I’ve saved a settings file, but I noticed the command line encoder takes a “frame rate” parameter. Does this override the frame rate saved in the settings file? Or does the settings file not even store a frame rate?
Similarly, does the “output codec” parameter supersede the settings file, and what values are usable for this parameter?
Forget those questions… I think I’ve got it all sorted.
Thanks again for all your help.