submit to deadline is not working in nuke 6.3v4

Deadline
1

i have the repository in c:\rep
installed the client on the same machine

followed these steps>>

Nuke 6 and Later
Copy [Repository]\clientSetup\Nuke\SubmitToDeadline.py to [Nuke Install Directory]\plugins.
Create a menu item in the Nuke UI by adding the following lines to the menu.py file in the Nuke plugins folder:
import SubmitToDeadline
tb = menubar.addMenu("&Thinkbox")
tb.addCommand(“Submit To Deadline”, SubmitToDeadline.main, “”)

im getting the error >>
//////////////////////

“The SubmitNukeToDeadline.py script could not be found in the Deadline Repository. Please make sure that the Deadline Client has been installed on this machine, that the Deadline Client bin folder is in your PATH, and that the Deadline Client has been configured to point to a valid Repository.”

/////////////////////

ive renamed the script from “submitToDeadline” to “SubmitNuketoDeadline” still im getting the same error.

Please help me…

2

Hi,
Can you right-click on the deadline launcher app in the system try and click on the choose repository button and give it the path to your repository. In this case, c:\rep.
Mike

3

Also, you should change the name of the script back to what it was. The SubmitToDeadline.py script that you copied to the Nuke plugins folder is a proxy script that calls SubmitNuketoDeadline.py, which is located in \your\repository\submission\Nuke. The proxy figures out which repository you’re connected to, and then builds up the path to call SubmitNuketoDeadline.py from the repository. If it’s unable to do so, the cause is often one or more of the following:

  1. The Deadline Client hasn’t been installed on this machine (but we can already rule that out).
  2. The Deadline Client bin folder isn’t in your PATH. If you open a command prompt and run “deadlinecommand.exe getrepositoryroot”, you can confirm if it’s in your path. If you get an error that deadlinecommand.exe is not recognized, then you know it’s not in your path.
  3. The Deadline Client hasn’t been configured to point to a valid Repository. The command you ran in (2) should print out your repository path (C:\rep). If it doesn’t, then you know it’s not configured, and you can follow Mike’s instructions to set the repository.

Cheers,

  • Ryan
4

somehow its working… now i have a question which i need to work to generate quicktimes… I do know that there is a event gen script to generate quicktime after the renders… but we have a different strategy in generating the quicktimes like…

  1. we burnin the luts in rendered outputs which is hiquality jpegs and stencils with artist name frame numbers and shot desc in it.
  2. we leave the dpx without the luts applied on it …

so when we plug the event gen script since one of the sequence is dpx which cant be rendered and thus fails. And also it doesnt include any luts during the process which will result in generating (if it renders ) log formats.

Is there anyway where i can select the write nodes for the event gen?

5

You may have to create your own event plugin and customize it to suit your needs. If the existing quicktime generator doesn’t give you enough flexibility, then maybe Draft might be the solution:
thinkboxsoftware.com/news/20 … dline.html

Draft is still in beta, but we are still accepting beta testers. You can create templates in Python, and use the Draft module to process your images as you see fit.

Cheers,

  • Ryan