Looking at them again, two.png is 24 bit colour while the original png kept 32 bit. I wonder if that triggered a different scaling algorithm on endchan's side for the slightly different thumbs.>>111>>113
I think a lot of the silly files you see, like 1080p gifs, are due to some artists, while being great at drawing or modeling 3d, just happen to be ignorant about what file types and sizes actually are. They choose the wrong thing, have to rely on 'default' encoding settings, use some borked conversion software, or click the 'make this phone compatible' checkbox without realising. And there's a bit of auto-upload conversion scripting gone wrong. What used to be a pretty nice 15 second 22MB 1080p 60fps webm ends up a crazy 12fps super gif with a fucked palette. Thankfully, I would say the situation has improved in the past year or so. There are some fantastically well-optimised 4k webms floating around, even.
An idle dream of mine is to write a 'look at this media, see if it is massively unoptimised, and if possible make a "good" version' module that could take things like big pngs and make a human-imperceptible optimisation. It'd use pixel statistics to figure out the 'imperceptible' part, so you ideally wouldn't be able to tell which was the optimisation in a blind test. And ideally be completely deterministic, too, so the same operation on the same file on two computers produces the same byte-for-byte output file. Just an easy thing for anyone who was ignorant to say 'hey, I made/have this thing but don't understand the tech side, please make it nicer for sharing with an emphasis on human consumption'.
A bit like https://github.com/WebMBro/WebMConverter,
but for more media types and an emphasis on no downgrades.
I'd plug it into hydrus, but it would be completely optional, of course. I have played around with ffmpeg a decent bit and have some ideas on this for video. It wouldn't be massively difficult to do, just would take some work, and the end product would be pretty CPU heavy. I am somewhat surprised the codec creators haven't written their own 'just make this shit good' parameter, but I generally figure they work for the industry more than anything, who are happy with obscure params for their different specific streaming tech needs and so on.
However, on the hydrus side, improvements to the duplicate system may supersede most of this. Lots of people are already doing this reencoding work manually or with their own scripts, the results of which we all end up downloading as dupes. If hydrus gets auto-duplicate-resolution tech that can mine your existing data for more optimal dupes, we won't have so much reason to generate our own.
And who knows, maybe waifu2x tech will get crazy in the next five years and the whole argument will be moot.
Message too long. Click here to view full text.