The rendering job is submitted from Mac machine running OSX.
Both the input and output files are located on the same network share named “NetworkShare”.
Here is the file path as it is seen from the Apple machine or “a machine-submitter”:
/Volumes/NetworkShare/AE/output/Solar/Solar_34-40@@@@@.png
Before submitting a job using the “Configure Repository Options > Mapped Paths” dialog box I’ve defined the paths mapping as follow:
Replace Path: /Volumes/NetworkShare/
Windows Path: \\psf\NetworkShare\
When the render starts on Slave machine running WIndows in its Slave Log I can see that the mapped paths are being properly swapped:
2015-03-22 23:08:51: CheckPathMapping: Swapped "/Volumes/NetworkShare/AE/output/Solar/Solar_34-40@@@@@.png" with "//psf/NetworkShare/AE/output/Solar/Solar_34-40@@@@@.png"
2015-03-22 23:08:51: CheckPathMapping: Swapped "/Volumes/NetworkShare/AE/Output/output.@.jpg" with "//psf/NetworkShare/AE/Output/output.@.jpg"
On a same Slave Windows based machine in Deadline Monitor’s Task View I right-click on one of the Tasks and choose : “Explore Output”. It opens Windows File Explorer properly showing the content of the folder to where the output images were written. That feature works well.f
But “View Output” command from a same right-click menu results to an error message:
Output file: “\\psf\NetworkShare\AE\Output\output.@.jpg” does not exist.
It seems there is something wrong with the use of three backward slashes seen at the beginning of the output sequence’s file path:
[b]\\psf\NetworkShare[/b]…"
Should it be there two slashes instead? How to avoid it? Please advise.
Hello,
Can I ask what Deadline version you are using? Is the application being use After Effect, or something else? I am curious about the presence of the @ symbols, were those edits by you, or does the output have an @ symbol? Would be good to know this in order to trouble shoot. Thanks.
It is Deadline 7.
I have tested it with Maya and other submitters (from inside of the application and from Deadline “Submit” menu). The triple backward slash problem persists regardless of the job’s plugin type.
Deadline does a proper job of swapping the paths for the scene file path being rendered, for the output folder path (seen when you right-click a task in Task View and choose “Explore Output” sub-menu).
But it puts that triple backward slashes “\” when it assembles a file path to the rendered output images. This assembled path could be seen by right-clicking the task name in Task View and choosing “Copy Output Path” menu.
You can also right-click the task name in Task View and choose “View Output” command. “View Output” command will try to lunch a default image viewer passing to it the same file path shown when you right-click and choose “Copy Output Path”.
I think both “Copy Output Path” and “View Output” commands (both are accessed via task’s name right-click menu) use the same code to assemble the file path to rendered image sequence. May be there is a bug there resulting to three forward slashes at the beginning of the Windows path when it Deadline swaps mapped paths from OSX path to Windows.
Once again, here is the example:
Hello,
So I have gotten a chance to test this, and was not able to replicate this. I tested Deadline 6.2.1.50, Deadline 7.0.3.0, and 7.1.0.27, and I did not see this. My Mapped Paths and the resulting output paths in the monitor are in the attached images. Could you archive the job you are seeing this on so we can take a look? Thanks.
Cheers,
I was able to get some additional info on this problem…
When Windows machine picks up a render job Deadline calls CheckPathMapping function to “translate” a supplied a Mac OSX file path to Windows file path. Deadline uses the settings specified in Configure Repository Options > Mapped Paths.. Here is the screenshot of the current settings:
Interesting that Deadline’s CheckPathMapping does a proper file path translation when it translates a OSX scene file paths for both maya scene file and maya project:
[code]Swapped “/Volumes/repo/projects/rfm_project/scenes/binary.mb” with “w:\projects/rfm_project/scenes/binary.mb”
2015-05-02 10:01:18: CheckPathMapping: Swapped “/Volumes/repo/projects/rfm_project” with “w:\projects/rfm_project”.[/code]
But then later (after the rendering) it fails to do a proper job… Here is a Slave’s log:
2015-05-02 10:01:32: CheckPathMapping: Swapped "\\Volumes\repo\projects\rfm_project\images\renderedImage_11.0001.png" with "\w:\projects\rfm_project\images\renderedImage_11.0001.png"
Scheduler Thread - Could not get file size for \\w:\projects\rfm_project\images\vrayLight_11.0001.png: The given path's format is not supported. (System.NotSupportedException)
Once again, it was a Windows machine that performed the rendering. Yet by some reason it “thinks” the images it rendered were written in Mac OSX style file path…: “/Volumes/repo/projects/rfm_project/images/renderedImage_11.0001.png”
Apparently, Deadline tries to replace this “Mac OSX file path” forward slashes with the backward slashes: so, instead of “/Volumes/repo/projects/rfm_project/images/renderedImage_11.0001.png” it uses “\Volumes\repo\projects\rfm_project\images\renderedImage_11.0001.png” which results to illegal file path: “”\w:\projects\rfm_project\images\renderedImage_11.0001.png".
How do I submit the archived job so you could take a look at it?
Here are few more screenshots showing the Repository Options Settings values and their effect on how Deadline translates the Mac paths to Windows paths:
###############
Approach # 1. With the Network Drive mapped as “W” letter on Windows machine and Repository configured as:
###############
getting a proper path translation from Mac to WIndows for “Explore Output” right-click menu:
But Deadline fails to translate properly a Mac file path used by “Copy Output Path” right-click menu. There are two backward slashes proceeding drive letter “w:” what makes file path invalid:
###############
Approach # 2. With the Network Drive not mapped as a letter on Windows machine.
Instead a Server local ip address is used.
And Repository configured as:
###############
Once again, the file path translation from Mac to Windows for the “Explore Output” right-click menu works properly:
And just like with the approach # 1 (when drive letter was used instead of ip address) the translated file path used by “Copy Output Path” is all wrong:
The problem with file path translation becomes evident in other places as well such as when Deadline tries to get the rendered images file size during the last portion of rendering task (see my earlier). Here is the copied/pasted output from Slave log showing this occurrence:
2015-05-02 10:01:32: CheckPathMapping: Swapped "\\Volumes\repo\projects\rfm_project\images\renderedImage_11.0001.png" with "\w:\projects\rfm_project\images\renderedImage_11.0001.png"
Scheduler Thread - Could not get file size for \\w:\projects\rfm_project\images\vrayLight_11.0001.png: The given path's format is not supported. (System.NotSupportedException)
I am sure there could be other places where the wrong path translation will effect the reliability of the rendering task as well. Please advise.
I’ve been able to reproduce this on my machine, I’m unsure why Dwight wasn’t able to. What version of 7 are you running, exactly? This might’ve been a regression in later code than he was trying (I was on the latest dev code).
It wasn’t immediately apparent to me what was doing it, but something along the way definitely added another slash in there. I’ll log it to fixed internally, but unfortunately, I’m not sure that there’s much of a workaround for you in the meantime, since it seems to be in compiled code. I’ll keep you posted if come up with something, though!
Cheers,
Jon
I am glad you were able to reproduce the same issue! Hopefully you would be able to debug and fix it.
I am on:
Deadline Version: 7.0.2.3 R (24b5c0a7f)
FranticX Version: 2.1.0.0 R (3f765e675)
From what I understand the earlier version of Deadline might not have the same bug. Could it be a solution to switch to the earlier version of Deadline (till the newer release of Deadlien gets it fixed)?
Thanks in advance!
I’m not sure that downgrading would be worth it for this small of an issue… Keep in mind you’d also be re-introducing older issues we’ve fixed in 7.0. As far as I can tell, this is limited to the Copy Output Location of the Task Pane, unless you’ve experienced otherwise?
If it’s just a matter of that functionality being important to your workflow, you could write a Task script that copies the properly swapped output path to the clipboard. This wouldn’t really be extensible if there are multiple different output paths for a single task, but could work in the simple case of one path per Task.
