Re: NUKE Studio 11.35 Download 2019
Thomas
I have nuke_studio fully working with the old style config, but after updating to config_default2 it does not even initialize. Under Nuke 12.0 studio I get no errors in the script editor, but in Nuke 11.1v3 I get:
for clarification this issue is only with nuke studio, regular nuke, and nukeX function perfectly under the new config, with all our custom pipeline stuff hooked up. I am ONLY experiencing issues with Nuke Studio 11.1v4 and 12.0v2 (basically all supported Nuke Studios)
Hey,
I mentioned that I was using the default paths, because we generally launch using a .py launcher that sets all our studio environment variables, and global paths to load plugins/gizmos ect for nuke, but I am bypassing that for these tests, because it does add environment variables that could clash (though they are tested under the other config with no issues), but to eliminate that as a problem and keep these tests clean, I am circumventing all of that and doing a clean launch using the system installed path.
I am publishing from nuke studio to create and update sequences and shots in Ftrack. Our studio is using ftrack folders and subfolders and nesting sequences and shots within those. I have not found the method for doing this when I publish out of nuke studio. Does anyone have an example or can point me to document that can help? Im attaching image for clarity
Hey, testing the NukeStudio functionality also. Is it possible to submit sequence but change the starting frame? The way I understand it, Deadline now takes the correct amount of frames when submitting a sequence but not the starting frame. So since all our compositions start at 1001, it never renders the correct frames. Could it be changed in the py code somewhere? It seems much more stable than nuke frameserver.
As I'm sure you're well aware, Nuke Studio has the incredibly useful tool which creates an entire directory structure, render plates, creates nuke scripts, etc. And you can also sneak in python commands for each shot. At our little studio, we've created a Nuke Studio Uploader to our custom shot tracker, which will render and upload each shot to our online dashboard, alongside all of the requisite info for that shot (similar to shotgun).
Does Prism have any kind of python 'API'/library we might use to enter all shot data into the the Prism shot data .yml files? The nuke studio API can also acknowledge tags, so we may also be able to tag shots to automatically create maya, houdini, or nuke files upon creation. We could also bundle this with some of the Kitsu sync people have been playing with.
If you need to modify any existing functions in Prism you can create a Prism plugin which monkeypatches a Prism function with your own custom function. That way you can basically add your custom code to every function in Prism and still keep all your modifications in a plugin, which makes it easier to distribute your changes to other people.
I'm reaching out because we've also been working on Kitsu support for this. @danell - I've noticed in your kitsu/prism integration there is a place in the UI for the user's kitsu login / password. I'm wondering if we could collaborate in order to store the kitsu user's API key in a config file where any prism user can access it? Honestly I'm new to kitsu, but it seems like their API is robust enough to support logins without storing the user's username/password as plaintext. (even though I've noticed that some kitsu config files require us to do so ? )
Once you login you will be logged in until you close your python instance (like if you restart Prism). But as the user has written their url, username and password into Prism it's saved in the users config file. Every time there is a call to Kitsu I check if there is any saved login-keys saved. If not, then login with the saved information.
This is a subclass of the standard Hiero transcoding task, which will register the results of the transcode as a Publish in ShotGrid. Optionally a Version will also be created in ShotGrid. If a Version is created, then a Quicktime will also be created and uploaded as Screening Room media.
This is a subclass of the standard Hiero Nuke script exporter, which registers the resulting Nuke script as a PublishedFile in ShotGrid linked to the Shot. The settings allow you to specify which Toolkit-enabled WriteNodes to include in the file on export.
The app settings plate_published_file_type and nuke_script_published_file_type allow you to control what file type the PublishedFiles are registered as. In addition, nuke_script_toolkit_write_nodes allows you to control which WriteNode settings should be available in the export dialog.
The name of the Hiero sequence will be used for the sequence name, and theshots will have their cut info filled in (Cut Order, Head In, Cut In, Cut Out,Tail Out, Cut Duration, and Working Duration). In addition if poster frameswere selected for the sequence or the items that make up the shot, they will beuploaded as the thumbnails for the shots.
You can reserve Deadline Workers for a rendering over the Nuke Studio frame server from Nuke Studio by installing the integrated submission script, or you can reserve them from the Monitor.The instructions for installing the integrated submission script can be found further down this page. The Deadline Workers will create the specified number of Nuke Frame Server Workersprocesses on the machines in which they run.
After the render is finished, you can press Release Machines or close the submitter UI (Setup Frame Server Workers With Deadline) to mark the Frame Server Job as complete so that the render nodes can move on to another Job.
Note: Only one Deadline Worker per machine may pick up a Nuke Frame Server Job, as allowing multiple Workers on the same machine to try to bind to the same port would not work. Deadline will also fail a render if a Deadline Worker running on the Master Machinetries to pick up the Reserve Job, as it is already running an instance of the Frame Server and the same port binding conflict can occur.
You can configure the Nuke Frame Server plug-in settings from the Monitor. While in super user mode, select Tools -> Configure Plugins and select the NukeFrameServer plug-in from the list on the left.
Note, if the executable supports a MAJOR.MINOR.REVISION (9.0.123) numbering system in its path, then you will need to configure the explicit exe path to the particular revision that you have installed on your machines. Deadline does not track every possible revision available or indeed where it might be custom installed to, so a studio should verify their exe paths are correct for each application version they choose to use with Deadline. Multiple exe paths can still be declared and the first one that is found on a particular Worker on a particular platform will be used from the exe list.
Workers To Use Interactive License: A list of Workers that should use an interactive Nuke license instead of a render license. Use a , to separate multiple Worker names, for example: worker001,worker002,worker003
Prepare OFX Cache Before Rendering: If enabled, Deadline will try to create the temporary ofxplugincache folder before rendering, which helps ensure that comps that use OFX plugins render properly.
The following procedures describe how to install the integrated Nuke Frame Server submission script. This script allows for submitting Nuke Reserve Frame Server Workers Jobs to Deadline directly from within the Nuke/Nuke Studioediting GUI.
A CustomSanityChecks.py file can be created alongside the main ReserveFrameServerSlaves.py submission script (in [Repository]\submission\Nuke\Main), and will be evaluated if it exists. This script will let you set any of the initial properties in the submission script prior to displaying the submission window. You can also use it to run your own checks and display errors or warnings to the user. Here is a very simple example of what this script could look like:
7fc3f7cf58