4 ms·
My first thought was that Google as recompressed everyone's images to save space and corrupted them in the the process. Hopefully everyone gets their images res
by sitkack 4y ago
My first thought was that Google as recompressed everyone's images to save space and corrupted them in the the process. Hopefully everyone gets their images restored.
- cm2187 4y agoI would have rather thought it would be some sort of image enhancement algo gone wrong.
- IshKebab 4y agoYeah it's definitely some overflowing brightness enhancement thing. You can see that in the before/after photo that someone posted.
- vanderZwan 4y agoI was thinking something similar: it has a distinct posterization look that I tend to get when I mess around with images and reduce the bit-width of my input a little too much and my integers overflow. But those tend to result in "zebra stripes" like patterns, so you're probably right that the issue is more one of not using saturating integers while amplifying a value above the bit-width of its container.
- deleted 4y ago[deleted]
- sitkack 4y agoYou can boost contrast to make low bitrate images look better, so it could be a combination of both.
- ReactiveJelly 4y agoIn the thread they say that the original files are available in Google Takeout, so it'll probably get fixed eventually.
- Shorel 4y agoEvery time Google tells me my 15 GB of storage is almost full, I download every photo and delete it from their servers.