Jump to content

Lorenzo Angeli

Administrators
  • Content Count

    227
  • Joined

  • Last visited

  • Days Won

    15

Everything posted by Lorenzo Angeli

  1. hi @Hadrien FARRE this error often comes from a mix up between python 3 and python2, usually trying to load python2 in python3 interpreter. Also can see you are using python 3.9 , although supposed to be working , we currently support up to 3.8 with a closer eye to 3.7. hope it helps. L.
  2. Download 0.3.1 Originally written by Mike Datsik What's new * Changed : Update setup process * Fixed: Houdini fails to load under linux How to install stop ftrack-connect-package download and uncompress the new version in : <ftrack-connect-package>/resource/connect-standard-plugins/ restart ftrack-connect-package
  3. @matthieu Thanks for the headup on the PySide version! if you are using the pyside2 branch of connect (which is also python3) you should set : FTRACK_API_USER FTRACK_SERVER FTRACK_API_KEY the other legacy envs (such as LOGNAME) have been deprecated in that branch. hope it helps. L.
  4. hi @matthieu, we are actively working on connect for python on 3 .If you like to give it a go , you can try this branch This new version though is not compatible with the current integrations ., but we are working on solutions to make them work back, just not there yet. In regard of your error, seems strange to be coming from the api , as it seems to be referring to Dialogs, which are just a ui thing. There'll be some news soon. Cheers. L.
  5. Hi @Finn Jäger, what i would try to is to upload the file as you like , but ensuring ftrack does not re encode it. This can be done though connect, overriding the encode event listener: or straight from the api hope it helps. L.
  6. Download 1.3.0 Changes: Changed : Update pyside signal signature for pyside2 compatibility. New : Add support for FBX import. 1) remove previous plugin from either connect plugins or connect resources. 2) download the new version from the above link 2) decompress the zip in the FTRACK_CONNECT_PLUGIN_PATH 3) restart connect If there's any problem please let us know! L.
  7. Hi @marc mantei glad to you hear you sorted it If there's anything else, please do not hesitate to get back in touch! L.
  8. Download new hook file. The installation directories for Cinema 4D have changed with the recent releases. In order to show the new applications, you must replace the existing hook file, which can be found in the following directories: macOS: /Applications/ftrack-connect.app/Contents/MacOS/resource/hook Windows: C:\Program Files (x86)\ftrack-connect-package-1.1.1\resource\hook
  9. @jen_at_floyd you should have an email.
  10. Download 2.4.1 What's new New : Startup error related to location setup are now visually reported. Fixed : Discovery does break on non context entities. How to install stop ftrack-connect-package remove previous nuke studio plugin from : <ftrack-connect-package>/resource/connect-standard-plugins/ download and uncompress the new version in : <ftrack-connect-package>/resource/connect-standard-plugins/ restart ftrack-connect-package
  11. Download 0.3.0 Originally written by Mike Datsik What's new * Changed : Add file logger * Changed : Update pyside signal signature for pyside2 compability. * New : FBX export on publish. * New: FBX import. * Fixed: Thumbnail save failed on windows publish. * Changed: Have plug-in load proceed if there is an exception setting up frame range and fps. * Fixed: Hip can now be imported on Windows with paths having backlash (\) elements. * New: New Import,Merge & Open import options. How to install stop ftrack-connect-package downlo
  12. Hi @marc mantei , please ensure you are extending the FTRACK_CONNECT_PLUGIN_PATH and not overwriting it. L.
  13. Hi @zhouyu08512, as the question seems a bit vague, would you mind sending an email to support@ftrack.com , providing all the information you have about the tool you want to write and what you've been trying so far (with code if possible), so we can try to help ? Looking forward to hear more from you! L.
  14. Hi @Aaron Powell, more than "whatever works for you" is really the fact we try not to enforce these , as are usually defined by studio structures and pipelines. that said, it really depends on what you are after..... overall if you just have scripts which use the ftrack_python_api, my suggestion would be to have them stored in a central place and mapped to the PYTHONPATH (you can think also to have some inheriting from a central path for utilities and having modules named for each show with the specific code you need.) On how, you can go from setting PYTHONPATH into the envs to use someth
  15. @ch_brown @Florent Dupont you should be having an invitation email now, let us know if does not work for any reason. Cheers. L.
  16. Hi @John, sorry for the delay on getting back to you. if you have a centralised storage scenario, the easier one would be to provide your own custom location , having it registered and then through an action provide the transfer of the components into the other location. The only thing you need to be careful about are the priorities of the location themselves, so you don't (by mistake) make the other one replacing (as priority) the centralised storage. here couple of examples might be of help in your journey https://bitbucket.org/ftrack/ftrack-recipes/src/master/python/actions/multi
  17. Hi @zhouyu08512, sorry for the delay on getting back to you. Versioning is handled by ftrack itself and is not something we allow to define though the Nuke Studio templated names. I'd suggest, if you haven't yet, trying the latest version available on the forum and see whether the video issue is solved. let us know how it goes. If the problem persist, please open a ticket with support@ftrack.com so we can properly investigate your issue. Cheers. L.
  18. @Mani Varma would you mind opening a ticket with support@ftrack.com providing the logs from ftrack-connect and any relevant information about your setup, so we can properly have a look into your issue ? Thanks. L.
  19. Hi @Bryan Fordney if you are using actions and events (hence you are in python land), I'd suggest using the appdirs module. We use the same to store connect and other plugin credentials, here an example. Hope it helps. L.
  20. Hi @Mani Varma From the outputs it seems you are using connect-package version 1.1.1 , would you mind trying with the latest 1.1.2 version ? Overall though, the error you are having is usually generated by a python version lower than 2.7.9 Please let us know how it goes. Cheers. L.
  21. All platforms: Download 1.0.3 Documentation Changes since last version fixed : Action icons not correctly loading. changed: Version comments are published as Perforce changelist description. new : Update docs to include timeout solution for credentials. How to install stop ftrack-connect-package remove previous nuke studio plugin from : <ftrack-connect-package>/resource/connect-standard-plugins/ download and uncompress the new version in :<ftrack-connect-package>/resource/connect-standard-plugins/ restart ftrack-con
  22. Hi @Bryan Fordney we have a similar integration for Nuke Studio and we are looking into the user base requests for other DCC applications. Are these the kind of features you would be after ? Cheers. L.
  23. Hi @Rory , as long as the module you are importing are in PYTHONPATH it should work. If you have both python2 and 3 available be careful though as the variable is the same for both and can lead to issues. If you still have issues, please send the relevant code to our support providing details about where the third party module is located and how has it been installed. Cheers. L.
  24. Lorenzo Angeli

    Action on Shot

    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 re
  25. 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
×
×
  • Create New...