Deadline Monitor - Submit DJV job to Deadline (Win7)

Deadline
1

Figured I would make a new thread, though the goal is still the same (making a QT in Deadline). DJV actually seems to get farther with aforementioned goal, and it also is Windows based (which is better for us anyway).

The problem I am seeing here just seems to be that it doesn’t render properly back out to the file server.

Deadline Version 5.2.47700
Windows 7 Rendernode
djv-0.8.3-pre2_winxp-x86

Here is the error:

0: STDOUT: Z:\vfx_010.101551-101911.dpx 1920x1080:1.78 RGB U10 361@23.976
0: STDOUT: [ERROR] Image I/O, QuickTime - Cannot open: Z:\DJVQuicktimeTest4.mov (#-43)
0: An exception occurred: Exception during render: An error occurred in RenderTasks(): [ERROR] Image I/O, QuickTime - Cannot open: Z:\DJVQuicktimeTest4.mov (#-43)
at Deadline.Plugins.ScriptPlugin.RenderTasks(String taskId, Int32 startFrame, Int32 endFrame, String& outMessage) (Deadline.Plugins.RenderPluginException)

It works when I just render the .MOV to the C drive (just by changing the output [in red below] path to C:). Permissions on the server are wide wiiiide open and I remapped the network drive under that specific cmd.exe just to make sure it wasn’t an issue with that shell instance. I can run just “echo asdf > Z:\temp.txt” and it works fine creating the file and writing to it… Something to do specifically with DJV?

0: INFO: Render Argument: “Z:\vfx_010.101551-101911.dpx” “Z:\DJVQuicktimeTest4.mov” -time_units frames -tag_auto True -load dpx color profile auto -save quicktime codec h264 -save quicktime quality lossless

On a whim I decided to try rendering it via the Mac, hilariously enough it renders out to the server just fine from there! It’s mounting the server via smb as well so I don’t really know what could be causing the difference, going to try the command line render out to the server from Windows and just crank up the Samba logging and see if it shows me anything untoward.

2

Is the Deadline slave on Windows running as a different user than the one you’re mapping the Z: for (for example, it’s running as a service as a different user)? That could explain the problem.

Have you tried rendering to the UNC path instead of Z: to see if that works?

3

Mapped as the same user running it yes.

I will try the UNC path and see what it do.

4

Worryingly, this feels familiar to me :frowning:
Can you try creating the *.mov out movie to 1 directory level deeper instead of the root @ “z:\”?

Me thinks DJV is misbehaving here? Darby is threatening to release a newer v0.9 version for Windows shortly. (Its already out for OSX and Linux)

Is it this newer version you tested successfully with OSX or was your OSX successful test also using exactly the same version of DJV?

Thanks,
Mike

5

That actually was deeper in the directory I cut it out for security. I used .8 on both OSX and Windows, was about to use .9 but then I saw it wasn’t really in Deadline so I didn’t use it. OSX/Windows tests were using the exact same version.

6

So, to confirm. Does it work if you output the movie to a sub-directory or not?

7

Nope.

8

Hi,
Could you try not using H264 codec and change to something else for a test?
Any difference?