Nuke - Quickdailies Node


A custom dailies node in Nuke that creates a quicktime and creates a corresponding review version in Shotgun.
Latest Version: v0.3.6 (prod)
For our version numbers, we follow the Semantic Versioning standard.
System Name: tk-nuke-quickdailies

Please Note: This document describes functionality only available if you have taken control over a Toolkit configuration. Please refer to the Shotgun Integrations User Guide for more details.

This app adds a node type to Nuke which you can add anywhere in your node graph. Once added to your scene, you can double click the node, go to the properties page and hit the "Send to Review" button. The app will then render a quicktime of your scene, add burnins and slates and send it to Shotgun. It will also generate filmstrip thumbnails which makes it easy to preview the version in Shotgun.


This Shotgun App adds a custom node to Nuke. The node is called Quick Dailies and lets you quickly send stuff to review. You can create a Quick Dailies Node via the Shotgun Node Menu:


You simply attach the node to any part of the Nuke graph that you want to inspect and send to review:


If you click on the node, the following, very simple UI appears:


Clicking the button will launch a dialog asking you for comments and to type in a name. The name is auto-populated with the current work file name if this is available:


Once you click "ok", the App will generate a Quicktime with a slate and burn-ins and create a corresponding Version in Shotgun.

Snapshot Snapshot

Related Apps and Documents

Review Submission

An app that provides functionality to help submitting image sequences as Versions in Shotgun for review. This app does not have a UI but instead provides API methods for quicktime and review generation. You can call the app from your scripts, or from within hooks. For example, your publish configuration can call this as part of a post process hook if you want to create a quicktime and send it for review. This app will generate a quicktime with burn-ins and slates. You can configure if you want it to upload the quicktime to Shotgun or keep it on disk, or both. Lastly it will create a new version inside of Shotgun, ready to reviewed in Screening Room!

Installation and Updates

Adding this App to the Shotgun Pipeline Toolkit

If you want to add this app to Project XYZ, in an environment named asset, execute the following command:

> tank Project XYZ install_app asset tk-nuke tk-nuke-quickdailies

Updating to the latest version

If you already have this item installed in a project and you want to get the latest version, you can run the update command. You can either navigate to the tank command that comes with that specific project, and run it there:

> cd /my_tank_configs/project_xyz
> ./tank updates

Alternatively, you can run your studio tank command and specify the project name to tell it which project to run the update check for:

> tank Project XYZ updates

Collaboration and Evolution

If you have access to the Shotgun Pipeline Toolkit, you also have access to the source code for all apps, engines and frameworks in Github where we store and manage them. Feel free to evolve these items; use them as a base for further independent development, make changes (and submit pull requests back to us!) or simply tinker with them to see how they have been built and how the toolkit works. You can access this code repository at

Special Requirements

  • You need Shotgun Pipeline Toolkit Core API version v0.14.12 or higher to use this.
  • You need Engine version v0.2.3 or higher to use this.


Below is a summary of all the configuration settings used. These settings need to be defined in the environment file where you want to enable this App or Engine.


Type: list

Description: List of hooks that runs after a quickdaily has been rendered and uploaded to Shotgun. Parameters passed to the hook are mov_path, version_id and comments.


Type: template

Description: The location where the output quicktime will be written to. The two fields iteration and optionally name will be populated. Iteration is an integer number which will be automatically calculated based on the existing files on disk. Name is typically derived from the name of the current scene.


Type: hook

Default Value: {self}/

Description: Hook for customizing codec settings used when generating quickdaily items for review.


Type: template

Description: Template used to populate the version name in Shotgun. You can use any field from the current context (such as for example Shot and Sequence) and the template must include iteration. Additionally, name and the current version will be used if they are defined.


Type: int

Description: The quicktime resolution height


Type: int

Description: The quicktime resolution width


Type: bool

Default Value: True

Description: If true, the Quicktime movie will be uploaded to Shotgun in the Version's sg_uploaded_movie field which will allow the Version to be viewed in the Shotgun web player.


Type: template

Description: Template that will be used to extract the name and version from the current scene. Both name and version are optional.

Release Notes

Welcome to the release notes for this App. Below you will find an overview of all the changes we did for each release. We try to be as detailed as possible and include all bugs we have fixed, features we have added and things that may have changed. If you have questions about a particular release, don't hesitate to contact our support team!



Updated app icon.



Small fix to correctly support Nuke 10.5v1



Accounts for changes in the Write node's .mov encoding settings in 10.0v2+


