Lorenzo Angeli

Hi Thorsten, there are some news regarding api and support for py3k. We have been opening a new forum section to provide early access (with instructions and warnings) to the development branch which provide support to python 3.6 , how to install and test. If you have a chance to test, please share there your finds in there! Cheers. L.

Please note, the current development status is in Beta stage and is not suitable for production. Welcome to the ftrack-python-api tech preview for python 3.x compatibilty. Here are some brief instructions on how to start testing the upcoming release of the new API. We strongly recommend sandboxing the testing environment using virtualenv. Prepare your sandbox Create a virtualenv with the Python 3 interpreter: $ virtualenv -p `which python3.6` ~/ftrack_python_api_py3k Activate virtualenv: $ source ~/ftrack_python_api_py3k/bin/activate Install Install from the development branch: $ pip install git+https://bitbucket.org/ftrack/ftrack-python-api.git@backlog/ftrack-python-api-compatibility-with-python-3 Test Run python from virtualenv and check that everything is in place: (ftrack_python_api_py3k) $ python -V (ftrack_python_api_py3k) $ Python 3.6.5 You can now start the Python interpreter and start using the API as usual. >>> from ftrack_api import Session >>> session = Session() >>> projects = session.query('Project').all() >>> print(projects) If you need to use the Python3 and the ftrack module just run Python directly from the virtualenv using: $ ~/ftrack_python_api_py3k/bin/python3 -c "import ftrack_api;print(ftrack_api.__version__)" Bug reporting Please use this thread to report issues and bugs. When reporting bugs, please remember to include: * Operating system in use. * Python version in use (use: python -V). * Full stack trace or error.

Hi @Jay Roth, would it be possible to send to support the log file so we can have a further look in what might be happening ? You can find here the troubleshooting guide for c4d . Cheers. L.

Hi @fooopa and welcome back to ftrack folder structure is somewhat tricky to generalise for every user case, that's why our is customizable from the end users to fit their needs. You can find a complete example in the ftrack-recipes repo, from there you'll be able to decide how and where files will be stored and named. Keep the location's api documentation at hand while looking into the code as it might come at hand for the terminology. If you feel like ftrack is limited for what concerns interaction and customisation, please keep in mind that any operation with ftrack entities can be driven through event system: In the same recipes repository, you can find a good example on how to create an action that extracts data and produce a downloadable excel file. If you have any issue or doubt with it please let us know. Cheers. L.

Hi @dthomlison depending on your operating system the folder containing the actions, could be in different places: OS X: ~/Library/Application Support/ftrack-connect-plugins Windows: C:\Documents and Settings\<User>\Application Data\Local Settings\ftrack\ftrack-connect-plugins Linux: ~/.local/share/ftrack-connect-plugins get to the folder , depending on your Os , and remove the actions. if you are still having issues please let us know. Cheers. L.

Hi ftrack-connect-package gets shipped with its own python interpreter. looks like the python you are running lacks of the ssl support: >> SSLError: Can't connect to HTTPS URL because the SSL module is not available. you might have to rebuild python with it. hope it helps. Cheers. L.

Hi Timofey, if you are using connect, click on the system tray icon and then Open plugin directory. in there you should be having the actions code, removing or moving it to another folder should resolve your issue. if you have any issue know ! L.

Hi @hulmanen, sorry to see you are having issues. I've been able to replicate the problem and it seems to be coming from missing library in Nuke Studio. In order to confirm, can you please check if in your console you get this error ? /usr/local/Nuke11.2v3/QtWebEngineProcess: error while loading shared libraries: libQt5WebEngineCore.so.5: cannot open shared object file: No such file or directory Looks like Foundry is aware of this (Ticket #334788). You can check the status of this ticket here : Hope it helps, we will follow up with Foundry and see by when they'll be able to provide support. Cheers. L.

Thanks Laura, we'll be having a look and get back to you. If you are using legacy api thought I would suggest start looking on how to port it over the new api code. You can find a good example here: https://bitbucket.org/ftrack/ftrack-example-location Cheers. L.

Hi Laura, I'm sorry to hear you are having issues. If the custom location gets picked up by interactive maya and it can publish correctly, should work from within a batch session as well. Are you using the new python api to register the location or legacy ones ? Would it be possible for you to share the code you are using to register the new location ? If, for privacy reasons you cannot post it here, feel free to open a ticket at support@ftrack.com and share it there. Cheers. L.

Hi @hquintanaro Are these error coming from the ftrack-connectg-package you have been dowloading from https://www.ftrack.com/en/portfolio/connect ? ftrack-connect-package (on linux) should be able to run centrally, but is suggest first to test it locally. If you do have errors try to see if you have any missing library regarding ssl. Cheers. L.

Hi hquintanaro, can you please check if this happens to you with the latest official build as well ? https://www.ftrack.com/en/portfolio/connect Thanks. L. p.s python 2.7.15 is not available by default on CentOS Linux release 7.5.1804 (Core) is this something you've been compiling or from a repository ?

Download 2.0.0RC2 Requirements: Centralised storage scenario or a custom location available and working. What to expect to work: Create project structure on selected server project Note this has been changed from previous version. Validate against selected project schema Create extra tasks on clips through tags dropping Publish to given selected task Customise asset name to publish to Customise asset type to publish to Rendered Plates (Shot Exporter) Rendered Audio (Shot Exporter) Rendered Quicktime (Shot Exporter) Upload for review on server Generate and upload Thumbnail (Shot Exporter) Publish EDL (Timeline exporter) Rebuild tracks from server Allows versioning of rebuilt tracks Reintroduce and expand the clip template parser Simplify the path management New ftrack style icons. (new) Nuke studio tokens can be used as asset name. (new) Task presets can be duplicated. (new) Task presets allows changing output component name. (new) Nuke script gets read assetized through Transcode processor selection. Aim for Testing: Nuke Studio / Hiero versions : 9.X , 10.X , 11.X External Frame server Project creation Task Creation Track rebuild Versioning Task duplication Nuke file generation Note: Due to the continuous changes to the path management, using previously saved presets makes the integration break.

Hi Neelz, sorry to hear you are having problems. At the moment we do not support resolve of the asset name through tokens , but is an interesting idea worth looking into. Another thing which look suspicious is that the Shot Template is empty where should be populated with a some default parser. A new RC version will be soon released, in the meanwhile though , would you mind sending the log file ? If you don't know how, please have a look at the section 'Where can I find the ftrack Connect log files? ' of our help center. Cheers.

Hi Niels, Thanks for testing and sorry to hear you have been having problems. we have just released an updated version (RC1) of the plugin with many updates and changes. https://forum.ftrack.com/topic/1371-200rc1/ Please give it a go and let us know!