Lorenzo Angeli

  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Lorenzo Angeli

  1. Hi @Milad Entezami, I see your concerns. I think is good to have these duplicated though, as once in a project they will start evolve on their own. With this solution you can publish back the new result in the library later on as separate (new) asset or as a new version (updated) of library one. hope it helps. L.
  2. Although not web based, one option I can think of would be : 1) have a project to act as library, 2) one action which allows to re migrate the assets to/from a given project . (could be a reworked version of this example: https://bitbucket.org/ftrack/ftrack-recipes/pull-requests/4) This could be extended to keep reference (as metadata or custom attribute) on where the asset originally comes from (as project when publishing back). 3) a pyside based browser (so can be used as widget in maya, nuke and any other qt based application) to act as library browser. Although requires some work, seems doable. L.
  3. Hi, the best option to review the images as they are, would be to use a player such as rv or hiero player, which can open the local image sequences. To be honest, encoding a good quicktime and push it as it is without re encoding it is something I have found as a good solution as well, also because allow "remote" review, which frames, does not. Here some more info on how to upload without re encoding http://ftrack-python-api.rtd.ftrack.com/en/stable/example/web_review.html?highlight=review Hope it helps ! L.
  4. Hi @L Smallwood you can find an example on how to build url path here : https://bitbucket.org/ftrack/ftrack-connect-pipeline/src/b7043ae2cd364a4637bf7efbf359087ac404ca1e/source/ftrack_connect_pipeline/ui/publish/workflow.py#lines-374 but this is basically to what boils down to: '{server_url}/#slideEntityId={version_id}&slideEntityType=assetversion&view=versions_v1&itemId=projects&entityId={project_id}&entityType=show' you'll need to format with : server_url, version_id and project_id Hope it helps.
  5. Hi @cschnell, I'm sorry, but looks like that at the moment you cannot compare different attributes in a filter expression. Being an interesting feature to have I pushed to the other developers as feature request. Hope it helps. L.
  6. Hi Thorsten, there are some news regarding api and support for py3k. We have been opening a new forum section to provide early access (with instructions and warnings) to the development branch which provide support to python 3.6 , how to install and test. If you have a chance to test, please share there your finds in there! Cheers. L.
  7. Please note, the current development status is in Beta stage and is not suitable for production. Welcome to the ftrack-python-api tech preview for python 3.x compatibility. Here are some brief instructions on how to start testing the upcoming release of the new API. We strongly recommend sandboxing the testing environment using virtualenv. Prepare your sandbox Create a virtualenv with the Python 3 interpreter: $ virtualenv -p `which python3.6` ~/ftrack_python_api_py3k Activate virtualenv: $ source ~/ftrack_python_api_py3k/bin/activate Install Install from the development branch: $ pip install git+https://bitbucket.org/ftrack/ftrack-python-api.git@backlog/ftrack-python-api-compatibility-with-python-3 Test Run python from virtualenv and check that everything is in place: (ftrack_python_api_py3k) $ python -V (ftrack_python_api_py3k) $ Python 3.6.5 You can now start the Python interpreter and start using the API as usual. >>> from ftrack_api import Session >>> session = Session() >>> projects = session.query('Project').all() >>> print(projects) If you need to use the Python3 and the ftrack module just run Python directly from the virtualenv using: $ ~/ftrack_python_api_py3k/bin/python3 -c "import ftrack_api;print(ftrack_api.__version__)" Bug reporting Please use this thread to report issues and bugs. When reporting bugs, please remember to include: * Operating system in use. * Python version in use (use: python -V). * Full stack trace or error.
  8. Hi @Jay Roth, would it be possible to send to support the log file so we can have a further look in what might be happening ? You can find here the troubleshooting guide for c4d . Cheers. L.
  9. Hi @fooopa and welcome back to ftrack folder structure is somewhat tricky to generalise for every user case, that's why our is customizable from the end users to fit their needs. You can find a complete example in the ftrack-recipes repo, from there you'll be able to decide how and where files will be stored and named. Keep the location's api documentation at hand while looking into the code as it might come at hand for the terminology. If you feel like ftrack is limited for what concerns interaction and customisation, please keep in mind that any operation with ftrack entities can be driven through event system: In the same recipes repository, you can find a good example on how to create an action that extracts data and produce a downloadable excel file. If you have any issue or doubt with it please let us know. Cheers. L.
  10. Hi @dthomlison depending on your operating system the folder containing the actions, could be in different places: OS X: ~/Library/Application Support/ftrack-connect-plugins Windows: C:\Documents and Settings\<User>\Application Data\Local Settings\ftrack\ftrack-connect-plugins Linux: ~/.local/share/ftrack-connect-plugins get to the folder , depending on your Os , and remove the actions. if you are still having issues please let us know. Cheers. L.
  11. Hi ftrack-connect-package gets shipped with its own python interpreter. looks like the python you are running lacks of the ssl support: >> SSLError: Can't connect to HTTPS URL because the SSL module is not available. you might have to rebuild python with it. hope it helps. Cheers. L.
  12. Hi Timofey, if you are using connect, click on the system tray icon and then Open plugin directory. in there you should be having the actions code, removing or moving it to another folder should resolve your issue. if you have any issue know ! L.
  13. Hi @hulmanen, sorry to see you are having issues. I've been able to replicate the problem and it seems to be coming from missing library in Nuke Studio. In order to confirm, can you please check if in your console you get this error ? /usr/local/Nuke11.2v3/QtWebEngineProcess: error while loading shared libraries: libQt5WebEngineCore.so.5: cannot open shared object file: No such file or directory Looks like Foundry is aware of this (Ticket #334788). You can check the status of this ticket here : Hope it helps, we will follow up with Foundry and see by when they'll be able to provide support. Cheers. L.
  14. Thanks Laura, we'll be having a look and get back to you. If you are using legacy api thought I would suggest start looking on how to port it over the new api code. You can find a good example here: https://bitbucket.org/ftrack/ftrack-example-location Cheers. L.
  15. Hi Laura, I'm sorry to hear you are having issues. If the custom location gets picked up by interactive maya and it can publish correctly, should work from within a batch session as well. Are you using the new python api to register the location or legacy ones ? Would it be possible for you to share the code you are using to register the new location ? If, for privacy reasons you cannot post it here, feel free to open a ticket at support@ftrack.com and share it there. Cheers. L.
  16. Hi @hquintanaro Are these error coming from the ftrack-connectg-package you have been dowloading from https://www.ftrack.com/en/portfolio/connect ? ftrack-connect-package (on linux) should be able to run centrally, but is suggest first to test it locally. If you do have errors try to see if you have any missing library regarding ssl. Cheers. L.
  17. 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 ?
  18. 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.
  19. 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.
  20. Cheers ! Let me know if you have any other issue or question.
  21. 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.
  22. 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.
  23. 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.
  24. Hi Robin ! Although totally doable , with an event that intercept the publishing event and update a folder with a symlink , or copying to the latest version, this is not something I would suggest doing. When you embrace an asset management system you should almost forget the file system structure and rely on the server queries* to see what's the latest/current version. This because latest or current, could not be the latest published but , possibly , the latest approved, or not even on the same disk. If you always have to rely on latest published, my suggestion would be to code a small tool to pick the latest published through the api only. Hope it helps. If you have any other question, please let us know ! L. * eg: the file system where assets are published is not available to the artists to look into, or based on id rather than names, so the published files cannot be modified.
  25. Hi Tuan, Ftrack default (storage scenario / default structure) file system structure is sanitised in order to work in mixed operating system environment. here where does happen: https://bitbucket.org/ftrack/ftrack-python-api/src/c2fcbca6f8a957a423f6bc2f2bde768a0d8e50b6/source/ftrack_api/structure/standard.py#lines-126 The best solution you have to get this as you like, would be to create a custom location + structure. If you want to dig deeper on how to create custom location (and structure), have a look in here : http://ftrack-python-api.rtd.ftrack.com/en/stable/locations/overview.html?highlight=structure http://ftrack-python-api.rtd.ftrack.com/en/stable/locations/tutorial.html Hope it helps ! L.