With the 10.0v2 release, Nuke's dependency on the Quicktime desktop application was removed. As a result, if Quicktime is not installed, the settings for the Write node when outputting the .mov file type have changed.



Adds full support for on-the-fly context changes by re-caching templates when needed.



Quicktime movie will be uploaded to Shotgun by default



Fix an issue where bad quality QuickTimes gets generated in Nuke 9


Adds support for context changes.



Uses get_current_user to determine the current Shotgun user to associate the daily with.



Moves the Quicktime generation settings into a hook


  • Allows studios to easily override the default output settings. Also adds handling for the knob name change in Nuke 9.0 from codec to meta_codec.
  • Added setting to upload the movie to Shotgun. This allows reviewing the quickdaily in the Shotgun web player. Note, this is false by default to maintain backwards compatibility.
  • Updated default settings for Nuke 9+ on linux. Nuke 9 removed ffmpeg as a file_type and replaced it with mov64. This handles that case and sets the codec to jpeg in that case to match the behavior on Mac and Windows.


Name is no longer a required key in templates


Renames and support for the new name Sgtk.


Added app icon.


Updated to use new folder creation API methods.


Updated manifest to require core v0.12.5


App now supports code reload.


Extended the template format. Customizable names in Shotgun.

  • The way versions are named in shotgun can now be customized via a template.
  • Previously, version numbers were not used with this app, only the concept of iterations. Now version numbers can be used in the templates, but are optional.
  • The UI has been tweaked so that it displays the full shotgun version name, as it will be appear, and it is no longer editable.


Fixed a minor bug in the post-hook execution.


Initial Release to the Tank App Store.



  • 0

    This app doesn't upload the movie to Shotgun by default so your daily won't be viewable in the browser using Screening Room. We plan to update quickdailies to use tk-multi-reviewsubmission which is a more standardized "api-type" app. However, for now, you can add this functionality yourself using a very simple hook. 

    Check out this forum post for details: "How do I view my Nuke Quickdaily in Shotgun Screening Room"

    ** UPDATE **

    This information is outdated. See comment below for updated information.


  • 0
    Tony Hudson

    the below is not very clear:


    Below is a summary of all the configuration settings used. These settings need to be defined in the environment file where you want to enable this App or Engine.

    It would be much more helpful to give the NAME of the .yml file that should be edited. I've been searching for an hour and cannot find the file to edit in order to set the move size and a format. By default it is giving me a prores 4444 file which cannot be viewed in the web view NOR rv as rv will not display prores files


  • 0

    As of v0.2.0, you can now set the upload_movie setting to true in order to have the Quick Dailies app upload your movie to Shotgun in order to review it in the web player. 

    We have also moved the codec settings into a hook so you can customize this as needed by your studio. By default the hook is also handling the various changes and updates in Nuke so it doesn't fall back on the default Apple ProRes 4444 codec.

  • 0

    @tony, sorry for the confusion and trouble. With the new update, you should be able to update and things should work as expected again. The "environment files" we refer to in Toolkit documentation, are located inside your pipeline configuration in the config/env/ . These files are all .yml files and correspond to what type of thing you're working on (a Task for a Shot, a Task for an Asset, etc). For example, shot_step.yml refers to the environment when you're working on a Shot Task (the "step" in the filename refers to the PIpeline Step of the Task) and asset_step.yml corresponds to working on a Task for an Asset. These environments would be loaded by default when launching Toolkit from the Shotgun web application by right-clicking on a Task linked to a Shot or Asset. 

    In general, these are the two most common environments, but if you don't use Tasks at your studio, you may just want to work on the Shot ( shot.yml ) or Asset ( asset.yml ). The Project environment ( project.yml ) is the default envrionment loaded when launching your DCCs from SG Desktop, but it also the environment you'd work on in Hiero for example. 

    Hope that explains things a little better!


  • 0

    I am getting this error on my side after the new default config, and the recent updates


    API read() Playlist.sg_status doesn't exist:

    {"path"=>"sg_status", "values"=>["clsd"], "relation"=>"is_not"}



  • 0
    Manne Öhrström

    Hi Simon, This looks like it could be a bug on our end - sorry! We'll look into it asap. As a workaround to unblock you, you could create a status field on playlist and name it status (so that it's API name becomes sg_status). Then everything should work. (It turns out all sites don't have that field by default so we have to tweak or logic for listing 'active' playlists).


  • 0

    Wonderful! it works now!

    Thank you very much!



Please sign in to leave a comment.