Search the Community

Showing results for tags 'connect'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

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

Categories

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 15 results

  1. We have a custom build of ftrack-connect in the studio which triggers a call out to the main() method in ftrack-connect. This works well for us. Currently I'm trying to make some changes which allow us to switch environments prior to opening ftrack-connect. Unfortunately, when starting and then exiting/deleting any PySide based widget prior to calling connect's main method, ftrack loads with a number of errors showing. Both are using the same install of PySide. It's still functional but looks like the path to resources are getting confused. I get a number QPixmap errors repeated: QPixmap::scaleHeight: Pixmap is a null pixmap QPixmap::scaled: Pixmap is a null pixmap Does anyone at ftrack know why this might be happening?
  2. I've successfully migrated to 2018 on my local working pipeline. I send my tool to the remote repo, then clone that onto a server location. I do all the setup to get the venv working then run ftrack. Everything is fine at this point. When I run Maya everything works as expected until I get this error: // Error: No module named collect_playblast_camera # Traceback (most recent call last): # File "<maya console>", line 1, in <module> # File "path\to\dependencies\ftrack_connect\resource\connect-standard-plugins\ftrack-connect-maya-publish-0.5.1\resource\maya_plugin\userSetup.py", line 18, in create_publish_menu # context_id=os.environ['FTRACK_CONTEXT_ID'] # File "path\to\dependencies\ftrack_connect\resource\connect-standard-plugins\ftrack-connect-maya-publish-0.5.1\dependencies\ftrack_connect_pipeline\application_plugin.py", line 28, in __init__ # self.register_assets() # File "path\to\dependencies\ftrack_connect\resource\connect-standard-plugins\ftrack-connect-maya-publish-0.5.1\dependencies\ftrack_connect_maya_publish\plugin.py", line 31, in register_assets # ftrack_connect_maya_publish.shared_pyblish_plugins.register() # File "path\to\dependencies\ftrack_connect\resource\connect-standard-plugins\ftrack-connect-maya-publish-0.5.1\dependencies\ftrack_connect_maya_publish\shared_pyblish_plugins\__init__.py", line 9, in register # import ftrack_connect_maya_publish.shared_pyblish_plugins.collect_playblast_camera # ImportError: No module named collect_playblast_camera // It's strange because there is a module named collect_playblast_camera in that location. Also, .pyc files are generated for the __init__.py and collect.py files, so it's compiling in that directory until the error. I've tried a bunch of stuff including straight up copying and pasting my working ftrack connect directory into the cloned one. I get the same error no matter what. Any thoughts? Thanks! EDIT: I think it might have to do with the file path being too long (I'm using windows). The pipeline works fine on my home computer.
  3. Hey there, I am in the process of evaluating ftrack and have some questions regarding publishing. Quite possible that I am missing anything as I am having some trouble understanding the basic principles in ftrack (coming from shotgun). I am gonna first outline what I think is the default render/publishing workflow. Gone through that in afx and nuke but I guess the workflow is similar in maya. Here the procedure in nuke: Open nuke via ftrack-connect (correct context). Nuke script is saved in an (more or less) arbitrary location. Do your work Render to another arbitrary location Attach a ftrackpublish node to the write node and publish (or is the intended way to use the publisher via the ftrack menu and the ftrackpublish-node is legacy?). During the publish the nuke-script as well as the rendered-sequence will be copied to the fileserver. - Script and image-sequence will be placed side by side into the following structure (given that the task was tied to a shot): project/sequence/shot/scriptname/version/ - The name of the script will be generic (nuke-script.nk or something like that) and thereby the version/shot/sequence will be not saved explicitly to the files but implicit in the ftrack database as well as the file structure. If theses assumptions are correct, here are some questions: is there any way to access/parse the ftrack-context in nuke? I'd rather like to use a custom write node which is automatically populated with the correct render-path (built from the task/shot/sequence etc.) on our fileserver. This is especially true for renderings running on the farm. I don't want the artists to manually navigate to the appropriate location and enter the correct filename as this is one task which should be handled by ftrack imo. the same applies to the script itself. I'd like to force the artist to save the script on our file-server (in the correct location and name) which is - as opposed to local files - backed regularly is the publish-action itself customizable? As the components (rendered sequence and script) already are in their appropriate locations on the fileserver there would be no need for any copying. Instead I'd like to only register the components and create the versions on the ftrack-server. Guess that this could be done with a custom publisher but I'd really like to let the built-in do the heavy lifting and just modify it I am quite sure that everything is possible. Just trying to figure out how much effort it takes. Best, Julian
  4. Hi everyone! I'm writing here to let you know that we are working on some changes to make Connect easier to extend and develop plugins for. Some of you I've already been in contact with but I would love to hear the feedback and opinions from the Community. We have a lot of ideas that we want to implement in Connect but the plan is to start out by tackling two common issues: Extending and modifying the environment and command when an application starts from Connect. Adding hooks to Connect without modifying the FTRACK_EVENT_PLUGIN_PATH. The way we intend to solve this is: Emit an event every time an application is launched from Connect. The event will contain application identifier, context, command and options that contain the environment variables. Here you will be able to make changes to environment variables, command and options. This should allow a lot of flexibility without having to override the built-in hook it-self. A platform dependent default directory from where plugins can be discovered without modifications to FTRACK_EVENT_PLUGIN_PATH. E.g. on OS X it would be something like /Users/mattiaslagergren/Library/Application Support/ftrack-connect-plugins/. We also intend to give the option set an environment variable so that you can centralise the plugins to one directory that everyone in the studio reads from. Connect will pick up plugins from both places.
  5. Hi, we are using Photoshop combined to Ftrack trough the connect plugin in our production pipeline since a few weeks. It is great, so we would like to do the same with NukeX now. I have successfully set one of our workstation with NukeX and the connect package and can use the Ftrack plugin integrated in NukeX on this machine. However, I can't manage to reproduce this on any of or workstations. NukeX and the connect package are installed, I can launch NukeX from an action inside the web application or from the connect package itself, but I can't manage to see any ftrack related windows in NukeX on those machines. There are no ftrack related windows in the custom windows (see image attached below). I have tried to uninstall ftrack connect package and NukeX, then reinstalled them after a reboot, without any success. I'm running Windows 10 and ftrack connect package 0.5.4. So far I have tested NukeX 10.0v4 and 10.0v5. Am I missing something here?
  6. Hey, We're looking to get some better integrations with ftrack into our own offline interfaces of our pipeline. At this moment we're working off of a great foundation in the studio with an explorer (browser), asset loader, app launcher and lots of other tools. The intentions now are to mix these up with ftrack, like pull thumbnails from ftrack and push information to ftrack upon publishes, etc. As such I'm wondering what way we should go about this. Widgets Would we be designing our own Widgets using the API completely from scratch? Or can we use widgets from connect in our own interfaces? Are the widgets in connect intended to be used that way? Things that would potentially make it easy to display thumbnails of an asset (or other information)? Connect Would the integrations require a running connect? Or when would we use it specifically? Integrating ftrack into our tools What's the best way to go about this? Any tips from the community are also very welcome! It would be great to have informational up-to-date widgets that are all built to be smoothly cached internally. Yet at this stage it's hard to see if I'm building from the ground up or if there are elements I can connect together to get up and running faster (and even share back?)
  7. I've started this public repo as a learning tool. I'm not sure if other people will be able to use this in the future just by running it. I'd like others to be able to use this as a learning tool and give people who are helping me more context when they're helping me out. I'm also making this because I just don't know the best practices for setting up a pipeline like this, so please if you could offer any critiques or pointers for Python/PySide in general that'd be great. This is a VS 2015 project for windows and will require the user to download their ftrack_api from the ftrackapp website and place the contents of the .tar file in the [root_folder]\modules\ftrack\pythonpath folder. More details will be in the README. The repo: https://github.com/mikebourbeauart/ftrack-from-source
  8. In a previous post, I suggested changing some basic UI behavior in Ftrack. Mattias suggested that I try to make the changes myself (I didn't even realize that was an option!). While incorporating the ftrack-connect clone into my workflow, I came across the concept of submodules for Git. After a ton of trial and error I've finished transitioning my connect project to successfully launch my custom actions from this new ftrack-connect submodule. Now I'm running into some issues with missing dependencies when launching Maya (I haven't tried other programs yet). I'm just trying to launch Maya without any errors before I incorporate all of my custom Maya launching code and env variables. Right now, Maya launches successfully, but I'm getting these errors: # Error: line 1: ImportError: file C:\Program Files\Autodesk\Maya2016\Python\lib\site-packages\maya\app\general\CommandPort.py line 15: DLL load failed: The specified module could not be found. # // Error: file: C:/Program Files/Autodesk/Maya2016/plug-ins/xgen/scripts/igInitialize.mel line 63: ImportError: file C:\Python27\lib\ctypes\__init__.py line 10: DLL load failed: The specified module could not be found. // // Error: Unable to execute igInitialize.mel. // // Error: line 0: ImportError: file C:\Python27\lib\ctypes\__init__.py line 10: DLL load failed: The specified module could not be found. // // Error: Unable to execute xgen.mel. // // Error: file: C:/Program Files/Autodesk/Maya2016/plug-ins/xgen/scripts/xgenUI.mel line 198: Cannot find procedure "registerXGenPrefTab". // // Error: ImportError: file C:\Python27\lib\ctypes\__init__.py line 10: DLL load failed: The specified module could not be found. // These directories already exist, but they're not being picked up. I'm already adding sys.path to the PYTHONPATH like so:: env = os.environ.copy() env['PYTHONPATH'] = \ ';'.join(sys.path) + \ ';path/to/ftrack_python_api' + \ ';path/to/another/module
  9. Could you change it so the app icon doesn't disappear when hovering over an action? It would be great if the icon would just highlight or glow with the play icon overlaying on top. I can't tell you how many times I go to click on an icon and then move my mouse off of it just to make sure I'm clicking on the correct action. There's just something jarring about it. Thanks.
  10. Hi I have an action, that creates folders and opens them as an explorer window. This action may not always complete successfully if certain things are not set up correctly. So I want to be able to notify the user that the action has failed. There is a 5 sec time out on actions that presents them as failed if there isn't a reply. Unfortunately as the action can at times take longer than 5secs before it can be determined if it ran OK or not, so I had to reply before doing my stuff. `self.session.event_hub.publish_reply(event,data)` That's all fine, but now I need to provide a further message back to the user to say "actually its not worked and here's why". I thought seeing as it doesn't seem possible to send further replies, (presumably because the webpage stops looking after its received one), I could just show a `PySide.QtGui.QMessageBox` with my message. However it seems I can't as the environment my action is running in, already has a QApplication started, and my action is running in a thread that is not the Main GUi Thread. Are there any suggestions on how I could either use QT or in some way provide visual feedback to the user about what has happened? One thought I had which is not Ideal, but could be work able is to Popen a separate Python thread which can launch my window and receive cmd args about msg, but the msg might cover multiple lines making that not so practical. I did consider using a job but It just didn't feel quite right the action normally takes less than 5 secs. Thanks Phil
  11. Hello, I'm starting to mess around with connect and I noticed that the legacy 'ftrack.' API was being used in the examples. Am I using the correct version of the docs? Thanks -Mike
  12. Hi I'm trying to build tools that work around the context given in a certain application, such as nuke. The Issue that I have is that the current connect launch application actions don't provide a consistent context environment. For example nuke and maya, provides FTRACK_TASKID, FTRACK_SHOTID among other keys (I would consider not context based). But Nuke Studio doesn't provide any keys that are context based. It seems connect actions are designed to only provide the information that they feel is applicable to the ftrack tools running in the application, and with no consideration for requirements of other tools being written by 3rd parties. It would be nice if for example there was a "FTRACK_ENTITY" = "[TYPE];[ID]" sort of environment variable in every connect application, so that who ever is producing tools, could use it how they wish, and always be reliant on that variable existing. This would then free us up to make tools that weren't reliant on a Shot based work flow for example it could be any custom entity type then instead. I'm new to ftrack and come from a shotgun pipeline. I appreciate I don't have a full understanding of how things should work in ftrack, but I'm used to being able to launch an application in what ever context and then having my tools run off that. I also realise that I could write\modify the existing actions provided by ftrack, but that's not desirable due to updates and deployment of the code. Could this sort of thing be implemented or is there a different more preferred approach which I'm unaware of? Thanks Phil
  13. auto_transfer.py -------------------------------------------------------------------------------------------------------------------------------- # :coding: utf-8import platform as _platformimport getpassimport loggingimport ftrackTOPIC = 'ftrack.location.component-added and source.user.username={0}'.format(getpass.getuser())sourceLocation = ftrack.Location('source.location')targetLocation = ftrack.Location('target.location')class ComponentAutoTransfer(object): '''Component add sourceLocation to targetLocation.''' def __init__(self, name='ftrack.ComponentAutoTransfer', priority=50): '''Initialise ComponentAutoTransfer with *name* and *priority*.''' self._name = name self._priority = priority super(ComponentAutoTransfer, self).__init__() def getName(self): '''Return name.''' return self._name def getPriority(self): '''Return priority.''' return self._priority def handle(self, event): '''Handle published *event*. event['data'] should contain: * componentId - The id of the component to resolve for. * ''' # Only interested location is User Home location. # locationName = ftrack.pickLocation(event['data']['componentId']).getName() location = ftrack.pickLocation(event['data']['componentId']) if location.getId() != sourceLocation.getId(): print(u'Only Use source.location!! Exclude Location : {0}'.format(location.getName())) return #print(u'Component ID is {0}'.format(event['data']['componentId'])) #print(sourceLocation.getId()) if ftrack.pickLocation(event['data']['componentId']).get('id') == ftrack.Location(sourceLocation).get('id'): componentId = event['data']['componentId'] print componentId sourceComponent = sourceLocation.getComponent(componentId) # Add component to target location (and transfer any data) targetComponent = targetLocation.addComponent(sourceComponent) print(u'Transferred component {0} -> {1}'.format( sourceComponent.getInternalPath(), targetComponent.getInternalPath() )) else: print(event['data']['componentId'])def register(registry, **kw): '''Register auto_transfer plugin.''' logger = logging.getLogger( 'ftrack_plugin:ComponentAutoTransfer.register' ) # Validate that registry is an instance of ftrack.Registry. If not, # assume that register is being called from a new or incompatible API and # return without doing anything. if not isinstance(registry, ftrack.Registry): logger.debug( 'Not subscribing plugin as passed argument {0!r} is not an ' 'ftrack.Registry instance.'.format(registry) ) return plugin = ComponentAutoTransfer() ftrack.EVENT_HUB.subscribe('topic=ftrack.location.component-added and source.user.username={0}'.format(getpass.getuser()), plugin.handle) registry.add(plugin)resolver.py ------------------------------------------------------------------------------------------------------------------------------- # :coding: utf-8import platform as _platformimport getpassimport loggingimport ftrackTOPIC = 'ftrack.location.request-resolve and source.user.username={0}'.format(getpass.getuser())class ComponentInLocationPathResolver(object): '''Resolve the filesystem path of a component in a specific location.''' def __init__(self, name='ftrack.componentInLocationPathResolver', priority=10): '''Initialise resolver with *name* and *priority*.''' self._name = name self._priority = priority super(ComponentInLocationPathResolver, self).__init__() def getName(self): '''Return name.''' return self._name def getPriority(self): '''Return priority.''' return self._priority def handle(self, event): '''Handle published *event*. event['data'] should contain: * componentId - The id of the component to resolve for. * locationName - Name of the location to resolve for. Can be None to indicate location should be determined automatically. * platform - A string representing the platform to resolve for. Can be either 'Windows' or 'Linux'. ''' if getpass.getuser() != event['source']['user']['username']: # Only interested in specific current user topic. return # Extract useful information from passed event. componentId = event['data']['componentId'] platform = event['data']['platform'] if platform and platform != _platform.system(): # Don't resolve paths for other platforms. return locationName = event['data'].get('locationName', None) if not locationName: # Pick a suitable location if none was passed. location = ftrack.pickLocation(componentId) if location is not None: locationName = location.getName() if not locationName: return try: # Attempt to resolve to full filesystem path using locally # available location plugins. location = ftrack.Location(locationName) component = location.getComponent(componentId) resolvedPath = component.getFilesystemPath() except ftrack.FTrackError: return # Return data to send as reply event. return {'path': resolvedPath}def register(registry, **kw): '''Register resolver plugin.''' logger = logging.getLogger( 'ftrack_plugin:resolver.register' ) # Validate that registry is an instance of ftrack.Registry. If not, # assume that register is being called from a new or incompatible API and # return without doing anything. if not isinstance(registry, ftrack.Registry): logger.debug( 'Not subscribing plugin as passed argument {0!r} is not an ' 'ftrack.Registry instance.'.format(registry) ) return plugin = ComponentInLocationPathResolver() ftrack.EVENT_HUB.subscribe('topic=ftrack.location.request-resolve and source.user.username={0}'.format(getpass.getuser()), plugin.handle) registry.add(plugin)---------------------------------------------------------------------------------------------------------------------------------- auto_transfer_error.log -- show below error log.... ERROR:FTrackCore.api.event.hub.EventHub:Error calling subscriber <Subscriber metadata={'id': '10280d1070594b2abc2ddb33d96c84b3'} subscription=topic=ftrack.location.component-added and source.user.username=kiseo_kim> for event <Event {'topic': u'ftrack.location.component-added', 'source': {u'id': u'b9d8d67ae5e64de498f08dc7cf683173', u'user': {u'username': u'kiseo_kim'}}, 'target': u'', 'sent': None, 'data': {u'locationId': u'ce9b348f-8809-11e3-821c-20c9d081909b', u'componentId': u'86fd5cfc-a7ca-11e5-9360-003048f5c468'}, 'id': u'5196c741ef6a4617acd0a4429afc0454', 'inReplyToEvent': None}>.Traceback (most recent call last): File "/app/prog/ftrack_connect/common.zip/FTrackCore/api/event/hub.py", line 663, in _handle response = subscriber.callback(event) File "/home/kiseo_kim/ftrack-lib/ftrack_events/auto_transfer.py", line 42, in handle if location.getId() != sourceLocation.getId():AttributeError: 'NoneType' object has no attribute 'getId'ERROR:FTrackCore.api.event.hub.EventHub:Error calling subscriber <Subscriber metadata={'id': '64757e1a507842dbbb268734aaf76807'} subscription=topic=ftrack.location.component-added and source.user.username=kiseo_kim> for event <Event {'topic': u'ftrack.location.component-added', 'source': {u'id': u'b9d8d67ae5e64de498f08dc7cf683173', u'user': {u'username': u'kiseo_kim'}}, 'target': u'', 'sent': None, 'data': {u'locationId': u'ce9b348f-8809-11e3-821c-20c9d081909b', u'componentId': u'86fd5cfc-a7ca-11e5-9360-003048f5c468'}, 'id': u'5196c741ef6a4617acd0a4429afc0454', 'inReplyToEvent': None}>.Traceback (most recent call last): File "/app/prog/ftrack_connect/common.zip/FTrackCore/api/event/hub.py", line 663, in _handle response = subscriber.callback(event) File "/home/kiseo_kim/ftrack-lib/ftrack_events/auto_transfer.py", line 42, in handle if location.getId() != sourceLocation.getId():AttributeError: 'NoneType' object has no attribute 'getId'INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): my.server.com86fd5cfc-a7ca-11e5-9360-003048f5c468INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): my.server.comERROR:FTrackCore.api.event.hub.EventHub:Error calling subscriber <Subscriber metadata={'id': '10280d1070594b2abc2ddb33d96c84b3'} subscription=topic=ftrack.location.component-added and source.user.username=kiseo_kim> for event <Event {'topic': u'ftrack.location.component-added', 'source': {u'id': u'b9d8d67ae5e64de498f08dc7cf683173', u'user': {u'username': u'kiseo_kim'}}, 'target': u'', 'sent': None, 'data': {u'locationId': u'87794940-a750-11e5-a7f8-003048f5c468', u'componentId': u'86fd5cfc-a7ca-11e5-9360-003048f5c468'}, 'id': u'f52ed905cdda453aab47c935f266e441', 'inReplyToEvent': None}>.Traceback (most recent call last): File "/app/prog/ftrack_connect/common.zip/FTrackCore/api/event/hub.py", line 663, in _handle response = subscriber.callback(event) File "/home/kiseo_kim/ftrack-lib/ftrack_events/auto_transfer.py", line 57, in handle sourceComponent.getInternalPath(),AttributeError: 'Component' object has no attribute 'getInternalPath'86fd5cfc-a7ca-11e5-9360-003048f5c468ERROR:FTrackCore.api.event.hub.EventHub:Error calling subscriber <Subscriber metadata={'id': '64757e1a507842dbbb268734aaf76807'} subscription=topic=ftrack.location.component-added and source.user.username=kiseo_kim> for event <Event {'topic': u'ftrack.location.component-added', 'source': {u'id': u'b9d8d67ae5e64de498f08dc7cf683173', u'user': {u'username': u'kiseo_kim'}}, 'target': u'', 'sent': None, 'data': {u'locationId': u'87794940-a750-11e5-a7f8-003048f5c468', u'componentId': u'86fd5cfc-a7ca-11e5-9360-003048f5c468'}, 'id': u'f52ed905cdda453aab47c935f266e441', 'inReplyToEvent': None}>.Traceback (most recent call last): File "/app/prog/ftrack_connect/common.zip/FTrackCore/api/event/hub.py", line 663, in _handle response = subscriber.callback(event) File "/home/kiseo_kim/ftrack-lib/ftrack_events/auto_transfer.py", line 54, in handle targetComponent = targetLocation.addComponent(sourceComponent) File "/app/prog/ftrack_connect/common.zip/FTrackCore/api/client.py", line 89, in wrapper result = function(*args, **kw) File "/app/prog/ftrack_connect/common.zip/FTrackCore/api/location/base.py", line 518, in addComponent raise ComponentInLocationError(componentId, self.getId())ComponentInLocationError: Component "86fd5cfc-a7ca-11e5-9360-003048f5c468" already exists in location "add7b91a-a3e4-11e5-a4fe-003048f5c468".Only Use source.location!! Exclude Location : ftrack.serverOnly Use source.location!! Exclude Location : ftrack.serverOnly Use source.location!! Exclude Location : ftrack.serverOnly Use source.location!! Exclude Location : ftrack.server86fd5cfc-a7ca-11e5-9360-003048f5c468ERROR:FTrackCore.api.event.hub.EventHub:Error calling subscriber <Subscriber metadata={'id': '10280d1070594b2abc2ddb33d96c84b3'} subscription=topic=ftrack.location.component-added and source.user.username=kiseo_kim> for event <Event {'topic': u'ftrack.location.component-added', 'source': {u'id': u'b9d8d67ae5e64de498f08dc7cf683173', u'user': {u'username': u'kiseo_kim'}}, 'target': u'', 'sent': None, 'data': {u'locationId': u'add7b91a-a3e4-11e5-a4fe-003048f5c468', u'componentId': u'86fd5cfc-a7ca-11e5-9360-003048f5c468'}, 'id': u'97300be5074e4455917f802fb9d47b21', 'inReplyToEvent': None}>.Traceback (most recent call last): File "/app/prog/ftrack_connect/common.zip/FTrackCore/api/event/hub.py", line 663, in _handle response = subscriber.callback(event) File "/home/kiseo_kim/ftrack-lib/ftrack_events/auto_transfer.py", line 54, in handle targetComponent = targetLocation.addComponent(sourceComponent) File "/app/prog/ftrack_connect/common.zip/FTrackCore/api/client.py", line 89, in wrapper result = function(*args, **kw) File "/app/prog/ftrack_connect/common.zip/FTrackCore/api/location/base.py", line 518, in addComponent raise ComponentInLocationError(componentId, self.getId())ComponentInLocationError: Component "86fd5cfc-a7ca-11e5-9360-003048f5c468" already exists in location "add7b91a-a3e4-11e5-a4fe-003048f5c468".86fd5cfc-a7ca-11e5-9360-003048f5c468ERROR:FTrackCore.api.event.hub.EventHub:Error calling subscriber <Subscriber metadata={'id': '64757e1a507842dbbb268734aaf76807'} subscription=topic=ftrack.location.component-added and source.user.username=kiseo_kim> for event <Event {'topic': u'ftrack.location.component-added', 'source': {u'id': u'b9d8d67ae5e64de498f08dc7cf683173', u'user': {u'username': u'kiseo_kim'}}, 'target': u'', 'sent': None, 'data': {u'locationId': u'add7b91a-a3e4-11e5-a4fe-003048f5c468', u'componentId': u'86fd5cfc-a7ca-11e5-9360-003048f5c468'}, 'id': u'97300be5074e4455917f802fb9d47b21', 'inReplyToEvent': None}>.Traceback (most recent call last): File "/app/prog/ftrack_connect/common.zip/FTrackCore/api/event/hub.py", line 663, in _handle response = subscriber.callback(event) File "/home/kiseo_kim/ftrack-lib/ftrack_events/auto_transfer.py", line 54, in handle targetComponent = targetLocation.addComponent(sourceComponent) File "/app/prog/ftrack_connect/common.zip/FTrackCore/api/client.py", line 89, in wrapper result = function(*args, **kw) File "/app/prog/ftrack_connect/common.zip/FTrackCore/api/location/base.py", line 518, in addComponent raise ComponentInLocationError(componentId, self.getId())ComponentInLocationError: Component "86fd5cfc-a7ca-11e5-9360-003048f5c468" already exists in location "add7b91a-a3e4-11e5-a4fe-003048f5c468". ------------------------------------------------------------------------------------------------------------------------------ What is the reason above error log? (automatic transfer is work fine, but... show above error log...) Thanks.
  14. Hi all, it would be great to add native web-proxy support to the ftrack connect app on Windows. I tried to work around this with using environment-variables ("FTRACK_PROXY" and "HTTP_PROXY" etc.) with no success. The app just returns a "Failed to connect to event server" error-message. Regards, Carl
  15. Hi guys, I'm having this issue with connect. It won't open up. I uninstalled it and re-installed several times with no luck. Any Ideas? File "C:\Program Files\ftrack-connect-package\library.zip\cx_Freeze__init__.py", line 29, in <module>File "C:\Program Files\ftrack-connect-package\library.zip\ftrack_connect_package__main__.py", line 70, in <module>File "C:\Program Files\ftrack-connect-package\common.zip\ftrack_connect\__main__.py", line 77, in main theme=namespace.themeFile "C:\Program Files\ftrack-connect-package\common.zip\ftrack_connect\ui\application.py", line 83, in __init__ self.login()File "C:\Program Files\ftrack-connect-package\common.zip\ftrack_connect\ui\application.py", line 138, in login self.loginWithCredentials(server, username, apiKey)File "C:\Program Files\ftrack-connect-package\common.zip\ftrack_connect\ui\application.py", line 194, in loginWithCredentials self.configureConnectAndDiscoverPlugins()File "C:\Program Files\ftrack-connect-package\common.zip\ftrack_connect\ui\application.py", line 201, in configureConnectAndDiscoverPlugins ftrack.setup()File "C:\Program Files\ftrack-connect-package\common.zip\FTrackCore\__init__.py", line 147, in setup EVENT_HANDLERS.discover()File "C:\Program Files\ftrack-connect-package\common.zip\FTrackCore\api\registry.py", line 54, in discover .format(modulePath, error)