New publish tools
3 3

15 posts in this topic

Hey everyone!

For a while now we have been working on improved / refreshed integrations in Nuke and Maya. We’re now happy to announce the first technical preview of these tools.

First out is revamped publishing tools in Nuke and Maya. At the moment we will have a limited set of workflows:

Maya: Geometry, Scene and Camera
Nuke: Image sequence/Render,  Camera

Today we will be releasing the Maya publish tool as version 0.1.0. At the moment there are several limitations of the publish tool and it should be seen as a preview of what is coming. Neither design, nor features represents what will be in the final version. Again, this is a technical preview and is not production ready.

The installation process is also rather technical and requires knowledge terminal, python and git. Installation instructions can be found here:

First draft of the documentation can be found here: http://ftrack-connect-documentation.rtd.ftrack.com/en/stable/index.html

We are very interested in your feedback! Especially in regards to general workflow; selecting a "publish action", multi-select items to publish, et.c. But also from a developer/TD perspective. What more requirements do you have to make it easier for you to hook in extend/enhance these tools.

Edited by Mattias Lagergren
Added nuke repository

Share this post


Link to post
Share on other sites

New versions release Nuke and Maya: 0.2.0

They contain various fixes and Thumbnail + Attaching scene as reference features from ftrack-connect-pipeline 0.3.0 

Pyblish plugins are now centralised in the ftrack-connect-pipeline repository. 

Remember to install the new dependencies if you want to update them

Screenshot at Nov 29 16-05-11.png

Note that we're still concentrating on features and this is not the final design.

Share this post


Link to post
Share on other sites

Hi everyone, new updates are available for nuke and maya: http://ftrack-connect-documentation.rtd.ftrack.com/en/stable/index.html

It is now possible to download the plugins and install them without having to know a lot about git, terminal and python. See the installation instructions here:

 

nuke_publish_image_sequence.png

Share this post


Link to post
Share on other sites

New version 0.4.0 is out for both Nuke and Maya, with support for adding a web reviewable when publishing:

  • Nuke: select a write node to generate a web playable video from.
  • Maya: select a camera to create a playblast to generate a web playable video from.

See the installation instructions here:

 

Publish with reviewable.png

Share this post


Link to post
Share on other sites

Hi @sridharank, I'm glad to see that you're trying out the new integrations. For the error; you need to either setup your own custom location or configure a centralised storage scenario: http://ftrack.rtd.ftrack.com/en/stable/administering/configure_storage_scenario.html

Share this post


Link to post
Share on other sites

Hi, this Publisher variant looks more friendly.  But it provides so many options...

In our pipeline we firmly defined which output types would be published from particular task type (Scene+Geometry from Modeling, Scene+Rig from Rigging, etc.).  We run our validation before publish dialog would appear, and require predefined nodes with particular name (camera) to be in scene and many other things. And all options are also hidden and set to defined values.

All we need is description, thumbnail and friendly designed ui. So would this publisher to be setup this way from any outer facility?

Share this post


Link to post
Share on other sites
Quote

 

Hi, this Publisher variant looks more friendly.  But it provides so many options...

In our pipeline we firmly defined which output types would be published from particular task type (Scene+Geometry from Modeling, Scene+Rig from Rigging, etc.).  We run our validation before publish dialog would appear, and require predefined nodes with particular name (camera) to be in scene and many other things. And all options are also hidden and set to defined values.

All we need is description, thumbnail and friendly designed ui. So would this publisher to be setup this way from any outer facility?

 

Hi Konstantin, thank you for the feedback. The goal is to make the new tools/publisher more configurable than before. 

I see it as we have to support three different levels:

  • Customers running Connect and integrations out of the box with a minimum.
  • More advanced customers should be able to hook in and modify the behaviour, hide advanced options or add others (should support your use-case).
  • Customers that want to build their own integration could fork or use our tools/UI components as building blocks.

Share this post


Link to post
Share on other sites
1 hour ago, Mattias Lagergren said:

Hi Konstantin, thank you for the feedback. The goal is to make the new tools/publisher more configurable than before. 

I see it as we have to support three different levels:

  • Customers running Connect and integrations out of the box with a minimum.
  • More advanced customers should be able to hook in and modify the behaviour, hide advanced options or add others (should support your use-case).
  • Customers that want to build their own integration could fork or use our tools/UI components as building blocks.

Great! So i see it here http://ftrack-connect-documentation.rtd.ftrack.com/en/stable/developing/publish_using_pyblish.html?highlight=pyblish . I have to try.

But the way i m not happy with Pyblish validators, our own validator return very complex data including callable python objects that would fix particular issue in different ways and use of exceptions will bring undesired performance penalty.

Share this post


Link to post
Share on other sites

New version 0.5.0 is out for both Nuke and Maya,:

  • Support for changing context globally. At the moment it only affects the new tools.
  • Maya: New light asset from Maya.
  • Nuke: Renamed Media asset to Render in Nuke (publishes write nodes)
  • Nuke: Validate reviewable before publish
  • Nuke: Improved validation that all files in an image sequence exists before publish.

See the installation instructions here:

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
3 3