-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integration with Guetzli by Google #56
Comments
I was just about to open the same issue to investigate 😄 Seems they require 300mb per megapixel of image, which is incredibly high. The project is also written in C++ which will make it more difficult to integrate, but it should be doable. I don't have a ton of time right now but here are some things to do:
|
Yes @danielgtaylor, let me be clear that guetzli is not ready for production. It takes good amount of time, coupled with use of 5GB memory for 24MP memory(I just commented this here) makes it unusable for 32-bit systems. It's also too slow for people who process thousands of images a day. Just imagine the cost of number of servers to use. But that doesn't mean it's not useful for all. However, I opened this issue as this project is just born and will mature to address these issues. Also, please link the butteraugli enhancement issue to this. I am in same position(don't have enough time) but in case if anyone picks any requirements mentioned above, do discuss before so as to not stop on other toes/work. I will try to pick one or other requirements and will address my results here. Of course for any manual image compression analysis, go ahead and do it. Since the more manual comparison is done the better as it is subjective. Thank you. |
More info here at the official repo and the blog.
The text was updated successfully, but these errors were encountered: