Jump to content

Search the Community

Showing results for tags 'tasks'.

  • 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. We're still refining our ftrack implementation and constantly trying to improve the pipeline. I'm curious how some of you are handling various steps in the process. Now, I generally have one, maybe two tasks per shot. Our VFX is usually pretty simple so Compositing and occasionally Rotoscoping is what we have been using. I track some of the steps of our process for tasks and shots with statuses. I'm curious to know when you decide to make a task for some to-do item on a shot versus keep it in the status? My shot statuses are: Not Started In Progress (when the artist begins work) Pending Review (when the artist submits a shot for review) Client Approved (when the shot gets approved by the director) Completed (when the shot is rendered) Delivered (when shot is uploaded to the server for the colorist) But, I wonder if we'd be better served by making tasks for things like generating the shot file for the artist, QC, final delivery, etc...?
  2. Hey Guys, We've had it come up multiple times where we have needed an attribute from a parent to be available for the child. Here are some examples: Shot seconds, or complexity information be available for Tasks lines Bid days, worked days, +/- days available for Versions lines and views. Just being able to access the parent information for any asset/shot from any view would be SUPER helpful. Thank you, Ozen
  3. ftrack provides in the version view to change the status of the version and of the related task. By changing the status of the version ftrack is saving the new status By changing the ststus in the same view of the task status, ftrack is first saving it and then re switching to the old status. In the Activities of the task the last activity is the change of the status, but there is no info from ftrack that he change the status back. e.g. I have on activities the new status changed to "Client Approved" and the status still (again) on "Sent to client"
×
×
  • Create New...