search

GaseousStates / webp

Automatically exported from code.google.com/p/webp
0 stars 0 forks source link

gif2webp -lossy produces corrupted Webp for GIFs with transparency #245

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Run gif2webp -lossy on the attached GIF

What is the expected output? What do you see instead?
Expected: Webp that looks like the original GIF
Actual: Webp that has weird transparency, looks corrupted, does not reflect the 
original GIF 

What version of the product are you using? On what operating system?
libpwebp  0.4.3 on linux server

Please provide any additional information below.
This doesn't repro if I don't specify lossy

Original issue reported on code.google.com by KTa...@gmail.com on 8 Apr 2015 at 9:21

Attachments:

GoogleCodeExporter commented 9 years ago 
Thanks for the report!
I can reproduce this offline.

The output WebP is correct when using v0.4.2, but shows these artifacts in 
v0.4.3
Likely culprit is: 
https://gerrit.chromium.org/gerrit/gitweb?p=webm/libwebp.git;a=commit;h=5691bdd9
da9239d9dbd680bd16af98c6123b2c02

At the same time, the output is correct at HEAD in master branch: 
https://gerrit.chromium.org/gerrit/gitweb?p=webm/libwebp.git
This is probably because the HEAD revision uses the new and re-written 
AnimEncoder API in place of gif2webp_util.[ch].

Digging deeper in gif2webp_util to figure out the problem.

Original comment by urv...@google.com on 8 Apr 2015 at 10:19

GoogleCodeExporter commented 9 years ago 
Looks like the fix for this is in master branch: 
https://gerrit.chromium.org/gerrit/#/c/72086/, but not in the v0.4.3 branch.

I'll work on getting that fix into v0.4.x as well.

Original comment by urv...@google.com on 8 Apr 2015 at 11:39

GoogleCodeExporter commented 9 years ago 
Thanks for looking into this! Is there an estimated date for the next release?

Original comment by KTa...@gmail.com on 8 Apr 2015 at 11:49

GoogleCodeExporter commented 9 years ago 
To avoid issues like this in the future, we'll do some more verification before 
the release. So, a very rough estimate for the release would be a couple of 
weeks.

Original comment by urv...@google.com on 16 Apr 2015 at 12:31