Erik

Members
  • Content count

    27
  • Joined

  • Last visited

  • Days Won

    3

Erik last won the day on October 19

Erik had the most liked content!

About Erik

  • Rank
    Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

418 profile views
  1. Working with Tags

    I'm digging up this old thread as well. We are making a new asset library and wanna tag versions with things like maya,maya_2017,vray,vray_3.5,character,fur,projectname and then be able to do a reasonably fast query against this through the API. Would modifying a custom enum attribute and add more values as we go along still be the best or only option? Feels like that attribute would get pretty crazy pretty quickly.
  2. Incoming links

    Chiming in on linking Asset to TypedContext (Sequence/Shot/Task/etc). Would be really useful.
  3. link attribute contains full_name of project

    We use it as a indicator of where in the tree structure you are at the moment like. '.'.join([foo.get('name') for foo in bar.get('link')]) gives for example Project.sequence.shot.task With the old api we do it in a recursive function using getParent and the end result is project.sequence.shot.task This is for a project where the Project name is Project and the Project code is project
  4. When getting the link attribute of for example a task it contains the full name of the project. I think in most cases it would make more sense to include the name aka project code instead. And if replacing it is not an option please include both. Like this we have to do an additional query just to get the project code.
  5. More control for custom attribute type number

    Adding to the define how many decimals club. Biggest problem at the moment being for example FPS. It can be 23.976 in a lot of places and I guess I could put it as text but then I have to do unit conversions everywhere which is not very elegant.
  6. It would be good to be able to do X amount of users without specifying the exact users. For example we know we will need 5 FX people on project X between dates Y and Z. This could be used to estimate license usage and renderfarm load earlier in the process than when there actually is decided who is going to work on it.
  7. Sharing Dashboards

    So we can save Dashboards http://ftrack.rtd.ftrack.com/en/stable/using/studio_overview/studio_overview.html#studio-overview-using-dashboards But how can they be shared between Users?
  8. Slack User Group

    Seems it works in the webbrowser but not the standalone application. Strange
  9. Slack User Group

    Stopped working today?
  10. With this setup it would be nice if Default role in settings could have more settings. Ideally it should have all the options you have when you assign roles to a user making it more of a "Default roles" setup. Currently all users here have "Restricted User", "User" (three different projects for time reporting), "AssignedCustom" (All projects, workaround from this thread)
  11. Going to try Lucas solution but don't like it. That a user with ASSIGNED role can not see the custom attributes on the shot that he is allowed to see don't make sense in my head.
  12. PDF / Excel Export

    I wan't bigger thumbnails in the pdf as well And ideally also thumbnails in the excel file
  13. Slack User Group

    Would not mind an invite. erik@goodbyekansas.se
  14. quality levels for review

    Does this work good nowadays? We had lots of issues with banding in resulting files when using lutrgb some year ago.
  15. Upload media to local ftrack server

    baseAttachmentUrl = '/attachment/getAttachment?attachmentid={0}'attachment = assetVersion.createAttachment(outfilemp4)mp4Component = assetVersion.createComponent(name='ftrackreview-mp4', path=baseAttachmentUrl.format(attachment.getId()))mp4Component.setMeta(key='ftr_meta', value=metaData)metaData = meta data as described in documentation outfilemp4 = path to correctly encoded mp4 as in documentation this works for us //e