Jump to content

Search the Community

Showing results for tags 'publishing'.

  • 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 Integrations
    • Releases
    • General discussion
    • Feature requests
    • Early Access Integrations & Connect
    • Help
  • Advisory Forum
  • Tech preview
    • API

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


Website URL


Location


Interests

Found 3 results

  1. Hi there, I recently switched away from Ftrack to Shotgun because the publishing tools seems so broken and limited in Ftrack. Shotgun does it much better, but the program as a whole is terrible and a pain to use. Ftrack is far superior when it comes to ease of use - with the excepting of publishing. I quickly switched back to Ftrack and now have to figure out a solution to my issue. Both programs seem to have terrible documentation and I can't figure this out. We have a small studio and I am a VFX supervisor. We have a pipeline that works perfectly for a studio our size and I don't want to mess around with it too much. My issue is that Ftrack seems to be be very rigid when it comes to publishing files. It wants to create it's own file structure which in my opinion is a complete disaster. I'm really not sure how anyone works this way. I want the artists to be able to submit shots for review that retain the naming convention of the shot they submitted, and retain the path on our server to the shot. I want to open a group of shots submitted throughout the day in RV - launched from Ftrack and review, annotate and make notes from within RV (on the original shots) that then get transferred to the shot tasks for the artist to see. Pretty straightforward. What I don't want is for Ftrack to copy the shot to some other location on my server, place it in a folder within a folder within a folder within a folder within a folder and rename the file "movie.mov". Before I ask how I can do this, I'm just wondering if someone can just give me a straight up answer if this is even possible. We've spent days trying to solve this. There are very few but broad and unhelpful documents about publishing, but otherwise the internet seems to be devoid of any useful help on this issue. Thank you so much for your help! cheers, Mike Ritchie
  2. In the Description field, in the info tab of the assetversion published, just the last line of the artist's comment is showing up This is what was submitted by the artist as comment
  3. 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
×
×
  • Create New...