Lorenzo Angeli

Hi @Henrik yes, that's correct. I cannot provide any ETA , but I've been taking note of the above request and added it in out feature tracking tool. Cheers. L.

Hi @alexisp could you please create an api user with explicit access to the private project and use that api key to create the session ? you can find more information in our help page: https://help.ftrack.com/en/articles/3004264-private-projects hope it helps. L.

Hi @Henrik, you can use custom attributes in expressions, but you can only reference attributes available on the entity itself, using self. you can see that in action for the duration : {self.fend - self.fstart + 1} here you can find more information about custom attributes and expression https://help.ftrack.com/en/articles/1040474-using-custom-attributes#expression-attribute hope it helps. L.

@Henrik check your inbox, have just been sent.

Hi @Brian, as you are provided with the id , you can use entity = session.get('Context', "<id>") print(entity['name']) let us know if this is what you are after. Hope it helps. L.

Hi @Kmeron, you should have recevied the invitation.

Hi @TeJa TJ to see when a custom attribute has been last changed you can query the Event entities as such: custom_attribute_events = session.query(select insert, parent_id from Event where insert is "update.custom_attribute" and parent_id is "<your-task-id>").all() this will return an Event object which will hold the timestamp on the created_at field and the previous and current value under the data field hope it helps. L.

Hi @Jan Ivar Solås I don't know much about Prism2, but In ftrack Studio you can configure the encoding quality from the Settings page. System settings ‣ ftrackreview ‣ Review settings If you want to publish using Connect , you can also take control of the encoding itself, overriding the encoding hook. Hope it helps. L.

Hi @Brad Falk following up here from the internal ticket as the solution might be interesting to others. If you want to customise the nuke studio output folder, the best option is to provide a custom template which include the entity you are missing (the folder in this case). An example template could be (please note the first {_:(FD|fd)}{Folder:\w+} which resolves the folders) { 'name': 'Custom with folders', 'description': ( 'Match and output desired structures with folders' 'Example: FDSOME_SQ001_SH010 will be matched as Folder with Name SOME , Sequence with name ' '001 and a Shot named 010.' ), 'expression': '{_:(FD|fd)}{Folder:\w+}{_:.+(SQ|sq)}{Sequence:\w+}{_:.+(SH|sh)}{Shot:\w+}' } The best way to test if the template is correct is to simply check with the underlying template engine with the following code: import lucidity string = 'FDNAME_SQ001_SH411' template = '{_:(FD|fd)}{Folder:\w+}{_:.+(SQ|sq)}{Sequence:\w+}{_:.+(SH|sh)}{Shot:\w+}' luc_tmpl = lucidity.template.Template('Custom with folders', template, anchor=None) print(luc_tmpl.parse(string)) Once the template is added to the nuke studio context_template_hook.py (note, in the installed plugin will be available under : C:\Users\<user>\AppData\Local\ftrack\ftrack-connect-plugins\ftrack-connect-nuke-studio-2.5.1\application_hook) Just restart Nuke Studio, and at export time, select the new custom template and continue the export as usual. The result structure should be similar to the image attached. Hope it helps. L.

Hi @Evan Hale if the location is found in connect, but not in the integration, is likely you are just registering just to the configure-location. Please try to add these lines too and see if does work: api_object.event_hub.subscribe( 'topic=ftrack.connect.application.launch', modify_application_launch ) # Location will be available from actions api_object.event_hub.subscribe( 'topic=ftrack.action.launch', modify_application_launch ) subscribing to these events should nake the location within the integrations too. here the location where this snippet has been taken from, so you have full reference Hope it helps L.

Hi @Brad as you have found out already , ftrack connect provides a default local path for plugins to be installed into, which is defined through the appdir module. There are ways though to override that path without having to touch the source code of connect. The easier and most suggested is to override the FTRACK_CONNECT_PLUGIN_PATH (for connect plugins) and FTRACK_EVENT_PLUGIN_PATH (for api hooks). These environment are used usually to centralise the plugins across the studio so won't have to live on local user's machines. You can find more information on the connect documentation as well as on the api one. If you want more informations or you have further issues, please feel free to open a ticket with support ! Hope it helps. L.

Hi @Brad, glad you find you way through the code and found out by yourself about the environment variable. You are right, original configs are better not to be touched due to update, and the env is there for you to customise the lauchers at your needs. We have now tracked this changes in docs and they will be updated for the next release . Cheers! L.

Hi @John Kalaigian I'm now looking into this issue. it seems to be triggered due to a miss initialization of the icons during the fist storage scenario startup. it'll be fixed in an upcoming patch version. thanks for reporting it.

HI @Evan Hale could you please post or send to support the code you are running ? The follwing snippet seems to return the availablity correctly: hope it helps. P.s Looking back at the code , the call thatreturns a dictionary is on the component and not on the location: This is because is returning the availablity for all the locations you can find the location avilability passing the location itself into the method: we'll have a look at updating the docs where needed. Thanks for reporting. L.

Hi @finnjaegger, Nuke Studio requires to have a Project set as context in order to be discovered. please have a look at our documentation and see if does help. Cheers. L.

Hi @Frank Rueter as we are still in development phase, our current RC code does not sit in the usual Master or Main branch but on a backlog/connect-2/story . If you open the commit history you can see in which feature branch we are currently working Nuke Studio / Hiero documentation are available on our help page as well as in the repo docs Hope it helps! L.

@Soal GIVORD @Hadrien FARRE As it seems you are both on Maya 2020.X could you please check if your issues are related to this maya bug ? We have many users importing and using daily our api in maya and this is the few issue we have been told so far. Please let us know if you still have issues. L.

Hi @YuChen ftrack_api refers to the latest ftrack python api, where ftrack refers to the legaci api which are deprecated by now (were supporting python2 only) hence finding the same classes (namely) on both. please use only : import ftrack_api.structure.Structure.base.Structure import ftrack_api.resource_identifier_transformer.base.ResourceIdentifierTransformer if you have any code still using: import ftrack worth looking into updating it to new api as you are likely to start finding issues , like SSL connections and such. hope it helps. L.

Hi @itotman, we do have an example event which ovewrite the publish function of connect to allow the use of ffmpeg to encode image sequences. you can find the code here but is likely you'll have to further customise it to fit your needs. https://bitbucket.org/ftrack/ftrack-recipes/src/master/python/events/encode_image_sequence/ hope it helps! L.

HI @YuChen, yes you are right. context['selection'][0]['entityType'] returns a lowercase type where you need an upper case. here you can see how we are handling it in our action handler source code. Hope it helps. L.

Hi @YuChenno worries, the ftrack-python-api 2.3.0 also run on python2.7.9+ . If you do have a file , please send it to support@ftrack.com so we can have a closer look. Cheers. L.

Hi @YuChen in order to build the entity , you can try doing the following. my_selection = self.session.get( context['selection'][0]['entityType'], context['selection'][0]['entityId'] ) hope it helps. L.

Hi @YuChen part of the work done on Connect for the 2.0 release has been moving out the application module out of connect into a dedicated plugin called ftrack-application-launcher which is shipped by default with ftrack Connect 2.0 . The source code can be found here Hope it helps! L

HI @YuChen and @PeterH would you mind trying updating the ftrack-python-api to the latest release version (2.3.0) This version released early this month (9Th Nov) provide a fix for your issue. Hope it helps. L.

@Vladimir Pylev if you want to use a cloud/object storage for backup or data share purposes, you can try to use the ftrack-s3-accessor written by nifty digit. At the moment I'm not aware of any accessor for google drive. if you need further info about locations I'd suggest having a look at this webinar and our api docs on Locations Hope it helps! L.