Jump to content

Milan Kolar

Members
  • Content Count

    81
  • Joined

  • Last visited

  • Days Won

    14

Posts posted by Milan Kolar

  1. Hi guys.

     

    I have an idea that might make navigating and sorting through the ftrack interface a bit easier.

     

    The problem is that when there are too many sequences, shots, tasks in the project it become difficult to micro manage everything. Especially priorities and due dates. We won't have time to be putting dates and priorities on every task, however it's nice to have them as it makes organizing views, tasks and work in general easier. 

     

    So I'm thinking whether it would be possible to implement some kind of top-down inheritance as an override on on certain task attributes. I'll use priority as example, but the same could apply to dates. 

     

    If we had a project like this.

    Seq01          | PR none-shot001       | PR High--animation    | PR none  --lighting     | PR medium--compositing  | PR lowSeq02          | PR Urgent-shot003       | PR medium--animation    | PR none  --lighting     | PR medium--compositing  | PR none-shot004       | PR low--animation    | PR none  --lighting     | PR medium--compositing  | PR low

     Then any sorting algorithms could simply go through hierarchy and sort by it. If task doesn't have it's own priority - use it's shot priority, if that doesn't exist, use sequence and only then assume there is no priority set on the task. If 2 tasks have the same priority, but their shots don't, the one with higher priority shot should be higher in sorting. 

     

    I'm going by the fact, that I've very rarely seen tasks needing to be prioritized, however we always get into rush to get shots or sequences out of the door. This way if a situation arrives, I could just set sequence to high, priority and everyones tasks would reorder to keep this sequence tasks on the top (they could keep shot prioritization within that of course)

     

    Yes we are talking about pretty much 3 levels sorting would need to go through, but the result would be much better representation of what needs to be done and when.

     

    Similar situation could be with sorting by date. If task is scheduled to end on 15.march, but it's shot is for 10.march, there's clearly been either human error or something is not right (I know you can't set dates on shots and sequences now, but is would sure be nice)

     

     

  2. Hey guys.

     

    I'll bump this a little bit and add to it.

     

    We're really trying our best to use 'my tasks' view but currently it's missing a few crucial pieces for us.

     

    1. Sorting by name, hierarchy exactly as Tilt wrote. Without this is becomes a big pile of mess and we can't find anything. This should be like a second layer of sorting on top of every single sorting type. So if I sort by priority, each priority category should be sorted by hierarchical name so if I have 30 medium priority shots, I can find ep100/sc02/sh0145 immediately. Same goes for sort by parent, this one is almost useful apart from (as Tilt said) the dividers between tasks. So to sum this one up: Nice solution would be either this name sorting to be applied on top of everything, or introducing a secondary sorting, so I could choose to sort by project and then priority. this would make it very clear to look at.

     

    2. We are not assigning tasks to people directly but rather let them pick from the list of available one. The problem right now is that not every unassigned task should be available. We use 2 statuses to deal with this. 'Not started' mean it's simply not ready, because the previous pipeline step wasn't completed (layout not done for animation for instance), however when layout artist finishes his job, he set's animation task to 'ready to start'. Animators are then assigning themselves to these tasks because they know, layout has been done and they can take it. This prevents too much micromanaging and is very easy to understand. Now, I'd like to be able to tell ftrack to only show tasks of certain status in the 'available tasks' column.

     

    right now for all task handling people have to use customized spreadsheet views, because there's too much stuff in 'my tasks'. So I have to ask the obvious: Is this anywhere near to being implemented? I'm sure there must be more people asking for this.

  3. To add to this one. I'd say that most of the 'types' things in ftrack should have a short name or 'code' field by which we could refer to it in the API.

     

    Usecase for task status codes:

    I have a daemon running that is responsible for changing statuses on task depending on what's happening with their versions. When i want to set a status using API I have to do something like this

    status = version.getStatus()project = version.getParents()[-1]statuses = project.getTaskStatuses()task = version.getTask()if status.getName() == 'Approved':    task.setStatus(statuses[3])

    Now I know that status 3 of this particular project is 'Complete', however this might not be true on another project, where we only have 3 task statuses in the schema. Hence it's really difficult to make things like this work across the board.

     

    What I'd like to be doing is

    status = version.getStatus()task = version.getTask()if status.getCode() == 'appr'   #or 'approved' or 'i like kittens' or whatever I set this status code to be in ftrack settings    task.setStatus('cmpl')      # or 'complete' or ... you get the gist. 

    Pretty much the same as idea as being able to refer to a project by it's code when retrieving it by ftrack.getProject(code), but inverse.

     

    Usecase for Task codes:

    Mostly for creating folder structures. If we have a task type called motion graphics, I'd like it to be represented also as mograph, so I could get this code and use it as a folder name upon its generation. No I need to have a small dictionary containing task types and their corresponding short names, which is just a little annoying.

     

    And as we are reaching for the sky already, it would be awesome if columns in spreadsheet view could change it's display from full name to this short code when scaled too small for full name to fit. We could get a lot of columns on the spreadsheet that way without really sacrificing readability.

     

     

    Sooo to finish this up, how is this looking as far as implementation goes? :)

  4. Actually I just found out, that this works to a certain degree.

     

    You need to use the team menu in the sidebar. When you leave it empty, then you see all the people in dropdowns. But if you choose a team for give project, You'll limit the dropdown menus to only selected users. In the attached screenshot, only I would appear in any user lists across the project.

     

    Mattias: I can however confirm, that making a person inactive, doesn't remove him from the user lists. (which I personally like. )

     

     

    team.PNG

  5. Strangely I'm having quite the opposite issues. When I add new inactive users (so I can plan production a few weeks and months ahead) I can't see them anywhere. Let's say I have a project starting in a months, I know I'll need to recruit 3 more people just for this project. I'd like to be able to plan this with dummy inactive accounts. Ideal solution here might be that they show up in studio planning tab so I can assign them to phases and see how many people I'll need at certain times. This would technically work as a kind of database for freelancers. I could plan ahead, and activate their accounts for 1-3 months when needed.

  6. Hi guys.

     

    Has anyone tried turning the hiero integraton into nuke studio? I didn't have time to get into it yet, but I'm assuming it should be fairly straight forward looking at the similarities between the two.

     

    Cheers.

     

    Milan

  7. I agree that some options of version handling would be handy. The trouble is that different studios might have very different version naming convention and systems so figuring out something that would work across the board would be challenging. On the other hand, I was developing on a production recently where current default version handling was actually requested because they specifically wanted to have ftrack versions for review separated from file versioning.

     

    Ftrack in vanilla state is currently very opened system and quite frankly needs a developer to make full use of it (as does shotgun I'd say). I'm hoping things will get simpler with future updates.

  8. Hey.

     

    First of all, client reviews look great and really foolproof, however there are couple of things we'd really appreciate. 

     

    1. Possibility for client to display a 'thumbnail view' of all the items. Pretty much what it looks like when managing client reviews. When you click on a thumbnail, it opens overlay with big version and comments for it.

     

    2. Scrolling in the list of items. Currently if we put 15-20 items in the list, there is no way to get to the last one without clicking through them. (There often situations where client doesn't have time to go through everything, but we need one particular item from the list approved asap, so we'd like him to be able to quickly scroll and find the right one)

     

    3. Name of the item on the items that are not highlighted (doesn't need task and version, just shot or asset) . Again so it's easier to find specific thing.

     

    4. Way to make reviews read only.

     

    Use case: Client wants to have access to previous review sessions for reference or whatever reason. However we'd like to be able to lock the comments and approval status of already processed list, so he's not tempted to add extra details or comments on approved shots.

     

    Use case 2: Client review would be perfect tool to present progress on a project in a quick way to, let's say investor, or simply someone who shouldn't be able to comment at all. If we could create a client review without the possibility of actually reviewing, it would expand the usage of this tool tremendously.

  9. I think this will be very welcome change and the proposed solution looks very good to me.

     

    One thing to point out is that currently folders for asset types in the outliner are not 'clickable', which means that If I want to see for instance only characters, I have to create custom filter for it. Episodes and sequences work as they should so adding this behavior to assets would be greatly appreciated. 

  10. Having messages, notes, newly assigned task... or pretty much anything (preferably customisable) make a small pop up notification on the desktop when they are sent or assigned would be very useful. The problem is that people might forget to check their messages, but if they get a tiny pop up it will at the very least remind them to go a check what's going on.

     

    Something like this for instance https://support.google.com/chrome/answer/3220216?hl=en-GB

     

    I'm not sure how easy is something like this to implement in other browsers, but Chrome seems to have built in way of doing it.

     

    I can imagine this appearing, when artist, get's a personal message (e.g. of certain category) or is assigned an urgent priority task and so on.  

  11. It would be great if we could customise types of upload in the launcher uploader. Currently there are only 4 options (img sequence, geometry, maya scene and nuke script), however if we could extend this to custom values, it would make it straight away possible to use ftrack with much wider range of workflows and software even before they are properly integrated.

     

    Example1:

    In current production we are using CelAction, which doesn't even have python, but giving artists option to publish manually through launcher by choosing CelAction scene and let's say quicktime movie, would make it possible for us to work straight away and all the data would be be consistent with other ftrack published assets.

     

    Example2:

    Production I'll be starting in couple of months will be using houdini. We're planning to fully integrate the ftrack into it, but until that point this type of publishing would ensure that any data input before we have it ready will be published properly as well.

     

    To wrap it up: We should be able to specify upload types that appear in launcher, plus adding a default type with would accept any type of data (even if it doesn't know what to do with it per se, it would at least track it's location)

     

    To be honest the whole publishing of 'assets' and version could be a tiny bit more open. For instance ability to add components in the web interface, or to create a version without uploading it online, but only linking to local file would be brilliant.

     

     

    Milan

×
×
  • Create New...