Lorenzo Angeli

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

Hi, I've replied at your support ticket. A potential solution is on its way. L.

Hi @guiramalho, I'm in the process of checking if there's any better way of doing the frame extraction, but what you are seeing are the default settings used by Hiero for the PosterFrame (which is what we are currently using internally) There are various ways you can define which frame to be used for now, either on the source clips: https://learn.foundry.com/nuke/content/timeline_environment/ingest/searching_bins.htm Or on the project settings: https://learn.foundry.com/nuke/content/timeline_environment/conforming/project_settings.html I'll reply to your ticket when I've more news about updates on the code side. Cheers. L.

@John Su, I've finished off testing now the remote encoding using as example a file (ProRes HQ 422 ) I downloaded from here the encode has been done with the following code: import ftrack_api session = ftrack_api.Session() version = session.query('AssetVersion').all()[-1] version.encode_media('c://path/to/PRORESHQ.mov') The remote encoding task finishes successfully and I can play back the video in the component. Hope it helps. L.

Hi @John Su, please have a look in here, by the end you'll find instructions on how to access the logs. Cheers. L.

Hi @guiramalho , this seems to be a file from the nuke studio integration . The code for the thumbnail in there is quite simple and pick the mid frame, please feel free to drop an email to support with suggestions on how it should behave and we'll be looking into it. Cheers. L.

No python api session in browser, the information between the desktop (path) and the server will be transmitted through the event system.

Hi @John Su, I'll check this asap. Would you mind sending the logs to support@ftrack.com ? They might contain some sensible information. Cheers. L.

The environment variable will tell the session object where to pick up its plugins (the resolve in this case). The resolve will then submit to the server the information on how to represent the component path through the event I've been linking you previously. Hope it makes more sense this way. L.

Hi @John Su, sounds strange should work, but I'll double check. out of curiosity what size were these files ? Cheers. L.

Hi @John Su, you can find some more information about the plugin ftrack environment paths here. Overall though the env does not have to be known by the server as is up to the session object to discover it and put it to the use. The resolve scripts uses the ftrack events to notify the server about the resolved path of the component . ftrack event system is quite powerful and I'd suggest digging deeper looking in here. You can also find more examples on how to use events in our recipes repository. Hope it helps. L.