Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror

Comment Re:so for AMD then (Score 1) 11

HL Lost Coast does not use HDR

It renders in HDR, then it does cute tricks to represent the HDR content on a normal display. This still improves the visuals in both bright and dark areas, accomplishing a huge percentage of what you expect from HDR.

This is similar to what is called "HDR" in images

The scare quotes ship has sailed, that's always going to be called HDR.

HDR support in Wayland is accomplished by allowing the clients to set color space and giving them floating point pixel buffers. NV does all of this just fine.

It does, what it doesn't do is work reliably.

The NV drivers are still fully featured.

IME they've been problematic when I've tried Wayland. I've been sticking with X11 as a result. It's then disappointing that 30 bpp does not work well with Nvidia with X, but sadly, it really does not. Which returns to, the Nvidia drivers are a letdown compared to the modern OSS ATI drivers. If it weren't for CUDA, I would have gone with ATI in this machine.

Comment Re:so for AMD then (Score 1) 11

Nowhere did I say that X did HDR.

What I said about this being the domain of AMD is that Nvidia drivers for Wayland don't work well. And this is becoming a problem for Nvidia more and more in general, which is ironic because I've always used them specifically because AMD was bad at drivers. Last I looked they still were on Windows, maybe that's better now, but I don't care about that at all.

The other thing I said was that 10 bpp is a requirement for output in the most commonly used HDR Display output format, which is still true.

I still don't understand why you find any of this confusing.

Comment Re:so for AMD then (Score 1) 11

I believe we've been over this before. It appears I failed at making you understand.

You cannot explain to me what you do not understand.

>8bpp is not HDR.

If they weren't talking about higher bit depth, it wouldn't matter which display system was involved. The most popular format for HDR displays to support is HDR10, which involves 10bpp. You can view HDR content on 8bpp displays, but you won't get full fidelity. Remember Half Life 2: Lost Coast? (Apparently Riven also used HDR techniques, can't say I noticed.)

I can make HDR images on my camera using Magic Lantern, and have done. It uses the technique where they're generated from bracketed exposures. They are striking even on a normal display with a typical color gamut.

Even displays with 8bpp panels can get more out of having a HDR signal (including >8bpp) so even I would like to have it, with my cheapass LG43UT80[00].) Unfortunately, I have an Nvidia card.

Now, what were you saying? I don't remember it being very interesting, but do go on.

Comment Re: Wrong reason... (Score 1) 30

I remember exactly what they did, they failed to check their output even slightly, the absolute clowns. It's very basic rules they broke, that even a student can grasp, and they did it while in the kernel.

But as you mentioned, and as I have mentioned repeatedly in the discussions we had around that time (when I was actually impacted by their failure, and Microsoft's bad patch about a week later, good times) they did use eBPF on Linux, but did not use it on Windows even though it was available on Windows as well. Their excuse, as I recall, was that it was insufficiently mature on Windows. This sounds plausible to me, but since I don't know enough about them to know whether it is. Maybe they just hadn't gotten around to it, and it was plenty mature, for all I know. Then again, if they're making a new interface with industry input now, it probably wasn't...

Slashdot Top Deals

An engineer is someone who does list processing in FORTRAN.

Working...