Slate frame generation in Nuke

Hi!
I’ve been trying to setup the slate frame generation in Nuke, but I’ve been stuck trying to retrieve the required data.

I’ve searched the documentation for info and the forums, but found limited information.

We are using the netflix_template slate-frame and this is what works and what doesn’t for us. What we can’t get to work just stays as the token.

  • f_submission_note - works, gets the comment from the publish window correctly (it’s empty here cause I forgot to put one)
  • f_submitting_for - should get the intent information, but not quite sure how to link it; tried multiple “tokens”, but couldn’t find any
  • f_vfx_scope_of_work - same as the above one, can’t find any usable tokens or a way to link the shot information, or description to this


Also, is there a way to also link the ‘shot name’ to the Ayon database? That would also be a nice thing to have. Maybe we can get more options in the ‘Key value mapping’ section in ‘Ayon settings’, or have an ability to add new fields ourselves.

Hi,

the f_submitting_for was used for netflix_template slate together with so called Intent. Intent was artist editable drop down list of options. Typically WIP | Creative Approval | Test. The purpose of Intent was low-friction communication of artist intention, regardless of the published version status (that can be edited later on). The Intent is not present in Ayon, and was not added to “new publisher gui”. Here is a Draft PR to actually remove it from the codebase.

Not sure if you are using Ftrack, here is the way to colllect the scope of work from custom Ftrack (shot) attribute.

Thanks!
Not using Ftrack, but Kitsu. Do you maybe know a way to get the same or similar attribute from it to Ayon? Doesn’t look like the custom attribute field exists in Kitsu settings.

Would love a complete list somewhere of attributes and tokens available to use in specific parts of Ayon

Sorry, I have no experiance with Kitsu.

I do fill the slate mostly by parsing the Nuke script name with TCL, something like

[join [lrange [split [file rootname [basename [value root.name]]] "_"] 0 5] "_"]

[if {[catch {[getenv FTRACK_API_USER]} result]} {return [getenv FTRACK_API_USER]} else {[getenv USERNAME]}]

[value root.first_frame]-[value root.last_frame]  ([value range_in]-[value range_out])  length: [value Length]

[date %d/%m/%Y]

There are couple of handy environment variables:
AYON_PROJECT_NAME, AYON_FOLDER_PATH

hth

Thank you very much!
Will look more into this.

Would be nice to be able to keep the intent feature :slight_smile: