Jump to content

Lorenzo Angeli

Administrators
  • Posts

    275
  • Joined

  • Last visited

  • Days Won

    23

Everything posted by Lorenzo Angeli

  1. Hi @Peter Arcara thanks for reaching out and sorry to hear you have been having issues. Few questions for you to try to better help: What version of connect are you using (1.1.2 or 2.0Rc ) ? Are you launching the integration from within connect with a context (task) selected ? Is your version of houdini py2 or py3 ? What os are you on ? (guess Windows) Can you please send console logs messages and ftrack logs ? Looking forward hearing from you. L.
  2. New pipeline framework The new pipeline framework below is for the upcoming replacement for the legacy connector integrations. We're currently in heavy development so recommend it should not be used in production as breaking changes are coming. We're sharing these updates for developers to see the direction we're heading towards and the new approaches our integrations are taking. Please note, this codebase only works with Python 3 interpreter and supported applications. Core plugins These plugins are essential for the following integrations. ftrack-connect-pipeline-1.0.0rc2.zip ftrack-connect-pipeline-qt-1.0.0rc2.zip ftrack-connect-pipeline-definition-1.0.0rc2.zip Integrations: ftrack-connect-pipeline-maya-1.0.0-rc2.zip ftrack-connect-pipeline-nuke-1.0.0-rc2.zip ftrack-connect-pipeline-3dsmax-1.0.0-rc1.zip ftrack-connect-pipeline-houdini-1.0.0-rc2.zip ftrack-connect-pipeline-unreal-engine-1.0.0-b2.zip Pre-compiled plugin for latest unreal, do not use the version available on the Unreal Marketplace. ftrackPlugin-U4.26.2-1.0.zip Documentation Please be sure to go through our docs if you have any doubt.
  3. Hi all, I'm happy to announce that this release marks the end of the private beta and start of the public beta for ftrack Connect as we get closer to the commercial release. Please keep the feedback coming, I go through every one. All of your feedback helps shape the direction and path towards the final release to ensure it's suits the needs of your production pipeline! ftrack Connect beta documentation can be accessed here What's new The package has been build using the latest cx_Freeze with Docker for Linux Centos 7 and 8 and Windows. The package include some previously missing modules such as html modules, needed to run location plugins such as ftrack-s3-accessor. ftrack Connect now won't error anymore under windows if you try to use command line. Note: on CMD and PowerShell you won't get any output, please use cygwin or git shell for that. application-launcher bumped to 1.0.1 to allow nukeX execution Note: ftrack-application-launcher comes as part of ftrack Connect. If you are running from sources you can install this pre built plugin if you prefer. connect has been updated to use the latest API 2.2.0 Integrations Cinema 4d integration have been updated to ensure to run on R23+ version. Cinema 4d includes now the plugin, you can simply make Cinema point the plugin path there! Legacy ftrack-connect-<integration> Won't be included anymore in the package, but will be available for download Framework integrations are not included yet as are going though a big rework on performance and UX. please follow this forum for more updates soon! Rv plugin 5.0 can be downloaded from here Download ftrack Connect 2.0.0 Rc3 Windows (re uploaded on 15/08/2021 due to corrupted upload) ftrack Connect 2.0.0 Rc3 OSX ftrack Connect 2.0.0 Rc3 Linux C7 ftrack Connect 2.0.0 Rc3 Linux C8 Documentation: ftrack Connect (package) ftrack application launcher ftrack connect cinema 4d RV Legacy Integrations download please note these integrations are limited to py2 supported interpreters, python3 won't work. ftrack-connect-maya [1.4.0] (<=2020) ftrack-connect-nuke [1.4.0] (<=12) ftrack-connect-houdini [0.4.0] (<=18) ftrack-connect-3dsmax [0.5.0] (<=2020) ftrack-connect-unity-engine [1.1.0] (<=4.25) ftrack-connect-unreal-engine [1.1.0] ) (<=2019) If your have issues or you want to report a bug: Write to support!
  4. @YuChenCustom AttributeLinks have been introduced in 4.8 , I'd suggest reaching out to our support to get more informations on how to upgrade. Hope it helps! L.
  5. You should now be in @molsontheory
  6. Hi @Damien Keraudren if what you want is to visually collect similar actions behaviors, you can use the variant https://help.ftrack.com/en/articles/1040465-actions Hope it helps. L.
  7. Hi @Damien Keraudren you approach seems quite right to me. Would you mind sharing the discover method code so we can have a closer look ? Cheers. L.
  8. @Andy C you should be in now!
  9. Hi @db5007 the version of connect you are using does not run py3k applications such as Nuke 13 *. If you want though, we have started a beta program here in the forum where we are providing support for those. Hiero ,in the specific, is still missing but it'll come before final release. If you are interested on joining please head here and get registered ! Hope it helps! L.
  10. Hi @Rory If you haven't I'd suggest having a read on the general syntax about the query system here. And look into details about the query projections to have a better idea on how to optimisatise the queries. In regard of your question: > Certain projnames return a result id/name but others don't ? Projects (as well as any other ftrack entity type) do have some values set and available by default and defined by the server schema, such as id and others. Name can be there or not , but really depends on the entity type (eg: AssetVersion won't, Project will ) The easier way to see what fields are available is to get the keys() off the entity you just got back from the query eg: a_project = session.query('Project').first() # return only the first project found print(list(a_project.keys())) which will return all the available fields available for the project: > ['created_at', 'managers', 'calendar_events', 'color', '_link', 'full_name', 'disk', 'children', 'timelogs', 'end_date', 'parent_id', 'created_by', 'disk_id', 'id', 'user_security_role_projects', 'start_date', 'project_schema', 'metadata', 'status', 'scopes', 'project_schema_id', 'parent', 'descendants', 'thumbnail_id', 'review_sessions', 'appointments', 'link', 'is_private', 'assets', 'is_global', 'name', 'notes', 'thumbnail', 'assignments', 'thumbnail_url', 'allocations', 'custom_attributes', 'created_by_id', 'root', 'context_type'] Hope it helps. L.
  11. Hi @alexisp, at the moment there's no direct call from the api to get the review session url, but can be "easily" generated with the following snippet: import ftrack_api session = ftrack_api.Session() # Retrieve the Review Session you are interested in rs = session.query('ReviewSession').first() # Ensure the shareable link is enable rs['shareable_url_enabled'] = true session.commit() # Get the signed url from the server signed_data = session.call([{'action':'generate_signed_url', 'entity_key':[rs['id']], 'entity_type':'ReviewSession'}]) # Compose the review url shareable_url = '{}/review/{}?signature={}'.format(session.server_url, rs['id'], signed_data[0]['signed_url']) print(shareable_url) hope it helps. L.
  12. Hi @AndyMaurer thanks for sharing back the fixes. Surely will come at hand to many others to have it ! Cheers.
  13. @aline3d you should be in now!
  14. @Toby Angwin @kristin you should be in now. Sorry for the delay !
  15. Hi @MattM, One way of handling this could be to provide a secondary location (with a lower priority than you main one ) to be used to move copy the data you want to archive. Such a solution can also provide various optional features, like archiving only approved data and backup dependent components. Although at the moment we do not provide such a feature off the shelf, our api can provide you all the basic building blocks to build it. Below some resources which can help you getting a grip with those: Location : https://help.ftrack.com/en/articles/1040442-locations Location API: http://ftrack-python-api.rtd.ftrack.com/en/stable/locations/index.html Location Webinar: https://www.ftrack.com/en/intro-to-locations-webinar Actions (to trigger the data archiving) https://help.ftrack.com/en/articles/1040465-actions Actions API: http://ftrack-python-api.rtd.ftrack.com/en/stable/handling_events.html Depending on where you want to archive the data (if not on your local storage) you could also use third party accessors such as the Amazon S3 one to have cloud backups: https://pypi.org/project/ftrack-s3-accessor/ If you want to get your feet wet with Location I also suggest having a look into our Recipes repository for inspiration: https://bitbucket.org/ftrack/ftrack-recipes/src/master/python/actions/multi_site_location/ Hope it helps. If you have any further question please let us know! L.
  16. Hi @Toby Angwin , Nuke studio currently requires a fully managed location in order to work. This because we want to have the files output fully handled from the Location and structure ftrack plugin. > We are using an un-managed storage scenario as we are starting to roll out ftrack across our facility and have an existing folder structure that can't easily be changed. We'll be looking on how we provide such a feature, but cannot provide an ETA atm. One option you could look into is to convert your folder structure into an ftrack structure plugin for your location. Hope it helps. L.
  17. Hi @John Kesig thanks for the suggestion ! We usually prefer to leave these customisation to end users to better match their local workflow. Soon though, there'll be more agile ways to provide what you are after. Cheers. L.
  18. Hi @finnjaegger thanks for the links and the insights. Be ensured Resolve is well on our radar and we are looking into providing a proper integration, there's just no ETA for it. I'll be having a proper look at what resolve 17 brings as it seems quite interesting. Stay tuned! L.
  19. hi @Hadrien FARRE this error often comes from a mix up between python 3 and python2, usually trying to load python2 in python3 interpreter. Also can see you are using python 3.9 , although supposed to be working , we currently support up to 3.8 with a closer eye to 3.7. hope it helps. L.
  20. 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
  21. @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.
  22. 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.
  23. 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.
  24. 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.
×
×
  • Create New...