I don’t know what a .webp file is but I don’t like it. They’re like a filthy prank version of the image/gif you’re looking for. They make you jump through all these hoops to find the original versions of the files that you can actually do anything with.
Edit: honestly I assumed it had something to do with Google protecting themselves from image piracy shit
Webp is an image format.
Jpg is ancient, and gif, holy shit gif is from stone age.
I dunno, if you’re playing a video, you probably want x264 or better these days, no? For music, we use some variant of mp4 or lossless at this point.
Yet with pictures, for some reason we insist on the old shitty stuff.
Using jpeg or gif is like using mp1 for music and VideoCD for video. Come on now.
The only problem with webp is that there’s quality loss if you convert an already compressed jpeg into webp with high compression rate, like some web sites do. That can suck, but I don’t know how else to get people to use more modern formats. Otherwise we’d be using ancient formats into the 24th century.
The old shitty stuff was designed to compress images and stuff to be small enough to transfer on potato internet.
Now the HTML size itself ends up larger than many of the images while they code in endless advertising and scripts.
Old internet was better TBH.
This isn’t really relevant when webp is more optimised and smaller file size. People are determined to force things to be GIFs despite them looking terrible and taking up 50MB for 10 seconds of 720p looping video.
Oh, I forgot to mention in my other comment, as far as compression goes, what ever happened to good old MIDI? 🤔
Midi is quite literally a text format, and you can open it in anything. It’s just a matter of interpretation what comes out of it.
I’m looking at a MIDI file in a hex editor right now, it’s literally not a plain text file. Plain text files use carriage return and/or line feed characters to end a line of text. MIDI uses null to separate instrument notes and attributes.
Also, when was the last time you tried opening a MIDI file? Seems like half the media player apps and even some operating systems don’t even natively support it anymore.
Ok apologies. But you get my point, it’s a set of instructions made for actual hardware with built-in samples. I don’t think there’s any such thing in modern computers even beyond emulation on OS level.
Sound players are made to play sound, not instructions, and most people don’t need to play MIDIs. Even so, the actual playback experience then depends on the OS/hardware/whatever, which again is not something you expect from a sound player.
You can always use specific software to play MIDIs, which are better equipped for it with stuff like MIDI font support, instrument selection and other stuff.
I never said GIF was all that great. Hell, beyond the fact that it was piss poor compression, it didn’t even have audio. 🤦♂️
Now MPEG1/2, MP3 and JPEG weren’t all that bad, considering the era of technology they came from.
I can definitely agree that modern compression has improved beyond that even, but at the same time now everything is automatically tagging in all sorts of extra data like, I dunno, the GPS location the image/video was taken. Like hey, let’s just broadcast everyone’s address to the rest of the world…
You can put metadata into jpg and mp3 as well, no differences there.
Of course, yes, you can. But back then, that was usually up to the person recording the media to manually add metadata later in processing.
These days everything is getting tagged automatically as you’re recording stuff.
Bye bye privacy.
And if you tell someone that it’s creepy and they should disable it, they look at you like you’re the weird one.
Indeed.
We live in a society. 🤷♂️
So was QuickTime and RealMedia. Today we know how to compress things better.
Agree with the HTML sadly… Sigh.
GIF was ancient in the YTMND.com days. And nowadays, YTMND is like two decades old. Back when my life had hope.
Sure, but so is .zip, and that’s still useful.
IMO a better argument would be how and why webp improves on jpg (better compression, etc), not just “it’s newer”.
I shouldn’t need to say this, but here goes: “old” and “shitty” aren’t actually synonyms.
It is more efficient. I thought it’s obvious, that’s why web sites use it, to save traffic and potentially storage. Hence my comparison to video formats. You don’t see YouTube playing videos in Real Media format.
It’s also more universal, combining features of jpg, png and gif. Gif especially is a dreadful format for what it’s commonly used. It was designed for tiny clipart animations, not HD video clips. Something like x265 can actually be hundreds of times more efficient.
Do you know if there are any formats that provide for native looping like gif? I find that feature useful for some standalone files.
WebM can create loops
Even .apng could but was rarely if ever done for some reason.
I haven’t even heard of .apng, is it widely supported?
No, lol.
It stands for animated png btw. It was an extension. The benefit was that it always rendered something everywhere, if it didn’t support the animation, because it would be read out as a regular (but suspiciously heavy) png in that case.
I brought it up because it’s yet another old-ass .gif solution that didn’t stick because people love the term “gif”.
I mean for audio I use these large mostly black disk things…
For nonphysical media I’m a filthy streaming whore.
Where does PNG stand in this timeline?
I think PNG is a good format even today. It’s lossless compressed, so there isn’t that much you can squeeze out of that with new algorithms as you can out of lossy formats with new and smarter approaches.
Sadly, PNG is being terribly misused on the internet too. What it’s good for is simple drawn graphics, which it can compress to oblivion. So it’s perfect for screenshots of say, your operating system’s windows. I took a sshot as I’m typing this, and it came out as 190 kB. Not bad.
But what it’s so commonly used for, is people taking screenshots of photos such as from Instagram, and then reposting them. So instead of a tiny and shitty 50 kB IG picture, you get a 1.5MB PNG screenshots. Some then recompress it to a 1.5MB JPG for “maximum quality” when they realise they can’t upload PNG to photo sites.
I also very often encounter huge PNG photos with their extensions changed to JPG, and I don’t know how or why that is happening.
This one really grinds my gears. Why do so many people insist on sharing text by taking a picture instead of pasting the text? Or better yet, just linking to the original? It’s such a waste of bandwidth :(
Probably people uploading to sites that limit extensions thinking they’re clever by just changing the extension, or being straight up wrong in thinking the extension changing actually changes the file type.
The sites might not bother to check the metadata, and anything worth any salt that displays the image will ignore the extension anyway.
That sounds logical, but on most operating systems these days the extension is hidden, and/or you need to go through some hoops to change it. So I would think that most people who think that wouldn’t even know how to change it.
But more importantly, where do those PNGs come from in the first place? Sure, some are clearly screenshots such as of IG or TT, but there are tons of large PNG images that are clearly photos from cameras that someone just took and resaved as png (and later, or someone else, then renamed to jpg).
I could understand that happening occasionally for a bunch of reasons, but I’ve encountered this so many times, it’s pretty bizarre.
Btw it’s something you might not even notice if you aren’t using e.g. an image viewer that uses a different icon or background based on actual image type.
I suppose another solution might be that it falls under those lines, but some misbehaving services where they’re uploaded are giving out improper filenames and not confirming the type.
Though I can’t imagine many of those being incredibly popular, or, it’s just that images are recycled for so long that eventually many of them hit such a site in their lifetimes.
Anyway here’s my take on it
Yet you still posted it in jpeg. Can’t fool me with your sly tricks.
Input #0, image2, from '85974f2f-5463-40ba-93ea-45417c183fcc.jpeg': Duration: 00:00:00.04, start: 0.000000, bitrate: 54211 kb/s Stream #0:0: Video: mjpeg (Baseline), yuvj444p(pc, bt470bg/unknown/unknown), 1513x947, 25 fps, 25 tbr, 25 tbnGood point lol
After reading through more comments in this discussion, maybe I have my answer, at least partially. A lot of people here suggest to use extensions and other ways to convert webp from the web to… PNG.
And then that PNG gets shared further…
Oh gawd if that’s why so many pngs are on the net… What a way to take a good idea and completely fuck it up. Now instead of a 2MB jpeg or 0.5MB webp we deal with 10MB pngs 🤦♂️
It supports features such as lossless editing and transparency but the compression is pretty bad.
It’s lossless, it’s meant for 2D and drawn graphics. Can’t do that much with lossless compression.
It’s still bad compared to modern lossless algorithms. PNG is very old and even though PNG encoders have evolved, it is still fundamentally a decade behind modern lossless compression algorithms.
For example: JPEG XL in lossless mode compresses at least 30% better than PNG.
Also, PNG is not actually lossless in many cases. PNG only supports RGB colorspaces. If you try to store anything that’s not in an RGB colorspace (e.g. a frame of a video) in a PNG, you will lose some color information as colorspace conversion is not lossless. Example of someone running into this issue: https://stackoverflow.com/q/35399677
JPEG XL supports non-RGB colorspaces so you don’t have this problem.
Okay but that difference is not as critical as with jpg, which are also more abundant. The bigger problem with png is that people use it for things it’s not meant or designed for - frame of a video being case in point.
If anything, it just proves how lacking we are in other image formats, when we keep shoehorning clipart formats like png and gif into other duties. Well not lacking as in not having them, but not using them.
There’s no real reason why you shouldn’t use PNG for a frame of video. I’m not talking about using it as a video format, I’m talking about extracting a frame from a video and sending it off to an editor for inclusion in another video or image.
As a user, I would expect that I could use the most popular lossless image format if I want to losslessly share a frame from a movie with someone.
Of course I do agree that we need adoption of other image formats. We really should not still be cramming everything in PNGs or JPGs in 2023.
There is, exactly because png is made for strict rgb colorspace. Especially today when videos can be in HDR and with all kinds of color correction shenanigans, so which you won’t get back once you try to put the PNG back into the video.
But I’m not a video editor, so I don’t know what still format is best suited for this. I imagine real editors can deal with it, and for regular people who just make screenshots for memes, it’s good enough. As I said, png is still a good enough format, but let’s not use it for stuff like converting webp photos for further sharing.
I think we generally agree but I just want to clarify anyways. I’m not saying we should use PNG to store frames from videos.
What I am saying however, is that we should replace PNG with a modern lossless image format that is more flexible so users don’t have to deal with these issues. All this colorspace stuff should be automatically handled and I shouldn’t have to worry about it not being lossless. If I want to save a frame of video, I should be able to do it using an image format that everybody recognizes and accepts, it should not be a huge hassle and it should be fully lossless.
PNG compresses like nothing else when it comes to graphs, text, UI elements, digital drawings, comics, screenshots from apps etc. And doesn’t suffer from “mosquito” artifacts and other .jpg nonsense. It was never meant to be used for photographs and other statistically “noisy” images for which .jpg works much better.
Isn’t it funny how the internet is full of Instagram screenshots in PNG, and Twitter screenshots in JPG?
It feels like some extra-dimensional aliens are fucking with us and making everything backwards.
AAC is only 5 years younger than JPEG. Lossless music formats are about as ancient as GIF.
But requirements for audio hasn’t changed that much, and overall it’s a much older and thus mature technology, that there isn’t much left to figure out. Consumer CD format with 16bit 44.1kHz has been around for 40 years, and you don’t need much better quality than that. So there isn’t much left to figure out.
But images and videos are different. 20 or 30 years ago you didn’t need to commonly send 20 MPix HDR photos and HD to 4k videos over the internet. Shoehorning formats that were made for 640x480 pictures and tiny silly clipart animations just doesn’t make sense, especially with all the development that’s been made in that time. Newer compression techniques can help, but you can only do so much.
Err…nothing in the file format spec restricts jpg to a particular size. I would actually argue that this undermines your point – bandwidth was incredibly limited in the 90s compared to what I see today.
Simple example: a 640x480 image is (at least) 307,200 bytes = 0.3M, so it takes at least 5.4 seconds to transmit over a 56k modem. A 4k image, same color depth, is 16000000 bytes = 15M. On a gigabit connection (what I have), that takes about 0.02 seconds.
I was taking more about quality than size in this particular comparison. In 1993 you were happy to squeeze through an image in any quality almost.
It goes hand in hand tho.
If you can compress a 50 MPix, 16-bit, high dynamic range image from a modern high-end DSLR to a reasonable size with a better algorithm and format, you’d also have an easier time squeezing a crappy 640x480 pic to an even smaller size. We just couldn’t do either so well 30 years ago.
Heh, in 1993 I wasn’t online at all. '97 or '98 is more like it in my case.
That’s a fair point, too, better image quality for a given size. I was more focused on raw bandwidth demands.