C language > Graphics programming
GDI+ WebP support
TimoVJL:
I start thinking, that MS don't want to support Win32 API and GDI+ any more.
frankie:
It seems that this format is a Google proprietary format released under BSD license.
It has been developed, based on a video encoder format VP8, with the scope to reduce image size for the rilief of Google storage space and network traffic speedup.
It includes a loss and lossless algorithm, but the image quality is poor compared to native JPG or PNG, and limited in dimensions. Currently is under development a new version that is supposed to overcome the quality problem, but it appeared to not be an easy task and for this reason Google relocated the WebP2 project to a research environment:
--- Quote --- "playground for image compression experiments".
--- End quote ---
The repository where are available sources and binaries is that reported by MrBCX.
Actually the format is handled by chromium browser and its derivatives, including MS Edge.
The format isn't supported in GDI+, but Google implemented a plugin for WIC (Windows Imaging Component) that integrated the format in the applications that use WIC as Windows Photo Viewer, Microsoft Office 2010, FastPictureViewer.
Conclusion: this format is very useful for web pages to speed-up loading and reduce storage that will make it largely diffused in web apps, but is resource expansive (the encoding/decoding is CPU intensive), and poor in quality (actual standard). The last is a limit for high quality pictures.
Last, but not least, if a giant as Google push it, be sure that it will be a de-facto standard shortly....
For more info see.
MrBcx:
From wiki:
On October 12, 2022, Google changed WebP 2's development repository's README file to state that "WebP 2 will not be released as an image format" and began describing WebP 2 as a "playground for image compression experiments".
frankie:
--- Quote from: frankie on February 28, 2023, 10:18:57 AM ---Conclusion: this format is very useful for web pages to speed-up loading and reduce storage that will make it largely diffused in web apps, but is resource expansive (the encoding/decoding is CPU intensive), and poor in quality (actual standard). The last is a limit for high quality pictures.
Last, but not least, if a giant as Google push it, be sure that it will be a de-facto standard shortly....
--- End quote ---
Considering that the encoding is made once, as a consequence, I was wondering, it will move energy consumption (CO2) from server side to user side...
MrBcx:
--- Quote from: frankie on March 01, 2023, 10:17:18 AM --- Considering that the encoding is made once, as a consequence, I was wondering, it will move energy consumption (CO2) from server side to user side...
--- End quote ---
If Google generates a web page that contains gifs and jpegs, your computer uses energy to decompress and display those images. Using a container like webp which requires more computing cycles will exacerbate energy usage on Google server (encode) and your PC (decode). But that increase in energy usage MIGHT be offset on both ends by the reduction in data that would need to be sent between Google's server and your computer when using a container like webp.
Determining whether the net energy usage is reduced, increased, or balanced is an exercise that I shall leave to the bean counters.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version