Eric Hermelin

Members
  • Content Count

    46
  • Joined

  • Last visited

  • Days Won

    7

Reputation Activity

  1. Thanks
    Eric Hermelin got a reaction from Tim Edelmann in Access custom_attributes' labels   
    Hi Tim,
    you can reach the custom attribute configuration like this
     
    project = session.query( 'select custom_attributes.configuration.label from Project' ).first() for custom_attribute in project.get('custom_attributes').collection: logging.info( custom_attribute.get('configuration').get('label') )  
    cheers
    Eric
  2. Like
    Eric Hermelin got a reaction from Luigi in Exporting Links   
    Hi Ozen, hope you are well!
    It is possible to using a advanced query filter to filter on linked entities, below are a few examples, it is however a bit fiddly to update these query filters if you wish to iterate over a few different shots / asset builds, so it might be worth writing a tool using the api to export the information in bulk
    Using a Shot Query filter, show only shots that have a incoming link to a asset builds named "Monkey"
    incoming_links.from.name = 'Monkey' Using a Asset Build Query filter, display all asset builds used for a specific shot
    outgoing_links.to.name = 'SHOT_NAME'  
    cheers
    Eric
     
  3. Like
    Eric Hermelin reacted to Ozen in Exporting Links   
    Asset one works great!  Shot one just needed a small change to make it work for a full shot number:
    For Shot 140/0105
    outgoing_links.to.name = '0105' and outgoing_links.to.parent.name = '140'
  4. Like
    Eric Hermelin got a reaction from Ozen in Exporting Links   
    Hi Ozen, hope you are well!
    It is possible to using a advanced query filter to filter on linked entities, below are a few examples, it is however a bit fiddly to update these query filters if you wish to iterate over a few different shots / asset builds, so it might be worth writing a tool using the api to export the information in bulk
    Using a Shot Query filter, show only shots that have a incoming link to a asset builds named "Monkey"
    incoming_links.from.name = 'Monkey' Using a Asset Build Query filter, display all asset builds used for a specific shot
    outgoing_links.to.name = 'SHOT_NAME'  
    cheers
    Eric
     
  5. Like
    Eric Hermelin got a reaction from sultanbal in Get AssetBuildTypes using new ftrack api   
    Hi,
     
    you can get the asset types for a project / project schema like this
     
    session = ftrack_api.Session() project = session.query( 'Project where name is "<ProjectName>"' ).first() types = project.get('project_schema').get_types('AssetBuild')  
    cheers
    Eric
     
  6. Like
    Eric Hermelin got a reaction from Mattias Lagergren in ftrack connect version 0.6.2   
    Hi,
    We have just released a new version of ftrack-connect 0.6.2 (https://www.ftrack.com/portfolio/connect). This is a major release as all ftrack connect plugins have been updated to no longer use our legacy API and instead use the new API. This change will improve performance across the board, as well as lead to a quicker development cycle. In addition, we are including our new Beta plugins for Maya and Nuke built around the open source project, Pyblish (http://ftrack-connect-documentation.rtd.ftrack.com/en/0.1.12/).

    Backwards compatibility with the old location plugins and actions are achieved through the ftrack-location-compatibility plugin (https://bitbucket.org/ftrack/ftrack-location-compatibility). While old locations and actions will continue to function, we highly recommend that you start looking at migrating your plugins and locations, please have a look at the migration documentation for more information (http://ftrack-connect.rtd.ftrack.com/en/latest/release/migration.html)
    For more information on what has changed please refer to each updated package:
    ftrack connect 1.0.1
    ftrack connect cinema 4d 0.1.3
    ftrack connect hieroplayer 1.1.5
    ftrack connect legacy plugins 1.0.0
    ftrack connect maya 1.0.0
    ftrack connect nuke 1.0.1
    ftrack connect nuke studio 1.0.0
    ftrack connect rv 3.6
    ftrack python legacy api 3.6.0
    We hope you enjoy the release. Please let us know if you have any questions or feedback.
    cheers
    Eric
  7. Like
    Eric Hermelin got a reaction from Remus Avram in Send an existing note to more recipients   
    Hi Remus,
    This is currently not possible, it is however something we are looking to implement in the near future. I will keep you updated on the progress.
    cheers
    Eric
  8. Like
    Eric Hermelin got a reaction from Remus Avram in ConnectError: No system tray located.   
    Hi Remus,
    I would imagine that the user has removed parts of his gnome panels, in particular the applet for tray icons. You could probably add it back manually by right clicking the panel and selecting "Add to panel" and then making sure the panel configuration matches one of your working users , I can sadly not replicate it here as I do not have access to a system with gnome 2.
    As an alternative you could reset the users gnome panel configuration completely ,  I believe that can be done by deleting ~/.gconf/apps/panel and all its sub files and folders and then logging in and out, that should force gnome to regenerate the default configuration.
    cheers
    Eric
  9. Like
    Eric Hermelin got a reaction from Fredrik Limsater in python legacy api packaging updates   
    Hi,   The ftrack legacy python api have been distributed as a separate package bundled with its dependencies available for download from the ftrack settings page. While this has proven to be useful in many cases it has complicated the build and installation process for tools such as ftrack-connect and its dependencies.   We have therefore bitten the bullet and separated it out to its own repository, the code is available on bitbucket ( https://bitbucket.org/ftrack/ftrack-python-legacy-api ) and  pypi ( https://pypi.python.org/pypi/ftrack-python-legacy-api/3.6.1 ). The only major change, a part from the distribution procedure, is that the python websocket-client package have been bumped to version 0.40.0 to allow support for proxy servers within the event hub.   To install the legacy api you can use pip pip install ftrack-python-legacy-api  
    If you wish to install it into a self contained folder with all its dependencies that can easily be appended to your python path  pip install -I ftrack-python-legacy-api --target /shared/studio/python_path/  
    We will continue to supply a downloadable package for the next few releases but please make sure to update your install/update procedures. I will also encourage everyone to use the new python api ( http://ftrack-python-api.rtd.ftrack.com/en/stable/ ) when developing new tools and when time permits start migrating existing tools.   Please let us know if you have any questions or concerns.   cheers Eric