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.
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
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.
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.
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.
“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.
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.
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.
Those randos were Nvidia developers and DE developers making such statements towards distribution maintainers after they asked if removing the automatic X11 fallback for Nvidia GPUs is fine.
It’s always “one last feature / Nvidia workaround until it’s fine”. The same thing since years. Surely this time everything is different.
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’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
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.
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!
You want to win me over? For starters, provide a layer that supports all hooks and features in xdotool and wmctrl. As I understand it, that's nowhere near present, and maybe even deliberately impossible "for security reasons".
I know about ydotool and dotool. 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 do move some windows with the mouse. There are other situations where I move/rezise them using keybinds that aren't standard, and I'd like the option to be able to continue to do that in the future.
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.
RDP (Remote Desktop Protocol) works leaps, bounds and miles better than the 1989 X11 Network Transparency system ever did. Especially so that X11 was never intended for hardware accelerated compositing or 3D apps.
PCs were not intended to have more than 640kb of ram and yet.
The blame can squarely be placed on nvidia for this decrepitude of X11 and its functionality which is in contradiction of nvidia’s unlimited profit ambitions.
RDP is the anachronism. Why would I want to stream a whole desktop environement with its own separate taskbar, clock, whole user environement. Especially given how janky and laggy it is.
No, I want to stream -just- the application, it should use my system’s color and temperature scheme, interoperate clipboard and drag&drop, be basically indistinguishable from a locally running app, except streaming at 500mbps AV1 hardware encoded, 12 ms latency max, 16k resolution, yes this is not a typo, 16 bit hdr, hdr that actually works, the sounds works too, works every time, yes 8 channel 192khz 24 bit lossless. Also capable of pure IP multicast streaming. Yes that means one application instance visible on multiple computer, at the same time and can be interacted with multiple users at the same time with -no- need for the app to be aware if any of this.
Do that with no jank and I’ll sing wayland’s praises.
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.
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.
Anti Commercial AI thingyCC BY-NC-SA 4.0Inserted with a keystroke running this script on linux with X11 bash #!/usr/bin/env nix-shell #!nix-shell -i bash --packages xautomation xclip sleep 0.2 (echo '::: spoiler Anti Commercial AI thingy [CC BY-NC-SA 4.0](https://creativecommons.org/licenses/by-nc-sa/4.0/) Inserted with a keystroke running this script on linux with X11 bash’ cat “$0” echo ':::') | xclip -selection clipboard xte “keydown Control_L” “key V” “keyup Control_L”
It isn’t, it’s just that marketing is really bad at displaying what HDR is about.
HDR means each color channel that used 8 bits can now use 10 bits, sometimes more. That means an increase of 256 shades per channel to 1024, allowing a higher range of shades to be displayed in the same picture, and avoiding the color banding problem:
I have never seen banding before, the image seems specifically picked to show the effect. I know it’s common when converting to less than 256 but color, e.g. if you turn images into svgs for some reason, or gifs (actual gifs, not video)
Also dithering exists.
Anyway, it’ll surely be standard at some point in the future, but it’s very much a small quality improvement and not something one definitely needs.
the image seems specifically picked to show the effect
Well, of course it is.
Banding is more common in synthetic gradients though, like games and webpages. A really easy way to see it is using a css gradient as a web page background.
Fair enough. Dithering would still be an option though. But if it’s not done I agree there can be visible stripes in some cases.
Also I wanted to apologize for the negative wording in my above comment. That was uncalled for, even if I think HDR is totally not worth it at the moment.
That’s just 10 bit color, which is a thing and does reduce banding but is only a part of the various HDR specs. HDR also includes a significantly increased color space, as well as varying methods (depending on what spec you’re using) of mapping the mastered video to the capabilities of the end user’s display. In addition, to achieve the wider color gamut required HDR displays require some level of local dimming to increase the contrast by adjusting the brightness of various parts of the image, either through backlight zones in LCD technologies or by adjusting the brightness per pixel in LED technologies like OLED.
I assume HDR has to be explicitly encoded into images (and moving images) then to have true HDR, otherwise it’s just upsampled? If that’s the case, I’m also assuming most media out there is not encoded with HDR, and further if that’s correct, does it really make a difference? I’m assuming upsampling means inferring new values and probably using gaussian, dithering, or some other method.
Somewhat related, my current screens support 4k, but when watching a 4k video at 60fps side by side on a screen at 4k resolution and another 1080p resolution, no difference could be seen. It wouldn’t surprise me if that were the same with HDR, but I might be wrong.
Anti Commercial AI thingyCC BY-NC-SA 4.0Inserted with a keystroke running this script on linux with X11 bash #!/usr/bin/env nix-shell #!nix-shell -i bash --packages xautomation xclip sleep 0.2 (echo '::: spoiler Anti Commercial AI thingy [CC BY-NC-SA 4.0](https://creativecommons.org/licenses/by-nc-sa/4.0/) Inserted with a keystroke running this script on linux with X11 bash’ cat “$0” echo ':::') | xclip -selection clipboard xte “keydown Control_L” “key V” “keyup Control_L”
yes, from the capture (camera) all the way to distribution the content has to preserve the HDR bit depth. Some content on YouTube is in HDR (that is noted in the quality settings along with 1080p, etc), but the option only shows if both the content is HDR and the device playing it has HDR capabilities.
Regarding streaming, there is already a lot of HDR content out there, especially newer shows. But stupid DRM has always pushed us to alternative sources when it comes to playback quality on Linux anyway.
no difference could be seen
If you’re not seeing difference of 4K and 1080p though, even up close, maybe your media isn’t really 4k. I find the difference to be quite noticeable.
yes, from the capture (camera) all the way to distribution the content has to preserve the HDR bit depth.
Ah, that’s what I thought. Thanks.
If you’re not seeing difference of 4K and 1080p though, even up close, maybe your media isn’t really 4k. I find the difference to be quite noticeable.
I tried with the most known test video Big Buck Bunny. Their website is now down and the internet archive has it, but I did the test back when it was up. Also found a few 4k videos on youtube and elsewhere. Maybe me and the people I tested it with aren’t sensitive to 4k video on 30-35 inch screens.
Anti Commercial AI thingyCC BY-NC-SA 4.0Inserted with a keystroke running this script on linux with X11 bash #!/usr/bin/env nix-shell #!nix-shell -i bash --packages xautomation xclip sleep 0.2 (echo '::: spoiler Anti Commercial AI thingy [CC BY-NC-SA 4.0](https://creativecommons.org/licenses/by-nc-sa/4.0/) Inserted with a keystroke running this script on linux with X11 bash’ cat “$0” echo ':::') | xclip -selection clipboard xte “keydown Control_L” “key V” “keyup Control_L”
But yes, it does make a difference how much of your field of view is covered. If it’s a small screen and you’re relatively far away, 4K isn’t doing anything. And of course, you need a 4K capable screen in the first place, which is still not a given gor PC monitors, precisely due to their size. For a 21" desktop monitor, it’s simply not necessary. Although I‘d argue, less than 4K on a 32" screen, that’s like an arms length away from you (like on a desktop), is noticeably low res.
No. Just like some people aren’t sensitive to 3D movies, we aren’t sensitive to 4k 🤷
Anti Commercial AI thingyCC BY-NC-SA 4.0Inserted with a keystroke running this script on linux with X11 bash #!/usr/bin/env nix-shell #!nix-shell -i bash --packages xautomation xclip sleep 0.2 (echo '::: spoiler Anti Commercial AI thingy [CC BY-NC-SA 4.0](https://creativecommons.org/licenses/by-nc-sa/4.0/) Inserted with a keystroke running this script on linux with X11 bash’ cat “$0” echo ':::') | xclip -selection clipboard xte “keydown Control_L” “key V” “keyup Control_L”
People aren’t “sensitive” to 3D movies due to lack of stereoscopic vision (That’s typical for people who were cross-eyed from birth for example, even if they had corrective surgery). Or they can see them and don’t care or don’t like the effect.
If you’re not “sensitive” to 4K, that would suggest you‘re not capable of perceiving fine details and thus you do not have 20/20 vision. Given of course, you were looking at 4K content on a 4K screen in a size and distance, where the human eye should generally be capable of distinguishing those details.
HDR is not just marketing. And, unlike what other commenters have said, it’s not (primarily) about larger colour bitrate. That’s only a small part of it. The primary appeal is the following:
Old CRTs and early LCDs had very little brightness and very low contrast. Thus, video mastering and colour spaces reflected that. Most non HDR (“SDR”) films and series are mastered with a monitor brightness of 80-100nits in mind (depending on the exact colour space), so the difference between the darkest and the brightest part of the image can also only be 100nits. That’s not a lot. Even the cheapest new TVs and monitors exceed that by more than double. And of course, you can make the image brighter and artificially increase the contrast but that‘s the same as upsampling DVDs to HD or HD to 4K.
What HDR set out to do was providing a specification for video mastering, that takes advantage of modern display technology. Modern LCDs can get as bright as multiple thousands of nits and OLEDs have near infinite contrast ratios. HDR provides a mastering process with usually 1000-2000nits peak brightness (depending on the standard), thus also higher contrast (the darkest and brightest part of the image can be over 1000 nits apart).
Of course, to truly experience HDR, you’ll need a screen that can take advantage of it. OLED TVs, bright LCDs with local dimming zones (to increase the possible contrast), etc. It is possible to profit from HDR even on screens that aren’t as good (my TV is an LCD without local dimming and only 350nit peak brightness and it does make a noticeable difference although not a huge one) but for “real” HDR you’d need something better. My monitor for example is Vesa DisplayHDR 600 certified, meaning it has a peak brightness of 600nits plus a number of local dimming zones and the difference in supported games is night and day. And that’s still not even near the peak of HDR capabilities.
tl;dr: HDR isn‘t just marketing or higher colour depth. HDR video is mastered to the increased capabilities of modern displays, while SDR (“normal”) content is not.
It’s more akin to the difference between DVD and BluRay. The difference is huge, as long as you have a screen that can take advantage.
Add comment