Nah, I don’t Need HDR
HDR is like RGB, sometimes cool if done really well but usually just a useless selling point.
Yes, I’ll take 8!
40,320?
Nah good old 255 (8-bit obviously)
For a second there I thought you were advocating for fluorescent green or monochromatic CRT screens of old.
Those are very cool tho, i still just barely got to experience those at home :D
Yeah I’ll stick with my monochrome 2 color display for now.
Joke’s on you I can’t afford an HDR display & also I’m colorblind.
You can still profit from the increase in brightness and contrast! Doesn’t make a good HDR screen any cheaper though…
Was gonna say the same thing, HDR is like flac and expensive amps for audiophiles Maybe we should start calling them visualphiles ? 🤷♂️
“FLAC? Mate I destroyed my ears when I was 14 and listening to Linkin Park MP3s grabbed off Kazaa in the cheapest chinese earbuds my allowance could buy, at the highest volume my fake iPod could drive. I cannot hear the subtleties in your FLAC if I tried.”
Cheek aside I believe the word would be Videophiles to pair with Audiophiles.
Eh SDR to HDR is a waaay bigger jump than Mp3 to FLAC. Assuming of course you have an actual HDR display. And not one of those “HDR” displays that only have like 400 nits of peak brightness.
If you can’t tell the difference between a FLAC and an MP3 that’s fine. I can through a cheap pair of headphones and it’s enough that I re-ripped my CDs to FLAC from 320mp3 and they really shine now.
Well, I can. But the difference is so minor it won’t make a difference in my opinion. Especially if you are listening mostly to digital music. It’s a different story for classical, especially violin. But if i played for you both 320 kb mp3 and flac you probably won’t notice unless i told you what to look for and thats fine.
I don’t judge people Hobies, i just wanted To point out how both are somehow similar
The thing is that no one should listen 128kb mp3 -or youtube rip- and having a wide accurate color range screen is more important imo
HDR? Ah, you mean when videos keep flickering on Wayland!
I will switch when I need a new GPU.
Now that explicit sync has been merged this will be a thing of the past
And it was never a thing on AMD GPUs.
videos? everything flickers for me on wayland. X.org is literally the only thing keeping me from switching back to windows right now.
Wayland has started to support Explicit Sync which can fix the behavior of Nvidia’s dumpster fire of a driver
Weird. I have Nvidia and I’m using Wayland and I’ve never had these flickering issues. But seems to be a common complaint, so I think I got lucky.
I’ve seen it in Steam off the top of my head but not much else.
Happens on both my NVIDIA machines, my Intel machines see no such behaviour.
I’m running it on laptop with Intel+Nvidia hybrid graphics. I had Steam on iGPU for ages before I realized, recently switched it to Nvidia but haven’t seen the flickering. I remember someone mentioning that it might have something to do with mouse polling rates or something, but I have a really cheap mouse so I might be too cheap to face that issue haha.
No issues in games, it’s the steam client which has issues.
Now that I remember Firefox extensions too are having issues with overlays (bitwarden) but I’ve not updated my system in a couple of weeks which might to be to blame here.
i’m kind of waiting for an implementation. The “protocol” is useless to me by itself
All of them are already merged. You just have to wait for it to trickle down to whatever you’re using.
For me it’s just games, I’m guessing it’s an Nvidia GPU? I hope explicit sync helps with that.
You want to win me over? For starters, provide a layer that supports all hooks and features in
xdotoolandwmctrl. As I understand it, that’s nowhere near present, and maybe even deliberately impossible “for security reasons”.I know about
ydotoolanddotool. They’re something but definitely not drop-in replacements.Unfortunately, I suspect I’ll end up being forced onto Wayland at some point because the easy-use distros will switch to it, and I’ll just have to get used to moving and resizing my windows manually with the mouse. Over and over. Because that’s secure.
I think the Wayland transition will not be without compromises
May I ask why you don’t use tiling window managers if you don’t like to move windows with the mouse?
Unfortunately, I suspect I’ll end up being forced onto Wayland at some point because the easy-use distros will switch to it, and I’ll just have to get used to moving and resizing my windows manually with the mouse. Over and over. Because that’s secure.
I think you were being sarcastic but it is more secure. Less convenient though.
I’m not sure if that’s what you’re looking for but KDE has nice window rules that can affect all sorts of settings. Placement, size, appearance etc. Lot of options. And you can match them per specific windows or the whole application etc. I use it for few things, mostly to place windows on certain screens and in certain sizes.
I think it’s possible to make such a tool for Wayland, but in Wayland stuff like that are completely on the compositor
So, ask the compositor developers to expose the required shit and you can make such a tool
hahahaha tell that to nvidia users
Smart Nvidia users are ex Nvidia users
Financially smart Nvidia users are Nvidia users
I think that may have been the case early into the Nvidia 30-series but now they seem closer in price and performance so I’m pretty sure my next card will be from AMD when I decide I need an upgrade.
I don’t get what you mean by that
GPU’s are expensive. lots of people can’t afford to ditch nvidia
Ok, makes sense. I thought you meant that nvidia gpus were cheaper than amd ones, which is obviously not true.
Actually wait until the next de releases hit repos, all the nvidia problems just got solved
What? Tell me more. Now! Please
here’s an article explaining the changes, that article was written before they were merged, but they’re merged everywhere now except wlroots. That’s coming soon too.
Obviously it won’t be all of them but I too am very excited about not having to get lucky with my games flickering or not.
Ah yes, the next release will always solve all problems since 5 years.
??? I have been following this for years and nobody I have seen has ever said that with nvidia on wayland
either way it has been tested and actually does so…
Then you didn’t follow closely enough. Nvidia comes up with EGLStreams and Gnome and Plasma accept patches to support this: next release will fix all problems.
Nvidia driver supports GBM: next release will fix all problems.
Only explicit sync is missing but once adopted surely all problems will be fixed.
It’s always one last feature that’s missing for perfect Wayland support…🤦
Nobody thought eglstreams was a good idea or a solution, gbm fixed being able to use wayland at all, no devs were saying that would resolve all the issues. The issues are currently solved, you can test the changes yourself if you don’t believe me, but this truly is the end
i’m not saying wait for the next release because they might solve it, I’m saying the current set of patches is confirmed to solve it.
Sorry, I won’t test this myself because I’ll never combine Nvidia with Linux for years to come but all the time it was promised that X11 fallback for Nvidia would no longer be needed and everytime it was followed up by countless bug reports that basic features aren’t working.
That’s the difference between some randos promising it and the devs extensively testing it and confirming it works universally.
I’m a happy Nvidia user on Wayland. Xorg had a massive bug that forced me to try out Wayland it has been really nice and smooth. I was surprised, seeing all the comments. But I might’ve just gotten lucky.
I tried wayland with the newest nvidia driver on Arch and it was unusable and extremely unstable.
I’m somewhere in between. X11 doesn’t work with linux-lts (arch) for me and Wayland stutters occasionally but not always. Usually it happens exclusively in games, some reliably, some when I switch windows and in some when I move around or increase game speed. But I’m excited for explicit sync
deleted by creator
may 15 Arch users are going to be down loading the NoVideo Wayland Driver.
OK but can you please call NVidiachan? I know you two don’t get along but maybe you can ask her for some support?
NVidiachan is busy selling GPUS for AI, but she is also working on adding explicit sync
If I understand correctly Nvidia isn’t doing anything to do with explicit sync, it just doesn’t support implicit sync which is currently what Wayland uses because we don’t have explicit sync yet. Explicit sync would work with existing Nvidia drivers.
How will HDR affect the black screen I get every time I’ve tried to launch KDE under Wayland?
It will make your screen blacker.
But it all seriousness, your display manager might not support Wayland. Try something like ssdm.
I’m using SDDM and it lets me select Wayland as an option just fine, Just my Nvidia card won’t load my desktop then.
I’m going full AMD next time I upgrade but that’s gonna be a while away…
Nothing you can do then. Stay on x11 until nvidia get their shit together.
They just did now that explicit sync is merged everywhere except wlroots
It should work with the latest Nvidia driver. It does for me.
deleted by creator
how on earth do I know what DM I’m using? Does it come with the compositor? I just start hyprland from the terminal without adding anything to systemd.
Then you aren’t using one
Oh, lightdm has some trouble sometimes on my other computer, are you saying that I could somehow start i3 without it when it breaks itself?
You could start it directly from tty with startx https://wiki.archlinux.org/title/Xinit
You already had me at “144hz on one monitor and 60hz on the other so I can enjoy the nice monitor without having to buy a new secondary one.”
Option "AsyncFlipSecondaries" "true"
It’s not ready yet.
The protocol for apps/games to make use of it is not yet finalized.
The protocol won’t be “finalized” for a long time as new shit is proposed every day.
But, for me and many others, it has had enough protocols to work properly for some years now. Right now I’m using Wayland exclusively with some heavy workloads and 0 issues.
I can play games and watch videos in HDR though
Me, not much of a gamer and not a movie buff and having no issues with the way monitors have been displaying things for the past 25 years: No.
When I could no longer see the migraine-inducing flicker while being irradiated by a particle accelerator shooting a phosphor coated screen in front of my face, I was good to go.
It was exciting when we went from green/amber to color!
without any interruption to gaming compability I definitely don’t want to switch sorry.
HDR is cool and I look forward to getting that full game compability and eventually making the switch but it’s just not there yet
Deleted
Been watching this drama about HDR for a year now, and still can’t be arsed to read up on what it is.
HDR or High Dynamic Range is a way for images/videos/games to take advantage of the increased colour space, brightness and contrast of modern displays. That is, if your medium, your player device/software and your display are HDR capable.
HDR content is usually mastered with a peak brightness of 1000nits or more in mind, while Standard Dynamic Range (SDR) content is mastered for 80-100nit screens.
How is this a software problem? Why can’t the display server just tell the monitor "make this pixel as bright as you can (255) and this other pixel as dark as you can (0)?
In short: Because HDR needs additional metadata to work. You can watch HDR content on SDR screens and it’s horribly washed out. It looks a bit like log footage. The HDR metadata then tells the screen how bright/dark the image actually needs to be. The software issue is the correct support for said metadata.
I‘d speculate (I’m not an expert) that the reason for this is, that it enables more granularity. Even the 1024 steps of brightness 10bit colour can produce is nothing compared to the millions to one contrast of modern LCDs or even near infinite contrast of OLED. Besides, screens come in a number of peak brightnesses. I suppose doing it this way enables the manufacturer to interpret the metadata to look more favorably on their screens.
And also, with your solution, a brightness value of 1023 would always be the max brightness of the TV. You don’t always want that, if your TV can literally flashbang you. Sure, you want the sun to be peak brightness, but not every white object is as bright as the sun… That’s the true beauty of a good HDR experience. It looks fairly normal but reflections of the sun or the fire in a dark room just hit differently, when the rest of the scene stays much darker yet is still clearly visible.
Here is an alternative Piped link(s):
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source; check me out at GitHub.
HDR makes stuff look really awesome. It’s super good for real.
HDR is almost useless to me. I’ll switch when wayland has proper remote desktop support (lmk if it does but I’m pretty sure it does not)
Seems like there’s a bunch of solutions out there:
As of 2020, there are several projects that use these methods to provide GUI access to remote computers. The compositor Weston provides an RDP backend. GNOME has a remote desktop server that supports VNC. WayVNC is a VNC server that works with compositors, like Sway, based on the wlroots library. Waypipe works with all Wayland compositors and offers almost-transparent application forwarding, like ssh -X.
Do these not work for your use case?
I did try those, but it might be the fault of my nvidia card for not working. The issue was that I wasn’t able to understand nor fix any problems that popped up. I’ll try it out again when I get a new GPU
Yeah, Nvidia really sucks on Linux unfortunately and they simply do not care very much.
MPV playback and games aren’t everything, but it’s decent for the starter
Kde on Wayland doesn’t even have sticky keys.
