AWS Thinkbox Discussion Forums

Draft Tile Rendering feedback

  1. On OSX there is a double forward slash “//” separating the directory and filename.extension in the RC render ‘task’ outputs “Copy Output Path” in a 3dsMax Job. On Windows, this same job is all back-slashes and no duplicate back-slashes exist.

  2. Draft Tile Assembler *.config files are created in the Job Aux directory and then should be copied down to the render output directory for possible later re-use. The file naming convention looks a bit out/wrong? - “test_0000_config_0_2013_12_4__020_36_20.txt” - strange time stamp format? Another example: “test_MultiMatteElement_0000_config_1_2013_12_4__020_36_20.txt”

  3. Draft TA *.config files ‘sometimes’ don’t get copied down from the Job Aux directory to the final render output directory for each render pass tile sequence. I’m struggling to find the pattern on this one to re-produce. Maybe it’s something to do with multiple Tile submissions…? still searching…

  4. In-consistent path separator endings for 3dsMax & Draft Tile Assembler jobs:
    On Windows = “” at the end of 3dsMax job
    On Windows = “” nothing at end of Draft job
    On OSX = “//” at end of 3dsMax job

Keep in mind the Tile / Region code I have here is a month ahead of what you are testing, so some of these might be already fixed in my WIP version.
If they are not not, I will look into them.

Regarding 2, the actual submission workflow is exactly the opposite. The files are created in the output folder and copied during submission to the Job folder. So the render output folder is the primary location where they get generated for future reference, but the Job Aux copies are used to actually perform the assembly.

Regarding 3, the file names look right to me in my current build. I will keep an eye for strangeness though.

Hey Mike,

For 1& 4 these are the same issue, and I am not sure we really need to do anything about it since it shouldn’t affect anything really. All that is happening is in smtd one of the 2 is printing out the wrong directory to the corresponding submit info file

Grant

Hi Grant,
The problem, is that if the path & path separators are not correct and a user on another platform OS, goes to view an image created from the Max job, via the deadline monitor view output and configured image viewer settings, then it will fail to resolve the path.
Mike

Hey Mike,
It looks all max jobs have been like this for a while. Have you seen any specific cases where it has failed for you? Otherwise it does not seem like their is a real reason to change it.

Grant

Privacy | Site terms | Cookie preferences