Robinson

Members
  • Content Count

    23
  • Joined

  • Last visited

  • Days Won

    2

Robinson last won the day on February 11

Robinson had the most liked content!

About Robinson

  • Rank
    Member

Contact Methods

  • Website URL
    http://www.cosavfx.com

Profile Information

  • Gender
    Male
  • Location
    North Hollywood, CA

Recent Profile Visitors

540 profile views
  1. Probably a big ask from a technical perspective but an incredibly useful feature in Review would be to wipe between two loaded versions in Ftrack Web Player. If wiping isn't possible, even a key press to quickly switch from version A to version B during playback would be helpful.
  2. Filters available in version view allow custom attributes on the version and on the Asset Parent, but not on the task from which the version was published. It would be great if custom attributes on tasks were an option in Filters on Version View.
  3. Is it possible to limit a custom attribute to a specific type of version IE a defined Asset Type? In our case we track each plate used in a composite and would like to include certain metadata on every frame sequence individually. We track these with a custom Asset type "Footage" I'd like to create attributes that would be relevant to these versions which are published directly to the associated shots, but irrelevant to versions published on task types. Is this possible in settings (I don't believe so) or with the API?
  4. Does there exist a detailed explanation of the logic behind Notes visibility by hierarchy and default notifications? This is what we observe: Notes appear to be generally revealed upwards in the Hierarchy. If "Notes" panel is viewed on a project all notes will be visible from every subordinate object. When viewed on a task, only notes input on that task are visible. Correspondingly, notifications appear to default to those users assigned to an object. This seems pretty straightforward. Notes that are entered on a version appear to propagate up through that task; every version associated with that task will share notes in the notes panel. Generally in our studio, versions are what receive notes. A version is associated with the parent task to which it is published, however Notes on the Task will not propagate downwards to the versions' note panel. Notification seems to only generate for users assigned to the task that published the version. This means that a version with other dependencies will not reveal notes to artists working on those other tasks. My questions are: - Are notifications generated for members of a team assigned to a parent shot or sequence when any activity occurs on subordinate objects? Ex. If Comp Team #2 is assigned to shot 001_001, then will every member of comp team #2 receive a notification for any note activity on any subordinate object of 001_001 by default? - Do task dependencies propagate notes from the dependent versions to other tasks in the pipeline or is there a way to achieve this through the API? Ex. 001_001_Final Comp v005 published to task "Compositing" receives notes that effect all the following tasks on the same shot "Tracking->Animation->Lighting->Compositing". Artists associated with all of those tasks need to see those notes. Is the only way to manually input them on each affected task? Notes on the shot level will not generate a notification or be visible on the tasks without navigating upwards. - Do asset Dependencies propagate notes from the dependent versions to tasks/assets used in the version? Ex. 001_001_Final Comp v007 published to task "Compositing" receives notes that affect the linked asset "Hero_Robot" containing associated tasks Modeling->Texture->Rigging. Will or can those notes be visible on the linked asset? - Are there any "baked in" exceptions to the rule that notes propagate upwards in the hierarchy?
  5. Just throwing my vote behind this here as well (and on Trello) Users assigned as managers receive so many notifications as to be almost worthless; the signal noise is too great. Filtering by custom attributes, task types, and even "subscribing" to notes on specific shots and sequences would be appreciated. -Andy
  6. Adding to this, there are a lot of areas where Phase, Team, and Tasks seem like they should correlate and do not: 1. If a project team is defined by adding groups in the project outliner, then all tasks assignee drop downs will be restricted to membership of those groups - This is currently true. However, if a group or subgroup is specifically assigned to a sequence or shot, the assignee drop down still queries every member of the team, regardless of group membership. It would be nice if task assignee drop down to be restricted by the specific group assigned to sequence or shot. 2. As mentioned in the opening post, it would be ideal to have groups in the phase drop down in the project tab of the planning page. 3. Another useful feature would be to have users and groups added to a phase on the planning page show up in the team for that project automatically if they aren't already, as they are being assigned to the project in both cases. 4. Related to the points above, if an artist is in a group that is assigned to a sequence, asset, or shot; that artist should only see subordinate tasks for that group assignment in the available tasks column of the Task Board. This could be an option on the phase allowing a Project Manager to define what tasks are visible to what groups by assignment and not just task type. Currently any task of the phase type will show up for any artist in the phase, regardless of group assignment. Functionally, what does assigning a group to a sequence or shot even do; as it doesn't seem to restrict or modify anything?
  7. It appears that users claiming tasks is a global setting only. I am trying to define a role that can see and claim available tasks, while limiting this for other roles. Is there a combination of role setting and this global setting that will be a functional work-around? Can it be defined by project? Specifically I'm hoping to create a team that can see all of the tasks on a sequence and self-assign from that pool of tasks ONLY.
  8. Hi Carl, Absolutely, putting this on the type would accomplish the same goal. While we are at it, the ability to name or label the overrides in the schema would also be useful i.e. "CG Override" "Admin Override" etc.
  9. It would be really useful if status overrides could be assigned to Versions based on their Asset Parent For example: CG workflow is very different than Comp workflow, and the former feeds into the latter; so we use different statuses on versions from each. ex. Modeling Task Version (On an asset) : Ready For Review -> Noted -> Lead Artist Check -> Ready For Comp -> Approved: For Final Final Comp Task Version (On a Shot) : Ready for Review -> Noted -> Lead Artist Check -> Approved: For Temp -> Approved: For Final -> Uploaded: Temp -> Uploaded: For Final -> Client Final -> Tech Noted -> Delivered Currently these statuses all live in the same drop-down and it would be cleaner and more intuitive if overrides could be built just like the task overrides. Thanks, Andy
  10. +1 We also find that dates for Shots would be a welcome addition.
  11. There are a couple of instances where it would be very useful to assign groups: 1. On the Planning Page, when creating Phases, assigning groups from the drop down. This would be a very useful way to streamline phase creation if a known group could be added I.E. "3D Team" 2. On the Team Calendar View when adding resources to view artist workload and assign tasks Currently each artist must be added individually to see availability and start assigning them tasks.
  12. This is something that occurs across all export types. Currently our fix is to export as CSV and use excel FIND and REPLACE command to strip out unwanted prepended text in one step. Relatively simple to do since the extra text inherited always starts with the Project name and you can just add wildcards to the search after that. Of course, Excel is not as pretty as the PDF output from Ftrack. It would be nice to have an option to choose what appears in the export. ------ From the example: "PROJECT NAME" / 010 (cameron) / 001 Select the column in Excel and Find: "PROJECT NAME" / **************** Replace all, leave replace text blank This solves your problem at the shot level, the task will now read "001 / REMOVE WIRES" which will at least be somewhat easier to digest.
  13. Since this post received so many views and no replies, I imagine other users were interested in some best practice ideas. Here's what we're doing at the moment (primarily dealing with episodic television): 1. On episode creation "Episode Due Date" is set to the likely final submission based on air dates and previous deliveries for the particular client. 2. All shots are imported from a spreadsheet and assigned a "Composite" task template which assigns a single compositing task to every shot. Regardless of complexity, every shot eventually goes to comp as the last step. 3. From the "Tasks" spreadsheet view select all tasks in the show (currently only compositing tasks) and assign a due date based on the final delivery. You will need to display the "due date" task attribute in your spreadsheet to do this. 4. From the "Shots" spreadsheet view click in the calendar next to "Shots" at the very top of the spreadsheet, drag to the current delivery date to schedule all shots for the duration of the project. 5. Other tasks can be added at this point and scheduled on a per task basis as the already scheduled compositing task will always fall last in dependancies. While imperfect, this approach gets the broad strokes information into Ftrack and allows tweaking down the line as necessary. Given the relatively quick turnaround, production can't devote too much time to micro managing artist schedules but this allows supes to get an idea at a glance what's going on in house and also shows artists (particularly 2D) when their shots are due so they can bug anyone further up the chain for elements they are missing if something slips through the cracks. If you've got suggestions/solutions I'd love to hear them!
  14. Milan, This works! In fact, if you create a permanent group that include all artists but excludes inactive accounts, production accounts, etc you can just assign it as the Team for each project as it is created. This way, if new users are added later you can update all projects simultaneously by updating the single global group in System Settings.
  15. That would probably work. Or having it as a role trait that determines if a user will appear in drop downs globally. Anything that allows the user to exclude production assistants, EPs, and the like who probably won't be assigned roto anytime soon. We're definitely getting Inactive users in the assignee drop downs though, the only way to reliably get rid of the name is to delete the account entirely.