-
-
Notifications
You must be signed in to change notification settings - Fork 320
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
Consider / propose as option / default to new lossy GIF encoder lossygif #291
Comments
Lol :) But yes, definitely. My main concern right now is how to structure the settings. I want to make it easy for the user to choose between different options without requiring extensive research. |
@phw cool; good point, UX/discoverability matters! Thanks for the continued work on Peek 🙂. |
The settings can be reduced to:
|
have you tested if lossygif also brings big advantages for "common" screen captures? as i understood the article i've read, it was mainly for compressing movie snippets (as in the example above)... |
It does help with screenshots a bit too, since anti-aliasing, icons and gradients can be lossily-compressed. |
@kornelski Thanks for the input. I did some initial testing with a quick 15 seconds screen recording, converting a intermediary video file as generated by Peek with the options used by Peek. The video itself is a screen recording of this github issue tracker, so plain color areas, not too many colors (not the area where e.g. gifski shows its strength). The video frames are extracted to single files using ffmpeg and converted to gif using ffmpeg, gifski, gifsicle and giflossy. The file sizes:
Now I can use gifsicle / giflossy as a postprocessor on those outputs to further optimize them: For ffmpeg:
For gifski:
So using giflossy would really bring the file size down significantly when using ffmpeg. It ads some extra post processing time, but I haven't done any measurements on this. If only gifsicle is available it doesn't help that much. Also adding giflossy as a post processor to gifski does not help much, but that was kind of expected. I tend to just use giflossy if available as a postprocessor by default, and maybe add an option to disable it. Here is the smallest of the files I could generate: |
It's that time again! (see #212 🙂). @pornel of ImageOptim/PNGQuant/gifsky fame just released a first version of lossygif (website, github). Quoting the website,
Would be awesome for Peek to be able to directly use it. As an option and maybe even by default, as it seems to output good-quality but very compact GIFs.
The text was updated successfully, but these errors were encountered: