4 ms·
2^14 pixels in both directions with 4 bytes per pixel (ARGB) puts the pixel data at a maximum size of 2^30 bytes. Just barely enough to be indexed using a 32-bi
by colejohnson66 8y ago
2^14 pixels in both directions with 4 bytes per pixel (ARGB) puts the pixel data at a maximum size of 2^30 bytes. Just barely enough to be indexed using a 32-bit integer (even a signed one if you want)
- flohofwoe 8y agoLooks like WebP uses RIFF data chunks [1] (which look a lot like the old Amiga IFF file format), and the size of such a chunk is a 32-bit integer. Besides, 16k width/height ought to be enough for anyone ;) [1] https://developers.google.com/speed/webp/docs/riff_container https://developers.google.com/speed/webp/docs/riff_container
- dllu 8y agoI take photos of trains [1] and regularly run into file format limitations as the photos can easily reach hundreds of thousands of pixels wide. Besides, modern cameras such as the Sony a7R II are already producing photos 8000 px wide, and the upcoming 100 megapixel cameras such as the Fujifilm will do 12000 px wide images. It's very easy to hit the limit if you're planning to shoot any panoramas. [1] https://commons.wikimedia.org/wiki/User:Dllu https://commons.wikimedia.org/wiki/User:Dllu
- jopsen 8y agoIf the raw size is approaching 4GB maybe it's fair to split the image.. Anyways, webp is for websites not cameras..
- IshKebab 8y agoI don't get your point. You wouldn't typically encode such a large image in one chunk.