Thanks & Regards,Vikas
--
You received this message because you are subscribed to the Google Groups "WebP Discussion" group.
To post to this group, send email to webp-d...@webmproject.org.
To unsubscribe from this group, send email to webp-discuss...@webmproject.org.
For more options, visit this group at http://groups.google.com/a/webmproject.org/group/webp-discuss/?hl=en.
Hi,On Fri, Jul 20, 2012 at 3:07 PM, Vikas Arora <vik...@google.com> wrote:Hi -Last few months, WebP team has been working on adding two enhancement features to WebP format v.i.z Alpha Channel support and Lossless support. Today we pushed out the next version of libwebp (ver 0.1.99), that contains these two features. The archives are available at [1] and the git repository has been tagged 'v0.1.99'. The iOS-App has been updated too with the latest codec and WIC coded will be updated soon. This is a pre-release of version 0.2.0, to allow for further incompatible changes based on user feedback. We encourage community to try out these two features and provide any feedback on the format.Last week we also published the study with compression and decompression characteristics of WebP with these two (Alpha & Lossless) newly added features and compared them with libpng and pngout. It was shown in the study that with these two new features, 97% of the Lossless (PNG) web images can be better compressed and one can relatively easily change these from PNG to WebP format. WebP with default compression settings can compress 34% better than libpng and 25% better than pngout. This suggests that WebP is promising for speeding up image heavy websites.In addition to adding these two new features, following changes (from NEWS file) have been done since last release (V0.1.3):- Add TIFF input support to cwebp (webp encoder).- Deprecated function WebPINew() has been removed.- Decode function signatures have changed to consistently use size_t over int/uint32_t.- decode_vp8.h is no longer installed system-wide.note also that the doc site has been updated to incorporate the latest changes, too. In particular:* the API description: https://developers.google.com/speed/webp/docs/api* the RIFF container description: https://developers.google.com/speed/webp/docs/riff_container
That's a nice step forward!
Could you gather some stats from your test files?
I'm curious to know which WebP lossless features are actually used (type and number of transforms, frequency of each predictor, color cache size, number of meta Huffman codes in the entropy image...).
Is there an easy way to produce WebP lossless files without transforms, entropy image, color cache, that could be used as a baseline reference?
--
You received this message because you are subscribed to the Google Groups "WebP Discussion" group.
To view this discussion on the web visit https://groups.google.com/a/webmproject.org/d/msg/webp-discuss/-/G2RjfJh0EfcJ.
Hi FrédéricOn Sat, Jul 21, 2012 at 6:21 AM, Frédéric Kayser <cry...@free.fr> wrote:That's a nice step forward!
Could you gather some stats from your test files?good suggestion! let's get started with: https://gerrit.chromium.org/gerrit/#change,28155More to come, but that's a start. I'd like to keep the stats light and avoid heavy scans though...
On Aug 13, 2012 10:32 PM, <literatur...@googlemail.com> wrote:
>
> Spineanu Radu wrote:
>
>> Is there a Chronium/Chrome release that incorporates 0.1.99?
>>
> Hello,
> google-chrome-unstable (22.0.1229.2-r150678) is build with v0.2.0-rc1.
Note: WebKit needs a refresh too, which is taken care of at https://bugs.webkit.org/show_bug.cgi?id=93430
>
>
> --
> You received this message because you are subscribed to the Google Groups "WebP Discussion" group.
> To view this discussion on the web visit https://groups.google.com/a/webmproject.org/d/msg/webp-discuss/-/-MMcUM6K3uUJ.
Spineanu Radu wrote:Is there a Chronium/Chrome release that incorporates 0.1.99?
I couldn't find that exact build so I tested with Google Canary 23.0.1237.0 canary.Unfortunately the webp I created isn't animating in this version. I'm not sure if it's me doing something wrong, or if that version of Canary was not built with the latest libwebp.