1. Company news

    1. 18
      posts
  2. ftrack Studio (main app)

    1. 1,175
      posts
    2. 1,195
      posts
    3. API

      1,677
      posts
    4. 615
      posts
    5. Actions and Widgets

      Extending the functionality in ftrack with custom Actions and Widgets - read more at ftrack.com/actions

      272
      posts
    6. ftrack Go

      Discussions about ftrack Go for iOS and Android

      22
      posts
  3. ftrack Review

    1. 97
      posts
    2. 109
      posts
    3. 26
      posts
  4. Connect and plugins

    1. 383
      posts
    2. Connect package releases

      Notes on the latest Connect releases.

      7
      posts
    3. 146
      posts
    4. 312
      posts
    5. 43
      posts
  5. Tech preview

    1. API

      18
      posts
    2. New integrations

      Discussions of the new tools that will replace current Connect integrations into Nuke, Maya, 3DS Max and other applications.

      31
      posts
    3. 31
      posts
    4. 3
      posts
  • Popular Contributors

    Nobody has received reputation this week.

  • Status

  • Who's Online (See full list)

  • Recent posts

    • Hello,   I am trying to use the new Review "Play selection in Player (Experimental)", but I can't figure out what information it's using to sort which order the shots play in.  It's not shot order, it's not the order it was published and it's not the order I clicked them in.  I can't move them around either.   Any help would be greatly appreciated!   thank you, Ozen
    • hi @Rory here a simple example to translate the entities using the action handler as base class: from ftrack_action_handler.action import BaseAction import ftrack_api class TestAction(BaseAction): label = 'Test Action' identifier = 'com.ftrack.test.action' description = 'Simple test action' def validate_selection(self, entities, event): if not entities: return False results = self._translate_event( self.session, event ) if not results : return False for (entity_type, entity_id) in results[0]: resolved_entity= self.session.get(entity_type, entity_id) print resolved_entity, resolved_entity.entity_type return True def discover(self, session, entities, event): return self.validate_selection(entities, event) def launch(self, session, entities, event): return { 'success': True, 'message': u'Done.' } def register(api_object, **kw): '''Register hook with provided *api_object*.''' if not isinstance(api_object, ftrack_api.session.Session): return action = TestAction(api_object) action.register() hope it helps. L.
    • Hallo Marc,   There is relatively little in the Connect log as this issue is strictly related to the Adobe plugin installation. A workaround has been to have an older version of the Adobe software installed so that the plugin will be detected. Adobe should allow you to download a previous version easily.   Please let us know how we can be of more help via your existing Support ticket. Cheers from Madrid, Dan
    • Hi @Aaron Powell using the discovery to populate the available applications does not work as it will look into the application store to decide which one to start. The best option at the time seems to be to override the _getApplicationLauncher as by this example to inject the launchArguments you are after. long story short this is what you can simply do:   class ApplicationLauncher(ftrack_connect.application.ApplicationLauncher): '''Custom launcher to modify environment before launch.''' def _getApplicationLaunchCommand(self, application, context=None): command = super(ApplicationLauncher, self)._getApplicationLaunchCommand(application, context) command.extend(context.get('launchArguments')) return command The issue is in the original _getApplicationLauncher, which extracts the extra launchArguments from the applications but does not take in account the current context. good news is that we are in the process of reviewing how applications are launched, hence this will be fixed soon. Cheers. L.