Lorenzo Angeli

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

@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.

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.

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.

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.

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.

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

@jen_at_floyd you should have an email.

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

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 download and uncompress the new version in : <ftrack-connect-package>/resource/connect-standard-plugins/ restart ftrack-connect-package

Hi @marc mantei , please ensure you are extending the FTRACK_CONNECT_PLUGIN_PATH and not overwriting it. L.

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.

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 something like REZ to handle it all from there. The latter option could be a bit of a stretch , depending on how often you need to maintain these, but might worth the time. Hope it helps. L

@ch_brown @Florent Dupont you should be having an invitation email now, let us know if does not work for any reason. Cheers. L.

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_site_location/ https://bitbucket.org/ftrack/ftrack-recipes/src/master/python/actions/migrate_components/ I'd suggest looking into these while keeping at hand the documentation for the location/structure system. http://ftrack-python-api.rtd.ftrack.com/en/stable/locations/tutorial.html?highlight=location https://help.ftrack.com/en/articles/1040442-locations Hope it helps. L.