This myth that ARM is more efficient needs to die already. The ISA has almost no impact on efficiency, and especially no impact on gaming, where the GPU is the much more important thing.
This myth that ARM is more efficient needs to die already. The ISA has almost no impact on efficiency, and especially no impact on gaming, where the GPU is the much more important thing.
Yes, there’s an addon for Firefox that gives you Netflix 1080p without any downsides, probably just by changing the user agent for Netflix.
Really shows how utterly useless the restrictions are.
This is about dragging a tab out of or into a browser window, and letting the compositor know about it, so it can move and place the window accordingly. Apps don’t get to place windows themselves.
The github repo has tons of issues about the problems caused by the hacks (from the cursor not being recorded, to it not working in Flatpak, not working with virtual displays, to even preventing graphical sessions from starting!) with the suggested solution of just using the remote desktop portal… I don’t know what the problem is, but it’s not a lack of knowledge.
misconfigured
Unless you did something really stupid and deleted system libraries or something like that, no configuration should cause crashes. Please make a bug report about it at bugs.kde.org. You might not be able to fix it yourself, but crashes are often relatively easy to diagnose and fix for a developer.
In the case of one project in paticular, that being the Sunshine game streaming project
That’s a terrible example, because they completely ignore the many many years old standardized APIs (screen casting and remote desktop portals) that they could use, in favor of doing hacky and broken things that require root access instead.
Xwayland doesn’t get input in some special way, it uses the exact same Wayland protocols to get input events as native Wayland apps. All claims about it being more complete or anything like that are nonsense.
Krita forces Xwayland because they have some X11 specific code they haven’t bothered porting away from, that’s all.
What kind of flickering? Does the display support adaptive sync? If so, try turning that off
You don’t need to use steamtinkerlaunch, putting gamescope --hdr-enabled --fullscreen -W width -H height -- %command%
into the launch options is enough.
Will the Gnome version of Bazzite work for HDR on an Nvidia GPU, or for that matter any other OS as long as I’m using gamescope to run the game with HDR enabled?
Gamescope can’t make a different compositor support HDR. Until Gnome supports HDR and the protocol used by gamescope, it won’t work.
For Netflix there’s a browser extension that does it, but I don’t know of a solution for other streaming services
I wouldn’t read that much into it. Valve isn’t Nintendo, I doubt they’d launch a new Deck without OLED
Yeah, it gets more blown out the bigger the difference between the sdr brighrness setting and the highlights is.
Support for HDR screenshots is hopefully something I can add soon-ish
How are you taking the screenshots? Spectacle might not capture HDR highlights well, but it should look all proper on SDR content
Also, your blog is fantastic, I’m always happy when there’s a new post =)
Thank you, I’m glad you like it!
I feel like in SDR mode, the OLED is pushing brighter images. I almost feel like it’s underselling the capabilities at 270, but does so to give pixels a rest every now and then, in the hope that the bright spots don’t stay stationary on the screen. It’s a wild guess, I have no idea.
It’s certainly possible, displays do whacky stuff sometimes. For example, if the maximum brightness in the HDR metadata matches exactly what the display says would be ideal to use, my (LCD!) HDR monitor dims down a lot, making everything far, far less bright than it actually should be.
KWin has a workaround for that, but it might be that your display does the same thing with the reported average brightness.
That’s not really a Wayland thing, that’s an (apparently badly implemented) attempt to bridge X11 apps to a permission system they were never written for.
With appropriate sandboxing of apps so they can’t just LD_PRELOAD code into all other apps you run, yes.
I understand that it’s an absolute brightness standard, not like the relative levels in SDR
The standard is also relative brightness actually, though displays (luckily) don’t implement it that way.
why does it end up washing out colors unless I amplify them in kwin? Is just the brightness absolute in nits, but not the color?
It depends. You might
Why does my screen block the brightness control in HDR mode but not contrast?
Because displays are stupid, don’t assume there’s always a logical reason behind what display manufacturers do. Mine only blocks the brightness setting through DDC/CI, but not through the monitor OSD…
Why is my average emission capped at 270nits, that seems ridiculously low even for normal SDR screens as comparison
OLED simply gets very hot when you make it bright over the whole area, the display technology is inherently limited when it comes to high brightness on big displays
Multi monitor VRR has never been problematic in Wayland, but the NVidia kernel driver doesn’t support it at all yet, Xorg or Wayland doesn’t matter.
enabling the built in color profile desaturates colors quite a bit and does some kind of perceived brightness to luminosity mapping that desaturates bright / dark hdr content even more
It maps the colors to be more correct, and it does use the brightness info from the EDID for HDR content, so that checks out.
I think there must be something wrong with my screen since the hdr reduces saturation more than anything else
It might enable some sort of gamut mapping on the display side… HDR on monitors is really weird sometimes.
Side note, when I turn off hdr only from kscreendoctor the display stays in hdr mode until it turns off and on again, that didn’t happen with nvidia
I think that’s a bug in amdgpu. It should force a modeset on hdr change, but it doesn’t.
… is not something you should ever use on a desktop PC. Due to its eternally very outdated nature and not even shipping bugfix updates**** it is not a good fit for anything but servers.
“Wayland” doesn’t handle monitors at all. What (because of Debian, wildly outdated) desktop did you use?
Not a Linux issue, but a problem with the desktop environment you chose. KDE Plasma allows you to configure panels in any way you want.