jonathan-v

Members
  • Content Count

    28
  • Joined

  • Last visited

  • Days Won

    9

jonathan-v last won the day on June 9 2014

jonathan-v had the most liked content!

About jonathan-v

  • Rank
    Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

460 profile views
  1. jonathan-v

    Old Actions

    Excellent! Thanks for the help. We we're actually using the old way with the topics function and found that it was deprecated which is why we we're hitting a brick wall. This is working much better, but definitely look into the old pop up dialog, as we find it is much faster to execute an action. Thanks again for your help.
  2. jonathan-v

    Old Actions

    Lately we have been digging deep into ftrack connect and the new actions implementation. We are finding that we don't like actions being so tightly connected to "connect". It's quite cumbersome to get working correctly and really doesn't fit into our workflow. I would love to just run an action without having connect running. There are some instances where it's not even possible for us to run connect thus not allowing us to use actions at all. We miss being able to run one listener from a server that activates all of our actions. This even leaves us with the flexibility of writing a custom user listener that fits our facility. As well as, managing permissions on who can run what action. In addition I miss the one click functionality of an action. Rather than launching a menu, finding the action and then executing. Just an unnecessary extra step. Is there any way to continue with the development of connect, but still allow for the old actions implementation? Actions really were what I found to be the most powerful aspect of ftrack and not being able to take advantage of that has been sad. Really appreciate the help, Jonathan
  3. Hello, I was wondering if there was a way to allocate certain users to a job, thereby giving them access to the job but restricting seeing all other users. For instance, at the start of a job I want to assign users to the job to access it rather than a specific task. This let's me assign leads first so that they may setup tasks for themselves and other artists. At the same time this would limit all the other hundred users from showing up in task assignment drop downs. I guess simply put I want to just add a list of users to a job that are booked only to that job and task from there. Thanks, JV
  4. This is a huge improvement!!! As mentioned above assets with 36 components used to take upwards to 8-9 seconds and we are now seeing the same asset returning in 0.6 seconds. Really appreciate the effort to get this optimized quickly. Thank you so much, JV
  5. As I mentioned before thanks to the "simple" cell formatting it has reduced places where this is a major issue. The following are where we hear the most artist/sup complaints. Basically it's just a way for people to see seq/shot at a glance and avoid diving into assets. Sorry for the horrible mock ups. Tasks Spreadsheet: Currently in simple formatting it strips to just the task. We were thinking it just strips the job(as it is really large). Ex: /seq/shot/taskName Version Thumbnails: The version link is usually not helpful with our link and people aren't fans of tool tips. Wondering if they could have shot/seq attributes? Or similar to the above where the version link doesn't have the job in it. Ex: App Launcher: Love the app launcher just have a hard time seeing tasks within it. Ex: Thanks JV
  6. Just wondering if this had ever been added and I am not seeing it? We are hearing more and more complaints about the full job name being included everywhere. It really is our fault for having the most ridiculously long job names ever, but having the option to just show the relative path would be a life saver. I would assume this would travel through to the app launcher as well? Seems that and versions is where people get hit the hardest. At least in the spreadsheet view we can set cell formatting to simple which helps tremendously. Just wondering if there is something similar globally. Thanks again!! JV
  7. We look forward to seeing what you develop on your end, but did manage to get a working solution for now. We were ideally thinking of a listener that is opened when triggered through the ftrack interface and closed after the program has been ran. Though that might be tricky? Thanks for your help.
  8. Hello, We've been using actions quite a bit, and love them. Is there a way to have a user end listener? For instance we would like to have an action that could make an edit of all the published dailies and open rv on the users machine. Another example is we want to use ftrack as a 3D repository interface. Say we have a cool animation in our ftrack archive job, there would be an action to check that out to a user defined job. As well as checking it back in at the end of a job. This would be very useful. I believe there is probably a way, but I'm not sure how to go about it. Thanks! JV
  9. Hello, For the most part we really love the asset management api. However, we are finding with large amount of assets(with multiple components) calling getComponents is proving to be crazy slow. For instance we have a render asset with 36 aov components. When we debug we notice it makes 248 calls to the server which seems unnecessary. We noticed this really only happens with getComponents. Ideally it would work similarly to getAssets which makes one call and returns the FTlist or maybe a dictionary. If there is possibly a better work around for this that we are missing would love to know your thoughts. Thanks JV
  10. Thanks! We are currently implementing method number 2, and are skeptical of giving the user the option to select dependencies upon asset publish. I think exploring the following feature is definitely the best solution for this scenario. Notifications are often a tough thing to manage and tend to just become overwhelming. Users are mainly only concerned with things that directly affect what they are working on. So giving them the option to follow certain assets is a great idea. That is probably the most important thing that we see is being able to follow an asset vs a task. The task could consist of multiple assets that are of no use to other disciplines. So users could follow assets as they version up, and maybe these even appear in their notifications with a different color coated background. Just something to visually help differentiate from everything else. Thanks again for your help
  11. Hello, We are getting a lot of feedback from users regarding notifications that don't directly relate to their tasks. I was wondering if there was a way where the user could "watch or follow" just certain assets that pertain to their needs. Or is there a way to setup task dependencies similar to asset dependencies? For example an fx artist is working on some type of character fx. Their feed should really only update them on latest anim cache, camera, and layout geo. Whereas now, they receive information on anything pertaining to the shot, which can be a ton of asset versions. Ideally their would be a smart dependency that is aware of their task and notify the user of only things that they have selected or part of a task dependency package. Not sure if this makes sense, but would love your thoughts on it. Thanks, JV
  12. This indeed sounds great. As we dig deeper into actions we are seeing a great deal of potential. One other thing I would like to suggest is custom actions linked within user roles. For instance only our restricted project managers should be able to generate asset build directories or something else we may want to lock down to specific people. Thanks, JV
  13. Hello Milan, We do all of our FX in Houdini and wanted to integrate ftrack as well. We used the Maya and Nuke plugins as a template but built a full Houdini integration from scratch. The whole toolset took about 3 days to build, couple of days of test dev and into production within a week. This includes an importer, asset manager, and custom pane that connects directly to the web interface. This dashboard allows users to quickly access information of an asset/task directly inside of Houdini. We found it to be more stable than the QT webview. In addition we made custom import nodes that were tagged manageable via the assetManager, and output rops to publish assets. We found no hangups/restrictions with the API, and actually feel setting applications up with ftrack is quite straight forward and painless. Not very helpful, but thought I would share our experience. JV
  14. Ahh I see. This is kind of a hacky work around, but does work as a short term solution for our situation. It is good to hear that there is a discussion on permission management because in it's current state it is confusing, and requires a lot of manual changes per user. We had other issues regarding managing permissions as I mentioned in this post: http://forum.ftrack.com/index.php?/topic/106-flexiblity-with-role-settings/ I really think just allowing the ASSIGNED type to have the same selectable permissions/custom attribs as the other types would be a great first step in the right direction. Appreciate your help! Thanks, JV
  15. Hello, We are experiencing an odd issue with our restricted user settings. Even though we have custom attributes selected as accessible they never seem to show up in the info section. For instance all of our users are of ASSIGNED type and cannot access work in, work out attribs on the shot. When switching the user back to a regular user that accesses all jobs the custom attributes work as expected. Any thoughts on this oddity are greatly appreciated. Thanks JV