Search the Community

Showing results for tags 'nuke'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Company news
    • General announcements
  • ftrack Studio (main app)
    • General discussion
    • Feature requests
    • API
    • Help
    • Actions and Widgets
    • ftrack Go
  • ftrack Review
    • General discussion
    • Feature requests
    • Help
  • Connect and plugins
    • General discussion
    • Connect package releases
    • Feature requests
    • Help
    • Connect plugins releases
  • Advisory Forum
  • Tech preview
    • API
    • New integrations
    • Studio overview
    • ftrack Review

Categories

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 4 results

  1. Hey there, I am in the process of evaluating ftrack and have some questions regarding publishing. Quite possible that I am missing anything as I am having some trouble understanding the basic principles in ftrack (coming from shotgun). I am gonna first outline what I think is the default render/publishing workflow. Gone through that in afx and nuke but I guess the workflow is similar in maya. Here the procedure in nuke: Open nuke via ftrack-connect (correct context). Nuke script is saved in an (more or less) arbitrary location. Do your work Render to another arbitrary location Attach a ftrackpublish node to the write node and publish (or is the intended way to use the publisher via the ftrack menu and the ftrackpublish-node is legacy?). During the publish the nuke-script as well as the rendered-sequence will be copied to the fileserver. - Script and image-sequence will be placed side by side into the following structure (given that the task was tied to a shot): project/sequence/shot/scriptname/version/ - The name of the script will be generic (nuke-script.nk or something like that) and thereby the version/shot/sequence will be not saved explicitly to the files but implicit in the ftrack database as well as the file structure. If theses assumptions are correct, here are some questions: is there any way to access/parse the ftrack-context in nuke? I'd rather like to use a custom write node which is automatically populated with the correct render-path (built from the task/shot/sequence etc.) on our fileserver. This is especially true for renderings running on the farm. I don't want the artists to manually navigate to the appropriate location and enter the correct filename as this is one task which should be handled by ftrack imo. the same applies to the script itself. I'd like to force the artist to save the script on our file-server (in the correct location and name) which is - as opposed to local files - backed regularly is the publish-action itself customizable? As the components (rendered sequence and script) already are in their appropriate locations on the fileserver there would be no need for any copying. Instead I'd like to only register the components and create the versions on the ftrack-server. Guess that this could be done with a custom publisher but I'd really like to let the built-in do the heavy lifting and just modify it I am quite sure that everything is possible. Just trying to figure out how much effort it takes. Best, Julian
  2. 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: https://bitbucket.org/ftrack/ftrack-connect-maya-publish https://bitbucket.org/ftrack/ftrack-connect-nuke-publish 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.
  3. Hi, we are using Photoshop combined to Ftrack trough the connect plugin in our production pipeline since a few weeks. It is great, so we would like to do the same with NukeX now. I have successfully set one of our workstation with NukeX and the connect package and can use the Ftrack plugin integrated in NukeX on this machine. However, I can't manage to reproduce this on any of or workstations. NukeX and the connect package are installed, I can launch NukeX from an action inside the web application or from the connect package itself, but I can't manage to see any ftrack related windows in NukeX on those machines. There are no ftrack related windows in the custom windows (see image attached below). I have tried to uninstall ftrack connect package and NukeX, then reinstalled them after a reboot, without any success. I'm running Windows 10 and ftrack connect package 0.5.4. So far I have tested NukeX 10.0v4 and 10.0v5. Am I missing something here?
  4. We have been doing some tracking in Nuke and have realized that there is not an option to publish this kind of asset. Maybe the Nuke Publishing system could be worked on as there are other Assets that are created at the beginning of a VFX project.