Jump to content

Lorenzo Angeli

  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Lorenzo Angeli

  1. Hi @intelyuxiang at the moment the only asset type allowed to be published are the image_sequences. We have now uploaded the technical documentation , please have a look a the trubleshooting page. Please rest assured we are actively looking on a potential fix. L.
  2. Hi @Konstantin Maslyuk just saw the PR , thank for it. We'll review whenever possible . Cheers! L.
  3. hi @Konstantin Maslyuk please feel free to fork the api and provide a PR against our repo ! more than interested to look into it. Thanks!
  4. Download 1.2.3 What's new New Provide output log file in default location. Fixed Do not look up for frame information when importing mov files. Changed Update pyside signal signature for pyside2 compatiblity. 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
  5. Download 2.3.0 What's new Fixed Custom start frame are not consistently output in frame sequence. Changed Lock OTIO dependency version to last python only. Fixed Sequences rendered with Nuke Studio cannot be imported in nuke. Fixed ImageSequences are rendered as FileComponent. Fixed Thumbnail generation breaks when exporting just nuke scripts. 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 versio
  6. Hi @Spencer, have you been checking on our API help ? Hope it helps. L.
  7. Hi @daansQt5 is currently not supported . We are working on that but there's no ETA atm I can provide I'm sorry. Unless you can find a way to install Qt4 on pop!_os I fear you are on a dead end for now. L.
  8. hi @daans, my suggestion would be to try to install in a virtualenv ftrack-connect from sources. the process would be something along these lines: 1) ensure you have libssl and qt are installed and available on the system 2) create a virtualenv for python 2.7 (python > 2.7.9) 3) clone ftrack-connect repository https://bitbucket.org/ftrack/ftrack-connect 4) activate virtualenv 5) run : python setup.py install if everything went well, you should now be able to run : ftrack-connect from the shell. Let us know how it goes! L. P.s Differently from ftrack-connect-p
  9. @Andrea Perisano I've been checking an on the upcoming release we are already set to use Python for unity api 2.0 . Stay tuned for more info. L.
  10. Hi Andrea, the unity integration is not officially out yet and we are still working on it. I'll be raising this api version issue internally and let you know. Thanks. L.
  11. Hi @Konstantin Maslyuk seems most of the time is spent on the json encoder, interesting. Can you provide what python version are you using and some code to replicate the profiling ? Thanks. L.
  12. Hi @John , if you want to remove the component and free up the space, you can use the <location>.remove_component(<component>) hope it helps. L.
  13. RC6 is now available on pypi and can be installed with : pip install ftrack-python-api==2.0.0rc6 What this version fix or improve: Event server wait method will sometimes raise a connection error because of a race condition. Improve testing
  14. Hi all, a new RC version (4) is out for testing.... this version introduce the fix for the issue @jen_at_floyd has been reporting above about SSL connection. You can install the new version as usual with : pip install ftrack-python-api==2.0.0rc4 Another step closer to the final release, please test and report if there's any issue! Thanks. L.
  15. @jen_at_floyd we are looking on adding your proposed fix (with few changes) to the api 2.0 branch. If you want you can test this before cloning the repo , changing branch and installing it into a virtualenv. This fix is likely to end up in the api 2.0 branch soon though, let us know in case you test. Cheers. L.
  16. Glad to hear @Konstantin Maslyuk ! The branch still requires some tweaks and details, but should soon get to master. More news and info on the branch itself L.
  17. @Konstantin Maslyuk I've now made so calling build_ext use the same command as Build hence building the missing resource.py, hope this ease your problem. This is what I'm doing for testing create a new virtualenv (I personally use mkvirtualenv wrapper) activate virtualenv go with the shell in the ftrack-connect repo folder and checkout the given branch (and pull) run to install in editable mode : pip install -e . run ftrack-connect : ftrack-connect here the versions of the basic moving parts I'm using: python : 2.7.
  18. Hi @Konstantin Maslyuk I've just been pushing a new commit on the above PR to ensure you can install qtext in build_ext command. Please pull again and give it a go. let us know how it goes. L.
  19. Hi @jen_at_floyd, thanks a lot for raising this issue and providing a potential solution. We'll be looking on whether this is something we can push upstream on the final release ! Cheers. L.
  20. Hi @Konstantin Maslyuk although not tested, connect should be able to support pyside2 though our QtExt layer, but has not been reviewed for supporting Python 3k atm. I'll be double checking the build_ext functionality in the above branch, keep monitoring it. > The rest is fine, i used docker/ubuntu:18.04. connect is currently tested and built for centos 7 , I've not much of an experience on Ubuntu, so not sure what packages are available and to what version. for this error: > distutils.errors.DistutilsError: Could not find suitable distribution for Requirement
  21. Hi @Konstantin Maslyuk, this is something I need to double check as I usually go for using pip to install dev versions with : pip install -e <path to repo> regarding connect there's a branch I'm looking into these days similar to your request: https://bitbucket.org/ftrack/ftrack-connect/branch/backlog/review-standalone-install try to give it a go and let me know. Cheers. L. p.s Jinja 3 is not a requirement of ours, is likely coming as sub dependency of sphinx or something similar. if you have a chance to pin down the offending module version let me know.
  22. New RC version is out for testing.... this version introduce a better check for remote event server connection while listening to events. you can install the new version with : pip install ftrack-python-api==2.0.0rc3 We are getting close to a final release, please report any issue you may find during the RC release phase !
  23. Thanks to all your feedback and bug reports, we are finally getting closer to a final release of the upcoming api 2.0 for python2/3 . If you want to install (at your own risk) the latest RC2 version please use the following command: pip install ftrack-python-api==2.0.0rc2 Full change log can be found here please report through the usual channels any issue or bug you might be finding. Cheers. L.
  24. I'd suggest to stick to C7 as long as possible atm. By direct experience C8 is not ready yet for production. L.
  25. @Nero Demaerschalk, Centos 8 is something we'll be looking into as soon as the distro is stable for desktop use (I'd suggest waiting more than .1 release) For python3 we have a dedicated thread in the forum at this address, feel free to test and let us know if you find any issue. We are working in these days to release a new api 2.0 for python 2 and python 3 for wider use, but the inclusion in connect will require more time due to some non backward compatible changes in the api. Hope it helps. L.
  • Create New...