Lorenzo Angeli

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!

Download 2.0.0RC1 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 versions! 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. Aim for Testing: Nuke Studio / Hiero versions : 9.X , 10.X , 11.X External Frame server Project creation Task Creation Track rebuild Versioning Known issues and limitations: Tasks and processors are not yet customisable. ftrack task type and asset types are not yet customisable. Nuke export / Notes is not assetised. Note: Due to the continuous changes to the path management, using previously saved presets makes the integration break.

Download 2.0.0c1 Requirements: Centralised storage scenario or a custom location available and working. What to expect to work: Create project structure on server 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 Aim for Testing: Nuke Studio / Hiero versions : 9.X , 10.X , 11.X External Frame server Project creation Task Creation Known issues and limitations: Clips should be named <SEQ>_<SHOT> to be exported Use : Right Click -> Editorial -> Rename Shots Tasks and processors are not yet customisable. ftrack task type and asset types are not yet customisable. Nuke export / Notes is not assetised. Versioning is not working yet

Download 2.0.0b1 Requirements: Centralised storage scenario or a custom location available and working. What to expect to work: Create project structure on server 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) Aim for Testing: Nuke Studio / Hiero versions : 9.X , 10.X , 11.X External Frame server Project creation Task Creation Known issues and limitations: Clips should be named <SEQ>_<SHOT> to be exported Use : Right Click -> Editorial -> Rename Shots Tasks and processors are not yet customizable. ftrack task type and asset types are not yet customisable. Nuke export / Notes is not assetised. Published clips are not updated in timeline.

Answered in support case, but here for reference: For what concerns location accessors, is pretty doable to write S3 and Azure ones (it has already been done before), you can find further information looking into the api: https://bitbucket.org/ftrack/ftrack-python-api/src/master/source/ftrack_api/accessor/ If the cloud storages provide a python api access (eg: boto for Amazon S3) and using the base accessor ( https://bitbucket.org/ftrack/ftrack-python-api/src/master/source/ftrack_api/accessor/base.py) as baseclass , is just matter of fully re implement the various method exposed. Although I would suggest to use these as a mid ground storage and keep the production files locally to the office and use these other locations just for transfer, this would allow you to get the best of both worlds. Hope it helps. L.

Hi Reynaldo, answered in support case, but for reference: Although the official support for python 2.X is set to 2020, DCC company applications (Autodesk, Foundry etc...) will slowly move over. During last year's Siggraph we've been discussing with them and through the https://www.vfxplatform.com it has been decided to start putting ahead a 3.6.X but is not been nailed yet, and therefore it'll likely take way longer to get fully adopted by the industry (I'm expecting a delay of at least 2 years.) To be honest I would avoid moving to py3 before all the DCC apps have been doing it. If you are interested though, you can find our (not ready to merge, therefore not supported officially yet) branch for py3k compatibility here: https://bitbucket.org/ftrack/ftrack-python-api/pull-requests/191 Hope it helps. L.

Download 2.0.0a1 Requirements: Centralised storage scenario or a custom location available and working. What to expect to work: Create project structure on server Validate against selected project schema 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) Aim for Testing: Nuke Studio / Hiero versions : 9.X , 10.X , 11.X External Frame server Known issues and limitations: Clips should be named <SEQ>_<SHOT> to be exported Use : Right Click -> Editorial -> Rename Shots Tasks and processors are not yet customizable. ftrack task type and asset types are not yet customisable. Nuke export / Notes is not assetised. Published clips are not updated in timeline.

Please note, the current development status is in Beta stage and is not suitable for production. Welcome to the new integration forum for the new ftrack connector ! This new integration aims to unify Nuke Studio / Hiero and be as close as possible to the original application workflow, making the user familiar in its usage. The new integration is packaged as a native ftrack plugin, ready to be dropped in to place. This forum will be providing a topic for each release and provide a download link for each build. Each topic version will be used to discuss bugs and feature requests. You can subscribe to this forum section to receive a notification when a new build is added. We recommend you use the latest build when available. Features and releases. Development will follow these priorities: Create and update projects and tasks Rebuild tracks and version Customise and improve UI Allow users customisation Install To install, download the zipped file from the correct version and follow these instructions to get to the plugin folder, then decompress the zip in there. Build If, instead you want to build from sources, clone the correct branch and run python setup.py build_plugin Bug report When reporting bugs, please remember to include: log file nuke version connect version any stack trace or error you are receiving

Cheers ! Let me know if you have any other issue or question.

Hi Kristing ! I've been looking now at the example you posted, and looks like it's missing something in order to cope with what you are after. Here how I got it working. In: ~/.local/ftrack-connect-plugins/testactions/hook * first.py * second.py each of these files contains a copy of the linked example. Here is how the classes are initialised: class MyCustomAction(object): '''Custom action.''' label = 'My Action' identifier = 'my.custom.action' description = 'This is an example action' variant = 'first' class MyCustomAction(object): '''Custom action.''' label = 'My Action' identifier = 'my.custom.action' description = 'This is an example action' variant = 'second' Then change in (both) the discover function to include the variant : return { 'items': [{ 'label': self.label, 'description': self.description, 'actionIdentifier': self.identifier, 'variant': self.variant }] } rather than : return { 'items': [{ 'label': self.label, 'description': self.description, 'actionIdentifier': self.identifier, }] } If you then restart connect , this is how the action should show up: To simplify further though, I would also suggest you to have a look at : https://bitbucket.org/ftrack/ftrack-action-handler Which aims to simplify the implementation of custom actions (http://ftrack-action-handler.rtd.ftrack.com/en/stable/). Please let me know if you have any further issue or questions. Cheers. L.

Cheers Scott, do you mind linking the thread on thinkbox forum ? So I can read and, in case, follow up ? If you have some development knowledge, or you have developers available, you can think of customising their code.(ps. sadly cannot find it on the github repo : https://github.com/ThinkboxSoftware/Deadline) Thanks. l.

Hi Scott, Deadline integration is maintained by ThinkBox itself, and I've not much direct experience with it. Regarding your issue though, the options :Submit Render Layers As Separate Jobs is enabled. sounds fishy, as is likely to generate one job (and therefore a new asset) for each layer. To me the best option would be to have 1 asset (Render) with all the render layers / passes published as components of the given asset version so would easy to know where they come from. e.g: ``` City (Render) v010 - diffuse: <path to diffuse pass> specular: <path to specular pass> <other_render_layer_name>: <path to other pass> ``` and so on. I'll try to dig deeper as soon as I have a chance in this integration and try to get a better grip on how could be improved. Let me know how it goes please. Cheers. L.