Hi,
I tried to render a Quicktime movie using Deadline 3. Both Fusion 5 and DFusion 4 write out a numbered sequence of .mov files instead of one single .mov. The AVI format works OK by the way. Also, I rendered the quicktime - comp/flow on the local machine with no problems.
Where to tweak to fix this?
Marcus
Weird. We aren’t having this problem here and we use the Fusion Quicktime plugin daily. When the QT job is submitted, does it have only one task which represents all the frames? If there are individual tasks per frame, that could cause this problem (although the submitter should prevent this from happening).
Cheers,
No, I mean the “Fusion”, not the “Fusion Quicktime” plugin. I tested regular eyeon DF / F5 flows, each containing a saver that was supposed to write out a QT. The jobs, the SubmitToDeadline.dfscript / SubmitToDeadline.eyeonscript generate, look good so far. In the submission GUI, in the comment field, there is a message “movie format…”. One machine gets one task with all frames - the usual way like in v2.7. No individual tasks per frame.
As I said, when I set the savers in the test flows to write out .avi, it’s rendering correct, single .avi files. It’s only the .mov filetype that fails (as far as I tested it).
greets
Marcus
Just tried this here with F5 and it’s working fine. I created a loader of 150 frames and a QT saver, and a single QT movie file was generated which contained the full sequence. The fact that it is effecting both DF and F5 for you is strange. Maybe it has something to do with the version of Quicktime that is installed on the machines.
One thing you can try is starting up fusion and opening up your comp. Then go to the console tab and type in the following (where ‘s’ is the start frame and ‘e’ is the end frame):
comp:Render( true, s, e )This is essentially the same script function that deadline is calling to do the render.
Cheers,
The problem was solved by re-installing the Quicktime Package on the slave by the way. So it hadn’t to do anything with Deadline at all.
Marcus