Jump to content

Search the Community

Showing results for tags 'ftrack-connect'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Company news
    • General announcements
  • ftrack Studio (main app)
    • General discussion
    • Feature requests
    • API
    • Help
    • Actions and Widgets
    • ftrack Go
  • ftrack Review
    • General discussion
    • Feature requests
    • Help
  • Connect and plugins
    • General discussion
    • Connect package releases
    • Feature requests
    • Help
    • Connect plugins releases
  • Advisory Forum
  • Tech preview
    • API
    • New integrations
    • Studio overview
    • ftrack Review


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 9 results

  1. Hi, Does anyone know what happend with the Flame integration plug which was on bitbucket ? Any plans to make a proper flame plugin ? Thanks,
  2. At the moment we can start as many instance of Ftrack Connect as we want. In this case in the Actions window in Ftrack Web UI you will get the same actions multiple times. Is it possible to restrict one instance per URL?
  3. Hi everyone, We have an issue trying to publish assets with maya2017 batch using ftrack-connect-0.7.6 & custom location (it worked with ftrack-connect-0.7.5). We started to dig and we noticed that the plugin is not selecting the custom location for publishing, even if it has the highest priority. Also, it's very strange that it works in maya for the same location. We printed out some information when location is selected by publisher (ftrack_connect/connector/base.py - pickLocation() method): We noticed that candidateLocation.accessor is not symbol.NOT
  4. Hey there, we are recently creating an executable file (.exe) for windows from the sources at https://bitbucket.org/ftrack/ftrack-connect.git. Having together all packages needed, this works great using Python 2.7.14, but there seems to be a major drawback. When trying to start Nuke via ftrack-connect-action, we get an error on hashlib saying: Nuke 10.5v4, 64 bit, built May 4 2017. Copyright (c) 2017 The Foundry Visionmongers Ltd. All Rights Reserved. Traceback (most recent call last): File "C:/Program Files/Nuke10.5v4/plugins/init.py", line 22,
  5. Hi everyone, I am currently trying to use nuke studio to prep plates and various assets. I though I could use the ftrack plugin to publish all these assets into our ftrack project but I have troubles writing a custom template. it seems the only data against I can run an expression is the shot name on the timeline, is this correct ? Is there any way to get sequence/shot/version from anywhere else (clip name or media file path would be great) ? Thanks in advance, Jerome
  6. Hi all, I have a simple hook added to FTRACK_CONNECT_PLUGIN_PATH: import ftrack_api class TestAction(object): identifier = "test_action" label = "Test Action" def __init__(self, session): super(TestAction, self).__init__() self.session = session def register(self): self.session.event_hub.subscribe('topic=ftrack.action.discover and source.user.username={0}'.format(self.session.api_user), self.discover) self.session.event_hub.subscribe('topic=ftrack.action.launch and source.user.username={0} and
  7. Hey guys, I just tried installing ftrack-connect through `pip install --target=C:\work\pipeline\dev\app\python git+https://bitbucket.org/ftrack/ftrack-connect.git`. The installation seemed to go smooth, but after the installation I tried running the ftrack connect service with: `python -m ftrack_connect`. That gave me the following error: ``` Traceback (most recent call last): File "C:\Python27\lib\runpy.py", line 162, in _run_module_as_main "__main__", fname, loader, pkg_name) File "C:\Python27\lib\runpy.py", line 72, in _run_code exec code in run_
  8. Hi all, where can I found the ftrack-connect offline documentation? Cheers!
  9. It would be an excellent feature of ftrack-connect to offer a UI for registering your workstation as a location in ftrack. That way when you publish using ftrack-connect, your component paths will be managed. I assume you might also want to add a preference in the ftrack web interface that would allow or disallow this functionality from connected ftrack-connect users.
  • Create New...