Lorenzo Angeli

Administrators
  • Content Count

    145
  • Joined

  • Last visited

  • Days Won

    9

Everything posted by Lorenzo Angeli

  1. HI @Dimitri Lucy, glad to hear ! let us know if anything else comes up L.
  2. Hi @Dimitri Lucy, whenever you are manipulating the PYTHONPATH I suggest extending it rather than overwriting it with something like : PYTHONPATH=%PYTONPATH%:C:\Python27\Lib\site-packages\ftrack_api On the error you are having though, seems to me that you are installing the new api , but trying to import the legacy ones. Could you please try to import ftrack_api rather than ftrack ? Let us know how it goes ! Cheers. L.
  3. HI @Mani Varma, If all you need is an efficient api to represent a tree I'd suggest having a look at this widget from connect. It does use a qtmodel which is quite efficient. Hope it helps. L.
  4. HI @Milan Kolar, Thanks for reporting it. I wasn't aware you were already using it ! Be aware that some breaking changes (session won't connect automatically to the event hub) are coming soon on the story branch so be careful. Feel free to get in touch through support to share any stack trace you might be getting. Cheers. L.
  5. Hi @Julian Martinz looks like we are on the same page now let us know how it goes! L.
  6. Hi @Julian Martinz, you cannot create two locations with the same name that would confuse the system. The idea of the proxy is exactly for this reason, the proxy will have your old name to match (studio.server1), where the underlying (proxied) locations will retain the different behaviour (studio.server1.managed, studio.server1.unmanaged) and the logic in the overwritten methods of the proxy location will dictate what component to handle with what location. Hope it helps. L.
  7. We have been restarting the work on the Python api with Python3k support. There's a new branch ( backlog/api-2.0/story ) to use to pick the latest and greatest, and it'll be used until the official release. Here how to update the above snippets to use it: ./pip3 install git+https://bitbucket.org/ftrack/ftrack-python-api.git@backlog/api-2.0/story If you do have any question of you find any issue please let us know.
  8. >> What would work is creating two distinct locations studio.server1 and studio.server1.unmanaged. Hi Julian, my suggestion of having a third location acting as proxy was coming from the idea of leveraging two different location with different behaviour. This though , requires to have clear rules on how these two locations will accept data (eg: image sequences -> unamanged, maya files-> managed.) >> Is there any way to revert a location instance back to the state it was before mixin in the unmangedLocationMixin? Not that I'm aware of tbh.... the above solution was though to be able to provide both at the same time. >> reconfigure my locations by emitting an 'ftrack.api.session.configure-location' event. This is something should be called when initialising the session not sure doing it programmatically would provide the results you are after. L.
  9. Hi @Jakub Trllo, you have almost answered yourself the question: >> It's probably because every time is used `custom_attributes` key on entity, api is querying values of custom attributes? It is quite possible that is what causing your slowdown. If you don't need / care about what the previous value was you can think of turning off the auto_popluate using the context manager for it. You can find further information here. Let us know how it goes! L.
  10. Hi @Julian Martinz , we'll be looking soon on providing something off the shelf. Your approach seems the on the right track though ! L.
  11. Hi @Julian Martinz if you want to use either one or the other in the same project you might have to think of creating what I would call a proxy location. This location would accept both (or more) the locations you want to use and through logical gates you can redirect the publish to what you want, either based on task, component or any other logic that suits you. Hope it helps. L.
  12. Hi @narvi, the latest perforce location plugin can be downloaded from this address. For what concerns S3 there's an example built on top of the legacy api here but still has to be ported to the new one. This is something on our todo list to port it over. Hope it helps. L.
  13. Lorenzo Angeli

    0.7.0

    Windows, Linux, Osx Download 0.7.0 Documentation Changes since last version changed : Pip compatibility for version 19.3.0 or higher. changed: Defer the Qt import when loading scenario. new : Use Qt.py instead of the bundled QtExt with Connect. new : Support publish of file sequences. fixed: Perforce modules cannot be imported and used in DCC application. new : Provide default file encode mapping based on the file extension. new : Enforce perforce username to be the same as the ftrack user logged in. Requirement Accessible Helix Server What to expect to work Storage setup User preferences setup Publish Versioning Aim for testing Publish from any application Import/Update version through connect's asset management system Known Issues and limitations There are known issues at the moment with Nuke Studio integration.
  14. Hi @narvi, there was , in the old api , an ftrack s3 accessor to make you able to move data in an out from there, but this is something we have to look back into and port over the new api, hopefully we'll be able to schedule this sooner rather than later. (contributions are welcome though ) Perforce wise, is coming. It does work as a normal ftrack storage , hence is client side but do not require local installation of the server . If you have any more questions please let us know. Cheers. L.
  15. Hi @Jakub Trllo, hierarchical attributes are tricky. Hope this snippet can help you out. If case does not let us know! Cheers. L.
  16. Hi Julian,if you have long running jobs, the best option you have is to actually use multithreading from within the action ,just be careful to use this solution as api are not thread safe, so the session will have to be created for each thread.overall though, my suggestion would be to use either a docker or a vm , where you can spawn a python process for each action you want to use, and potentially monitor themthrough supervisor or a similar process , so if any dies it'll restart automatically.As you stated , running more of the single event won't work as it will register more than one.hope it helps.L.
  17. Lorenzo Angeli

    2.2.3

    Download 2.2.3 What's new´╗┐ Fix: Improve render task deduplication logic. Fix: Integration fails to start on nuke >= 12. Fix: Thumbnail frame is now generated from the mid frame of the exported clip. How to install stop ftrack-connect-package remove previous nuke studio plugin from : <ftrack-connect-package>/resource/connect-standard-plugins/ download and uncompress the new version in : <ftrack-connect-package>/resource/connect-standard-plugins/ restart ftrack-connect-package´╗┐
  18. Hi @Alican, although api3 have been tested only on 2.7, 3.6 and 3.7, this error is usually given when the api are not properly installed with all their dependencies. I'd suggest looking at this post and try the suggested procedure to install the api with pip , through git. If you still have issues, please let us know! Cheers. L.
  19. Hi @John, encode_media does not currently support image sequences, only singe image or movies . you can find more information about this method here hope it helps. L.
  20. Hi @Konstantin Maslyuk yes we are currently working on that repository for some upcoming features on integrations, but is far from being usable. Regarding your note on the QApplication is something we'll also be looking into as soon as its more stable. Stay tuned L.
  21. HI, since 2018 the Nuke Studio integration has been revamped with new set of features. You can find the updated documentation here And here you can get access to the latest and greatest version. Hope it helps. L.
  22. Hi @Duncan, if you want to have statuses changes to persist, you have to remember to commit your session. Overall you can find a similar example on our recipes repository. Hope it helps. L.
  23. hi @Phil Franjo, although with different scope , there's an example to monitor status changes through the events here : https://bitbucket.org/ftrack/ftrack-recipes/src/master/python/events/cascade_status_changes/ Being event based (hence real time) won't act retroactively , this is something you can implement as one off script on the same logic. Hope it helps. L.
  24. Hi @Jed Frechette , the Py3k branch didn't get much of an update as we have not found any issue so far , but neither we heard users reporting using it. We do have testing on the latest python versions and lately tested on Blender 2.8.x (the only DCC which provides Py3k to my knowledge) and seems to be working fine there as well, but of course automated testing and light testing on just one DCC app does not provide full insights on whether something have been missing or not working properly to replace the current stable version. Siggraph wise, we wanted to start providing updates , but we've been kept busy with other things and we have not managed to find time to address proper time to push this forward, but this is something we'll definitely doing now that we are all back from the summer break. We are mostly waiting to have users reporting its testing so we can move forward. If you had a chance to test I would like to hear more from you ! (feel free to do so through support channel if you prefer ! ) Cheers. L.
  25. If you want to do it the ftrack way, I'd suggest let ftrack do the versioning . to get more information on how to properly publish version please have a look in our api docs: http://ftrack-python-api.rtd.ftrack.com/en/stable/example/publishing.html Hope it helps. L.