Page 1 of 1
"Comp:/" notation is not resolved in a multi-OS environment

Posted:
Tue Oct 11, 2016 9:02 am
by Noel Froger
here you can see the problem...A Windows sending a job to a mac
the saver is set to write "Comp:/_OUT/round_1/round_1_.tga"
but send to the windows path to the mac so this fail
1. If i load the comp on windows the render is OK
2. If i load the comp on the mac the render is OK
3. but if the render is networked the sender machine send his own path for the saver so this is failing...
- Code: Select all
11/Oct/16 10:51:10 mdp-macpro3 (10.0.1.70): Saver1_1 failed to write to "Comp:/_OUT/round_1/round_1_.tga" ("//mdpsrv-gre2/xxx/_OUT/round_1/round_1_0002.tga") frame 2: No such file or directory
11/Oct/16 10:51:10 mdp-macpro3 (10.0.1.70): Saver1_1 failed at time 2
11/Oct/16 10:51:10 = ERROR: mdp-macpro3 (10.0.1.70) *failed* frame 2 of \\mdpsrv-gre2\xxx\WM_presentation_02.comp
11/Oct/16 10:51:10 mdp-macpro3 (10.0.1.70) has been reassigned
11/Oct/16 10:51:10 - mdp-macpro3 (10.0.1.70) closed the comp \\mdpsrv-gre2\xxx\WM_presentation_02.comp.
11/Oct/16 10:51:10 + mdp-macpro3 (10.0.1.70) disconnected, did 0 frames of \\mdpsrv-gre2\xxx\WM_presentation_02.comp
Could somebody can help me ?
Re: "Comp:/" notation is not resolved in a multi-OS environm

Posted:
Tue Oct 11, 2016 2:47 pm
by Stefan Kirste
how did u mount your Networkdrive in Windows and mac?
is "//mdpsrv-gre2/xxx" the UNC Path ? where u have acess on the mac?
Re: "Comp:/" notation is not resolved in a multi-OS environm

Posted:
Tue Oct 11, 2016 8:14 pm
by Noel Froger
Stefan Kirste wrote:how did u mount your Networkdrive in Windows and mac?
is "//mdpsrv-gre2/xxx" the UNC Path ? where u have acess on the mac?
Hi,
Starting with a "//mdpsrv-gre2/xxx" is the windows network path
On the Mac or linux you have to mount them physically somewhere.
But that's not the problem here. The problem is that in the fusion interface comp:/ is resolving correctly on
both OS but when launched in network render fusion comp:/ isn't sent but the resolved path so this is not working...
Anybody experienced with mixed environments ?
Re: "Comp:/" notation is not resolved in a multi-OS environm

Posted:
Tue Oct 11, 2016 9:00 pm
by Eric Westphal
This seems indeed like a mixed environment issue.
The mac is probably expecting the mac/linux notation:
//mdpsrv-gre2/xxx/_OUT (forward slashes)
while the comp itself gets loaded from
\\mdpsrv-gre2\xxx\ (backslashes)
Normally this should resolve automagically, but apparently it doesn't.
Looks like a support-case to me.
Re: "Comp:/" notation is not resolved in a multi-OS environm

Posted:
Wed Oct 12, 2016 1:49 am
by daniel.koch
It's not so much a notation difference; backslash translation is handled OK, as you can see from the log. The comp is read from \\mdpsrv-gre2\xxx\WM_presentation_02.comp and sent to the Mac, along with the location it came from. When Saver1_1 tries to save to Comp:/_OUT/round_1/round_1_.tga, this is mapped to //mdpsrv-gre2/xxx/_OUT/round_1/round_1_0002.tga (with forward slashes).
But the Mac does not understand UNC paths like //mdpsrv-gre2/xxx/, so the file isn't found. When you load the comp directly from the Mac, Finder connects to smb://mdpsrv/, mounts the xxx share in its /Volumes/ directory, then loads the comp from (and saves to) /Volumes/xxx/. Unfortunately Fusion can't identify or match mounts in /Volumes with UNC paths, and can't translate these UNC paths automatically.
But you can set up a path map on the Mac to do that. In Preferences/Path Map, create a new entry mapping from //mdpsrv-gre2 to /Volumes. Assuming the share name is the same on each, that should work for you (alternatively your map can include the share names for each). You'll still need to ensure the Windows share is mounted on your Mac first, of course. The same approach will work on Linux volumes mounted in /mnt/.
Re: "Comp:/" notation is not resolved in a multi-OS environm

Posted:
Wed Oct 12, 2016 5:11 am
by Eric Westphal
Ah! Cool. Makes sense.
Thanks for clarifying!
Re: "Comp:/" notation is not resolved in a multi-OS environm

Posted:
Wed Oct 12, 2016 12:11 pm
by Noel Froger
Thanks Daniel, for clearing that and providing a workaround.
We don't expect here fusion to automagicaly match mounts because for example, our network drives in the compagny aren't mount in /Volumes, and on linux this can vary so much ...
What i don't get is the meaning for the "comp:/" notation if this isn't used .. Am i getting that correctly ?
Cheers