Jump to content

Robinson

Members
  • Content Count

    25
  • Joined

  • Last visited

  • Days Won

    2

Robinson last won the day on February 11 2019

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

820 profile views
  1. Interesting, It doesn't appear to correlate- is it possibly only notes directly entered to the task but not including on objects published to the task? In our workflow the discrete objects (versions) receive the notes so that would explain why we don't typically get the numbers.
  2. Hey All, Question about the My Tasks Kanban board. Infrequently, some task cards appear with a small number in a circle in the upper right corner, typically "1." I remember looking this up a few years ago, but can't for the life of me remember or find the answer in the new documentation. It doesn't appear to relate to new notes or versions.
  3. 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.
  4. 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.
  5. 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?
  6. 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;
  7. 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
  8. 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
  9. 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.
  10. 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.
  11. 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 -&
  12. +1 We also find that dates for Shots would be a welcome addition.
  13. 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.
  14. 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" / *****
  15. 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 "Ta
×
×
  • Create New...