Skip to content
This repository has been archived by the owner on Sep 20, 2024. It is now read-only.

Nuke: removing redundant Ftrack asset when farm publishing #2996

Conversation

jakubjezek001
Copy link
Member

@jakubjezek001 jakubjezek001 commented Apr 1, 2022

Brief description

No need to publish sequence with review if baked profiles are used.

Description

This was happenning due wild card regex match but since we are adding bakingNukeScripts atribute to instance data, it is quite clear we don't need to review also .exr image sequence.

Additional info

We had also not very nice way of Ftrack asset naming in case multiple reviewable representations were processed. I had hopefully preserved backward compatibility for single reviewable, but it needs to be tested. The feature was made optional and can be activated in settings project_settings/ftrack/publish/IntegrateFtrackInstance/nicer_asset_name

Testing notes:

Ideal test scenarios are following:

  • activate project_settings/ftrack/publish/IntegrateFtrackInstance/nicer_asset_name on your project
  • nuke single baking preset - ftrack component asset name should be in old way (subset name)
  • nuke multiple baking presets - asset name should be in new way (each component {subset}_{repre.name})
    image

Todo:

  • I have noticed we are also generating correct thumbnails for each reviewable, but those are not used anywhere. Anyway IntegrateFttrackInstances is not supporting multiple Thumbnails so this could be also improved.
    image
    Problem is that each of the representations (noLut, withLut) is having differently looking image and this will be great to display as thumbnail.

@jakubjezek001 jakubjezek001 self-assigned this Apr 1, 2022
@ynbot
Copy link
Contributor

ynbot commented Apr 1, 2022

@jakubjezek001 jakubjezek001 merged commit e3ceaa7 into develop Apr 4, 2022
@mkolar mkolar added this to the 3.9.3 milestone Apr 8, 2022
@mkolar mkolar deleted the bugfix/OP-2988_Nuke-redundant-review-repre-when-farm-publishing branch May 30, 2022 08:05
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants