search

qiqian / webp

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

webp format Pixel was crash #236

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. pixel was crash
same as webp -pre 4 

Resize filter Lanczos on Xnconvert

What version of the product are you using? On what operating system?
win 8.1 64bit
CPU : AMD Thuban
RAM : SAMSUNG 12G 
GPU : GTX 760

Xnconvert(http://www.xnview.com/en/xnconvert/)
Honeyview (http://www.bandisoft.co.kr/honeyview/)

Please provide any additional information below.

Original issue reported on code.google.com by x86andro...@gmail.com on 5 Jan 2015 at 4:23

Attachments:

GoogleCodeExporter commented 8 years ago 
Not sure I understand. Did one of the tools crash when converting the source? 
xnconvert isn't maintained by this project.
Or do you mean there were problems with the encode (artifacts, color shift, 
etc.)?

Original comment by jz...@google.com on 7 Jan 2015 at 5:00

GoogleCodeExporter commented 8 years ago 
uhm....

This point

same as -pre 4 option

Original comment by x86andro...@gmail.com on 9 Jan 2015 at 7:06

Attachments:

GoogleCodeExporter commented 8 years ago 
the fact that "webp lossless.webp" has smearing green artifacts seems to 
indicate
that the problem occurs *before* compression, since the compression is lossless 
afterward.
I suspect the resizing filter to introduce smearing.

Also, the lines in the source are anti-aliased. See the zoomed region attached.
This complicates the down-scaling, since the antialiased colors are melted into 
the final pixels.

If possible, best would be to directly generate this synthetic image at the 
final size (1920x1080) instead.

Original comment by pascal.m...@gmail.com on 9 Jan 2015 at 10:30

Attachments:

GoogleCodeExporter commented 8 years ago 
and.. no resize filter

Original comment by x86andro...@gmail.com on 9 Jan 2015 at 4:02

Attachments:

GoogleCodeExporter commented 8 years ago 
and file size

option

Original comment by x86andro...@gmail.com on 9 Jan 2015 at 4:37

Attachments: