Jump to content

Search the Community

Showing results for tags 'event listener'.

  • 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
  • ftrack Review
    • General discussion
    • Feature requests
    • Help
  • Connect and Integrations
    • Releases
    • General discussion
    • Feature requests
    • Early Access Integrations & Connect
    • Help
  • Advisory Forum
  • Tech preview
    • API

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


Website URL


Location


Interests

Found 3 results

  1. Hi, I am currently trying to automatically get web-playable movies when publishing the sequnces of frames. I'd like to discuss whether it's an optimal way of doing this and to ask some questions. I am registering for "ftrack.location.component-added" event, get the location and the component, check if a component's "system_type" is "sequence", ask the location to provide a file system path to frames, create a movie from these frames and fire up the "ftrack.connect.publish.make-web-playable" event providing the version id and the movie file path. The movie is generated fine, the event is published but nothing new is added to my version, the movie is not there. If I try to publish these frames together with this movie manually (by selecting the movie as web-playable in the ftrack connect), everything works as expected. Any suggestions? Thank you. Regards, Andriy
  2. I am about to shift some specific actions from running locally on user-workstations to one or two central worker-clients. Some of these actions will run a little bit longer and won't be discoverable during processing. To keep it simple, maintainable and scalable I'd like to avoid setting up threading/multiprocessing mechanisms inside the action and do that on a higher level instead. Is there a canonical way to pull this off? If I understand it correctly the event.stop() method will only work if I register the listeners from one single process. So multiple-docker containers or multiple hosts won't work because this would lead to multiple actions with the same name showing up for users. Is that correct? Anything else to watch out for?
  3. Hello. I am trying to create an event Listener that basically prevents people from moving assets inside ftrack. I found an example and tried to do it my self, but Iam getting some issues. the script is suscribed to 'topic=ftrack.update', and will always revert changes,but it seems the "revert function" also activates the listener, so it enters in an infinite loop. these are the functions used in my script. Any help would be very appreciated: def MoveAssetsBlock(session, event): reverted= False for entity in event['data'].get('entities', []): if (entity.get("entityType") == "task" and entity["action"] == "move"): entity_id = entity['entityId'] fObject = session.query("Context where id is '{0}' ".format(entity_id))[0] fObject['parent_id'] = entity["changes"]["parent_id"]["old"] reverted=True if reverted: try: session.commit() except Exception: session.rollback() raise def register(session, **kw): if not isinstance(session, ftrack_api.Session): return handle_event = functools.partial( MoveAssetsBlock, session) session.event_hub.subscribe('topic=ftrack.update', handle_event)
×
×
  • Create New...