Hi,
I have like it seems a weird bug on a mac, when trying to generate a quicktime movie. Somehow it always appends 0 in front of the first number in file sequence.
When submitting the job from nuke i do it in suspended state, and after that in deadline monitor i create a script job to Generate a quicktime preview movie out of rendered image sequence, which, is dependent on the parent job.
The job for nuke render fine, and then the quicktime generation job starts and failes with error because it can’t find filename like this
0: INFO: Startup Directory: "/Applications/Deadline/Resources/bin"
0: INFO: Process Priority: BelowNormal
0: INFO: Process is now running
0: STDOUT:
0: STDOUT: Input file: "/Volumes/deadline/render/nuke/tests/colorwheel_mb.0001.jpg"
0: STDOUT: Export settings file: "/Applications/Deadline/Resources/slave/jobsData/quicktime_export_settings.xml"
0: STDOUT: Codec: "QuickTime Movie"
0: STDOUT: Start frame: 1
0: STDOUT: End frame: 100
0: STDOUT: Frame rate: 24.00
0: STDOUT: Output file: "/Volumes/deadline/render/nuke/tests/colorwheel_mb..mov"
0: STDOUT:
0: STDOUT: Input file "/Volumes/deadline/render/nuke/tests/colorwheel_mb00001.jpg" does not exist
0: INFO: Process exit code: 1
i tried both with underscore _ and with . naming convention, both times, deadline appended 0 in front of number sequence. I even tried removing one zero when submitting job for quicktime in hope that it will read correctly 4 numbered image sequence, but then, naturally, complained “colorwheel_mb001.jpg” does not exist.
Quicktime generation works fine if there are no dots or slashes or anything in the filename like file0001.jpg.
I have one question though. Is it possible to have quicktime movie job automatically added when compositing job for example is added, and plus that is automatically dependent on it? If not it would be nice to have something like that in native apps submission dialogs in future release.
Hey vedranfx,
The reason the QuickTime Generator is doing this with the file names is that there was a bug in the code that we were using to parse in the file name. This has now been fixed and will be included in our next release. To get around this bug for now there must be a non-special character in front of the frame number (e.g. “/Volumes/deadline/render/nuke/tests/colorwheel_mb0001.jpg” in stead of “/Volumes/deadline/render/nuke/tests/colorwheel_mb.0001.jpg”) for the QuickTime Generator to recognize the file properly and not include the extra ‘0’. Sorry for any inconvenience this may cause you.
As for your question about having a QuickTime job automatically created when you submit certain jobs, this is on our wish list of features but we don’t have an estimated time line for when it will get implemented.
Sincerely,
Justin
Deadline Developer
Hey justin,
Thanks for prompt reply, yes i figured out that it works if there are no special characters before frame numbering…Also how i would workaround the problem when creating a quicktime script job, from the parent job, if that parent job has not rendered any frames? it complains if type the name of the file which will be there after the parent job finishes, and does not allow me proceed.
Hey vedranfx,
I’m having some trouble reproducing the problem that you are having, would you be able to post the exact error message Deadline is giving you and the details on how you are submitting the job? This will make it a lot easier for me to reproduce the problem and find an appropriate solution.
Sincerely,
Justin
Hey vedranfx,
I just did a little more testing and I think I may have found a workaround for your problem. The problem seems to be with the file explorer dialog. It checks for the existence of the file before it enters the location into the text field. To get around this you can type the file name with its location directly into the text field by hand, or by copying it and pasting it into the text field. Let me know if this solves your problem!
Sincerely,
Justin
Its very easy to reproduce.
My goal is to make quicktime job start after dependent job finishes rendering. But, when im creating my submits, the frames arent yet rendered, and when you go by searching for the INPUT filename for the quicktime to generate .mov it complains that is does not exist which is of course, true.
So the solution was to enter manually the name in the input name field, not to enter and browse for one…Although its logical why this error happens i figured out that deadline could extract the filename from the parent job, if the quicktime script has been submited from parent job, using the Script menu…Maybe thats a quick fix to quicktime script code?
Thanks
Vedran
Hey vedranfx,
This seems to be a good temporary workaround for this problem. Hopefully we will be able to implement the automatic QuickTime Job generation option into the submission scripts soon but until then this should work.
Sincerely,
Justin
