[GH-ISSUE #112] Which GIF encoder to be used in which situation #1469

Closed
opened 2026-03-01 18:45:44 +03:00 by kerem · 8 comments
Owner

Originally created by @panther2 on GitHub (Mar 21, 2017).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/112

There are three GIF encoders to select from: 2.0 - 1.0 - System

Are there any hints, pros, cons about when to use which encoder?

Originally created by @panther2 on GitHub (Mar 21, 2017). Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/112 There are three GIF encoders to select from: 2.0 - 1.0 - System Are there any hints, pros, cons about when to use which encoder?
kerem closed this issue 2026-03-01 18:45:44 +03:00
Author
Owner

@NickeManarin commented on GitHub (Mar 21, 2017):

2.0 = Only good if there's not so many colors on your recording.
1.0 = General use.
System = Compatibility reasons.

My idea was to completely replace v.1.0 with v2.0, but I couldn't finish to develop that encoder (with more customizations).

<!-- gh-comment-id:288050073 --> @NickeManarin commented on GitHub (Mar 21, 2017): 2.0 = Only good if there's not so many colors on your recording. 1.0 = General use. System = Compatibility reasons. My idea was to completely replace v.1.0 with v2.0, but I couldn't finish to develop that encoder (with more customizations).
Author
Owner

@panther2 commented on GitHub (Mar 21, 2017):

Thanks a lot!

<!-- gh-comment-id:288061070 --> @panther2 commented on GitHub (Mar 21, 2017): Thanks a lot!
Author
Owner

@panther2 commented on GitHub (Jun 18, 2017):

@NickeManarin

I am reopening this issue as I noticed a change with the new version 2.8:

Encoder choice is now:

stg

So again my question: Which encoder do you now recommend for which purpose?

Thanks a lot 😃

<!-- gh-comment-id:309296146 --> @panther2 commented on GitHub (Jun 18, 2017): @NickeManarin I am reopening this issue as I noticed a change with the new version 2.8: Encoder choice is now: ![stg](https://user-images.githubusercontent.com/20812775/27263430-1f26a1ae-5469-11e7-881c-674e5173dd30.PNG) So again my question: Which encoder do you now recommend for which purpose? Thanks a lot :smiley:
Author
Owner

@Riajyuu commented on GitHub (Jun 19, 2017):

@NickeManarin Why not add them to the tool tips. Now I see only 2.0 has tool tips.

<!-- gh-comment-id:309335156 --> @Riajyuu commented on GitHub (Jun 19, 2017): @NickeManarin Why not add them to the tool tips. Now I see only 2.0 has tool tips.
Author
Owner

@panther2 commented on GitHub (Jun 19, 2017):

I was under the impression that - because of the renaming from "2.0" to "ScreenToGif" - the "new" encoder was no longer "experimental", that's why I asked - but there still appears "experimental" in the tool tip.

Also in the Wiki there is still the old description:

There's three encoders available: V2, V1 and System. System uses a default palette, very fast, but not so pretty. V1 uses a neural quantizer to calculate the colors. V2 uses a more simple algorithm that gets the most used colors, not suitable to frames with more than 256 colors.

Not sure if "ScreenToGif" represents "V2" at what status (still under development?) and "Vorgänger/Predecessor" is V1...

@NickeManarin would you please explain the actual status/use cases?

Thank you again 😃

<!-- gh-comment-id:309546958 --> @panther2 commented on GitHub (Jun 19, 2017): I was under the impression that - because of the renaming from "2.0" to "ScreenToGif" - the "new" encoder was no longer "experimental", that's why I asked - but there still appears "experimental" in the tool tip. Also in the Wiki there is still the old description: > There's three encoders available: V2, V1 and System. System uses a default palette, very fast, but not so pretty. V1 uses a neural quantizer to calculate the colors. V2 uses a more simple algorithm that gets the most used colors, not suitable to frames with more than 256 colors. Not sure if "ScreenToGif" represents "V2" at what status (still under development?) and "Vorgänger/Predecessor" is V1... @NickeManarin would you please explain the actual status/use cases? Thank you again :smiley:
Author
Owner

@NickeManarin commented on GitHub (Jun 19, 2017):

@panther2 Sorry, the translation (German, I believe) still uses the old naming scheme. It should be v1.0 and v2.0 as the English version says.

I'll replace when I get home. Thanks.

<!-- gh-comment-id:309550474 --> @NickeManarin commented on GitHub (Jun 19, 2017): @panther2 Sorry, the translation (German, I believe) still uses the old naming scheme. It should be v1.0 and v2.0 as the English version says. I'll replace when I get home. Thanks.
Author
Owner

@panther2 commented on GitHub (Jun 19, 2017):

Oh, we already had the labels "v2" and "v1" in prior versions, even in German (as used in my first posting above) ... that's why I thought things have changed...
Thank you for clearing it up, @NickeManarin ...

So the Wiki description is still up to date?

<!-- gh-comment-id:309551582 --> @panther2 commented on GitHub (Jun 19, 2017): Oh, we already had the labels "v2" and "v1" in prior versions, even in German (as used in my first posting above) ... that's why I thought things have changed... Thank you for clearing it up, @NickeManarin ... So the Wiki description is still up to date?
Author
Owner

@NickeManarin commented on GitHub (Jun 19, 2017):

@panther2 Yes. :)

Next big update I'll focus on the encoding process.

<!-- gh-comment-id:309560921 --> @NickeManarin commented on GitHub (Jun 19, 2017): @panther2 Yes. :) Next big update I'll focus on the encoding process.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ScreenToGif#1469
No description provided.