Lorenzo Angeli

Hi @Julian Martinz , we'll be looking soon on providing something off the shelf. Your approach seems the on the right track though ! L.

Hi @Julian Martinz if you want to use either one or the other in the same project you might have to think of creating what I would call a proxy location. This location would accept both (or more) the locations you want to use and through logical gates you can redirect the publish to what you want, either based on task, component or any other logic that suits you. Hope it helps. L.

Hi @narvi, the latest perforce location plugin can be downloaded from this address. For what concerns S3 there's an example built on top of the legacy api here but still has to be ported to the new one. This is something on our todo list to port it over. Hope it helps. L.

Hi @narvi, there was , in the old api , an ftrack s3 accessor to make you able to move data in an out from there, but this is something we have to look back into and port over the new api, hopefully we'll be able to schedule this sooner rather than later. (contributions are welcome though ) Perforce wise, is coming. It does work as a normal ftrack storage , hence is client side but do not require local installation of the server . If you have any more questions please let us know. Cheers. L.

Hi @Jakub Trllo, hierarchical attributes are tricky. Hope this snippet can help you out. If case does not let us know! Cheers. L.

Hi Julian,if you have long running jobs, the best option you have is to actually use multithreading from within the action ,just be careful to use this solution as api are not thread safe, so the session will have to be created for each thread.overall though, my suggestion would be to use either a docker or a vm , where you can spawn a python process for each action you want to use, and potentially monitor themthrough supervisor or a similar process , so if any dies it'll restart automatically.As you stated , running more of the single event won't work as it will register more than one.hope it helps.L.

Hi @Alican, although api3 have been tested only on 2.7, 3.6 and 3.7, this error is usually given when the api are not properly installed with all their dependencies. I'd suggest looking at this post and try the suggested procedure to install the api with pip , through git. If you still have issues, please let us know! Cheers. L.

Hi @John, encode_media does not currently support image sequences, only singe image or movies . you can find more information about this method here hope it helps. L.

Hi @Konstantin Maslyuk yes we are currently working on that repository for some upcoming features on integrations, but is far from being usable. Regarding your note on the QApplication is something we'll also be looking into as soon as its more stable. Stay tuned L.

HI, since 2018 the Nuke Studio integration has been revamped with new set of features. You can find the updated documentation here And here you can get access to the latest and greatest version. Hope it helps. L.

Hi @Duncan, if you want to have statuses changes to persist, you have to remember to commit your session. Overall you can find a similar example on our recipes repository. Hope it helps. L.

hi @Phil Franjo, although with different scope , there's an example to monitor status changes through the events here : https://bitbucket.org/ftrack/ftrack-recipes/src/master/python/events/cascade_status_changes/ Being event based (hence real time) won't act retroactively , this is something you can implement as one off script on the same logic. Hope it helps. L.

Hi @Jed Frechette , the Py3k branch didn't get much of an update as we have not found any issue so far , but neither we heard users reporting using it. We do have testing on the latest python versions and lately tested on Blender 2.8.x (the only DCC which provides Py3k to my knowledge) and seems to be working fine there as well, but of course automated testing and light testing on just one DCC app does not provide full insights on whether something have been missing or not working properly to replace the current stable version. Siggraph wise, we wanted to start providing updates , but we've been kept busy with other things and we have not managed to find time to address proper time to push this forward, but this is something we'll definitely doing now that we are all back from the summer break. We are mostly waiting to have users reporting its testing so we can move forward. If you had a chance to test I would like to hear more from you ! (feel free to do so through support channel if you prefer ! ) Cheers. L.

If you want to do it the ftrack way, I'd suggest let ftrack do the versioning . to get more information on how to properly publish version please have a look in our api docs: http://ftrack-python-api.rtd.ftrack.com/en/stable/example/publishing.html Hope it helps. L.

Hi @Tom Mikota, although we allow to take control the versioning system this is something I would highly discourage of doing if not for extreme and well planned cases, as it would risk to compromise your versions consistency. Is always better let have ftrack come up with the right version at publish time. (more than one user could be in the process of publishing the same version , hitting a conflict !) . If you want go ahead anyhow here is a little snippet for you to use (again please be careful), to publish a new version under a shot: import ftrack_api s = ftrack_api.Session() asset = s.query('Asset').first() shot = asset['parent'] status = s.query('Status').first() version = s.create('AssetVersion', { 'asset': asset, 'status': status, 'comment': 'Added more leaves.', 'task': shot, 'version': 1000 }) s.commit()

Glad to hear ! If there's anything else we can help out with , just let us know ! L.

Hi @John Su, please have a look in the sources of the session : https://bitbucket.org/ftrack/ftrack-python-api/src/1f20fcd0f68d2db5188c995d1b5a34791dd7c066/source/ftrack_api/session.py#lines-263 Hope this clarify further how the environment are handled without connect running. L.

Hi @John Su the environment variables (guess we are still referring to FTRACK_EVENT_PLUGIN_PATH ) is only handled locally by the session object of the api, and does have nothing to do with the path resolution itself. This environment variable will tell the local event hub where to pick the plugins from. One of this plugin is the resolved which , once loaded, will respond to an event emitted from the server, returning the resolved path. >> but in this case ftrack-python-api doesn't get chance to do the work I'm not sure I'm getting this.... The ftrack-python-api (session) are used as part of the resolved itself, to return the resolved path to the server. https://bitbucket.org/ftrack/ftrack-connect/src/80850248fc57c232fa6267bfdeb87f3d3427b706/resource/hook/resolver.py#lines-30 If you need more information on how the session and the event hub works I'd suggest digging into our docs : http://ftrack-python-api.rtd.ftrack.com/en/stable/handling_events.html L.

Hi @John Su , The web browser obviously does not know nothing about your local environment variables. These are used only from ftrack session (ftrack-python-api) and ftrack connect to discover their plugins. The resolution server side is done through the ftrack event system which will instruct the server (through the socket) on how to handle the final path rendered in the ui. Hope it helps. L.

Hi @John Su, For what I can see it seems you don't have installed ffmpeg on the server, can you please double check ? On this subject you can find more information on our documentation: https://help.ftrack.com/en/articles/1040538-installing-ffmpeg-and-ffprobe Hope it helps! L.

hehe, that's what comments are for Glad you sorted it ! Cheers. L.

Great, let us know if you find any issue ! Cheers. L.

Hi @Tom Mikota, glad to see you managed to get your head around the query system ! overall to keep in mind: <query>.all() --> return all result or an empty list <query>.one() --> return the result or error if not found <query>.first() --> return the result or None if not found You can find more details in our api documetation Hope it helps. L.

Hi @Tom Mikota it seems the root logger is set to debug somewhere. you can try for now to set this on top of your script: import logging logging.basicConfig(level=logging.INFO) Hope it helps. L.

Hi @Tom Mikota I know well what you are doing as I've been doing this with Ffmpeg before and I can confirm all works as it should. My suggestion is to produce two videos, one prores 4XX for local review purposes and one mp4 for web review. To manually set the video you can use this : http://ftrack-python-api.rtd.ftrack.com/en/stable/example/web_review.html?highlight=upload which won't re encode it . Hope it helps. L