I know nothing about computers but this does not add up
I know nothing about computers but this does not add up
142 comments
-
-
Media viewer and the file browser are completely different programs with different support for media file types.
Not that this is an excuse for Media Viewer to not open webp files. Also asking you to pay for h265 support is extra ridiculous.
I just use VLC for everything.
-
They are made by the same company and sold as a unified software package under the name Windows 11 [edition]
-
-
Webp is the worst format ever.
Never mind that:
- it supports transparency;
- it can be losslessly OR lossfully compressed;
- it's so efficient it can fit ẏ̷̛̀̏̎̇͜ǫ̷̼̰̳̹́̆̍̐͜͝ủ̷͉̱̻̤̬̯̈́ŗ̸̒ ̸̨̟͈̳͍̱̀̏̓m̵̺͎̋́u̴͇̥͍͐̇̀̇͊̌̚͝m̸̢̢͕̻̬͙̒͗̽͋͆̕͝ in less than 2GB;
- it can be animated;
- is more than capable of representing 1:1 any GIF image;
it sucks because the one image viewer I've ever had installed by the ubiquitous (= monopolistic) operating system everyone has by default doesn't support it.
-
I just hate webp because it’s supported in a grand total of 2 programs so it’s just annoying to deal with
-
avif is better than it in almost all ways, and jpex xl is even better than that (but not about gifs i think)
webp is essentially a webm file (which is mkv with codec restrictions(vp8/9 and ogg vorbis or opus))
avif is av1 encoded files in a webp like container (but not webm afaik)
jpeg xl is a format made specifically for images
-
I just converted all the images on my website to webp for faster load time. Very happy with it.
-
I was farting around with renpy and grabbed some free assets since I wasn't making anything important, and I noticed that each image was a full megabyte, so I converted them to webp and reduced the entire project from 20mb down to just a few megs (I don't remember specifically but I remember it was a significant reduction)
-
-
and with very few exceptions i've run across, it's also (intentionally or not) configured to produce shit-tier quality output by pretty much everyone implementing it at any sort of scale.
-
Is this the only drawback though? Genuinely curious
-
Probably not, some here say there are better formats, but it's still much better at (almost?) everything than GIF
-
-
Is this a Windows problem I'm too Linux to understand?
Seriously, everything on my computer -- Firefox, Dolphin, Gwenview, GIMP, etc. -- supports webp just fine.
-
Yes. As someone who uses both, this is a M$ problem.
-
It’s an everywhere problem. A lot of sites and apps still don’t support it, but a most browsers do. So people download images from their browser, then they try to view / edit locally, or upload and share, and they hit a wall.
-
We of the privileged Linux class.
Yeah, same here. No problem with webp on Linux Mint.
-
I guess it's Windows users with the default image viewer. IrfanView on W10 handles webp fine for me.
-
So does XnView, both Windows and Linux.
-
IrfanView is GOAT. On par with VLC or Firefox IMO.
-
-
I’m too Linux to understand?
The advantage of using shared libraries is that you only need the one to support webp system-wide and then all apps that need it have it.
-
yes, because we just have 1 good libwebp library
-
-
I loathe windows, but I did just double check because this sounds inept even for M$ -- Win photos will absolutely open .webp, but it's not the default program for whatever reason and it just defaults to edge /
your_default_web_browser_here. Which is just impressively on brand for microsoft. Even when they have a feature they hide it to, idk, make themselves look even worse? Why not!(FWIW this is a clean install, I do not have any non-default codecs installed)
-
THANK YOU. you just saved me so much time with the knowledge.
-
Yeah, it's sorted through WIC iirc. As long as you have the codec installed you should be able to open it.
-
-
I didn't have time to check all the comments, so here's a backup:
Just install GNU/Linux
;)
-
KDE Plasma let's me use .jxl files as my wallpaper. I can also take screenshots in .jxl.
-
-
I kept a copy of the old Windows XP version of media viewer/pictute viewer, whatever the hell its generic name was becsuse at some point in, IIRC, Vista, they updated it to some piece of garbage that had an uglier UI, worked slower, had no options for slideshows, and didn't even support shit like animated .gifs.
Even that old ass program can open a .webp image.
-
Yo that was an absolute joke. Were they serious with that?
Windows handled gifs fine for years then suddenly only the first frame. Seriously?!
-
What the hell, seriously?
-
Wait how does that program know how to open webp? Does webp have like a fallback png mode or something?
-
Webp is a format Google made. Something gave it a codec, so it knows how to open it. It a program doesn't have the codec to read it, no go.
This may work depending on your application https://github.com/jacklicn/libwebp
-
-
I think it opens webp images, because it uses some built-in library (in your OS) to load and display images. WebP format was introduced in 2010, and Windows XP in 2001, so it couldn't support it out of the box.
-
-
I remember when you could’ve made this meme about PNGs.
-
Back when Windows 3.1 only supported BMP and maybe JPG
-
Fancy pants over here with their pictures and color.
-
-
And in a SANE world, somebody who learned a lesson would be using their knowledge so we don't keep repeating the same crap over and over again.
-
Thought you were making a joke about SANE, but that doesn't actually provide PNG handling, does it? 🫠
-
It's Microsoft you are talking about here
-
-
-
-
-
PNG is so fetch.
-
It already happened years ago. It's supported and widely used. Why do people keep posting this misinformational meme?
-
Sounds like windows people sticking to bmp images back when it was all it would support.
-
What are the odds I happen to be watching Mean Girls on Pluto when I scroll across this meme.
-
Irfanview is the answer.
I don't even know what the question was tbh, but I'm still right.
-
Unless the question was do you use faststone 😉
-
Irfanview is always the answer!
-
not allowing webp is the answer.
webp, as the name suggests, is a web image format. not a digital image format.
webp is a fucking cancer and deserves to be put in the same place betamax and 8-tracks were left to rot.
-
I use webp a lot, it's smaller than PNG for lossless images like screenshots and smaller than JPG for lossy while working for both. All the image editors and image viewers I use support it, so it's not inconvenient for me in any way.
Also Portable Network Graphics, as the name suggests, is a network image format, not a digital image format. Just having a laugh : )
-
There are many valid criticisms one can make of webp; perhaps discussing the pros and cons. Rather than using those you instead went after it's name not being linguistically accurate.
A bold strategy cotton.
-
Why is it bad? Like what should I use instead on my website for images and icons?
-
-
-
Time to screenshot the preview and stretch out the jpeg. Upload it when the time calls, only for the web server to re-encode it in webp. The cycle continues.
-
I do this regularly now.
-
-
I use irfanview, VLC and jellyfin. no problems.
-
I was trying to write something that would save an AVIF image this week. Holy shit the ecosystem is bad. I had to encode the image and write the exif tags with two different libraries. The latter being a CLI program and not a library. The WEBP situation is even worse.
We are never getting away from JPEG.
-
I know a bunch about computers and that doesn't add up to me either!! I hate the webp format.
-
Webp is honestly a really good format for what its made to do. That being said, windows support for it is lacking for some reason. I don't know why as it's been common for a long time now.
Also, you can always use ffmpeg to convert to png or jpg or whatever you want. Simple file conversions like that are super easy.
-
It means explorer is running in a web view
-
It doesn't necessarily.
Webp is just a file format like jpg, or png or anything else. You can implement support for it in a native app just the same as any other format.
What certainly IS true is that browsers supported it first (because distributing media on the web is what it was designed for as a format) and a lot of native image viewer apps are still lagging behind on their support.
-
-
-
It's a codec issue. You can get the codec if your OEM paid for it, if not you can buy it on the MS store. It sucks but plenty of other codecs have had the same issue in the past on windows, mkv wasn't playable by windows unless you had a codec for it.
-
And as per usual, VLC seems to somehow have all the codecs already.
-
win10-11. major oem prebuilt and cto should have it installed, otherwise it's here:
https://apps.microsoft.com/detail/9pg2dk419drg
should be 'free' afaik.for win<10, get WebpCodecSetup.exe from the webm/webp project download archives: https://storage.googleapis.com/downloads.webmproject.org/releases/webp/index.html
-
I haven't used windows in years, but I thought this was just about software patents for these codecs. So it should work in regions where software patents are not a thing then (e.g. Europe)?
-
-
Just use a proper Operating System and silly problems like that will go away.
-
Irfanviewer hours
-
taking a screenshot can solve some of this problem
-
I usually convert the image using FFMPEG and that works great.
-
/nods in that thank you kinds of way
-
-
It's not 2015, we don't need any more of those deep fried memes.
-
I just rename it to a ".JPG" file extension and that seems to work ¯(ツ)_/¯
-
-
Huh? I am pretty sure I didn't have any problem opening WebP files when I was still using Windows 10 (switched to Debian GNU/Linux btw).
142 comments
This is MS we're talking about. Preview and Viewer are probably made by two different teams in different countries, sharing no code, and prohibited from communicating with each other, even if they know about the other's existence.
And famously they fired all QAs years ago so there's nobody to test before releasing.
One leveraging the graphics engine from internet explorer the other using the graphics engine from ms paint 1.0
I work in big tech and this is my life. I envy anyone who thinks you're exaggerating, because that means they haven't experienced the joy of spending weeks trying to track down the team responsible for a bug and then months hassling them to fix it.
And if they do talk to each other, the different departments need to go through the whole hierarchy for everything and each manager puts their spin on it, so you get answers back from questions that were not asked.
Wait does this mean I work in little tech?
Oh, man.
I just stopped being hassled to fix a bug on somebody else's system (that mine interops with), by the same developers responsible for maintaining that other system, because the problem got bad enough to escalate until somebody responsible for both sides looked.
That said, I was just ignoring them. But hell...
I imagine the two teams sharing the same desk through a hole in the wall like in Brazil.
I can almost guarantee that they would be using different things. usually you have simpler libraries to decode formats (almost 1 for each codec), and separate programs plug these libraries in to generate the output. previews do not have to be accurate and have to be fast, so a simpler program with just linear scaling or something, where as actual image would be complex which has to worry about accuracy.
still not a excuse to not have support for a free 15 year old format
The image viewer is probably just Edge in a trenchcoat by now.
I think way more of windows 11 is just edge in a trenchcoat than anyone wants to admit...
Can't get away from it at work and i hate it. All we need computers for at work is web access and file sharing, but they still won't budge from daddy Microsoft.
It all makes sense now.
There's no QA to bonk people on the head.
Who the fuck's idea was Outlook (New)? Like half the features don't exist. And some of the actually useful new features simply don't work (looking at you," pop-out" reading pane view option. Where's my popped out reading pane Microsoft??? Did ya forget to test it? Turns out, yes)