Posts: 1,066
Joined: Oct 2011
Reputation:
27
Soli
Posting Freak
Posts: 1,066
Let's see what happens, maybe the devs will come to their senses:-) I imagine there will be a graduall shift towards rec.2020 colorspace with at least 10bit precision for OS, displays etc, now that UHD BD is fiiinally here. Perfect time to throw out old stuff. But will of course be a bumpy ride. Would be nice with one colorspace that rules them all instead of all these Adobe RGB for hi quality prints, DCI P3 for Cinema etc. Ok ok, time to end off topic :-)
Posts: 1,066
Joined: Oct 2011
Reputation:
27
Soli
Posting Freak
Posts: 1,066
Sorry I have to ask: Would it be possible to do this the other way around? Now it seems were in a "fake" rgb full mode. What if we could tell GPU that we are in limited mode, so the GPU takes care of compressing the data levels. This way the OS doesn't have to support it. At the same time, we have a way of "annotating the surfaces" ( as you call it) when playing video.
Posts: 23,347
Joined: Aug 2011
Reputation:
1,085
fritsch
Team-Kodi Developer
Posts: 23,347
Intel's Limited Mode was:
Everything you get is clamped to 16:235 - no matter if it was clamped already (!) ... that's the whole issue we discuss here. All the other stuff, color processing, shaders for BT709/BT601 conversion and so on are fully implemented in kodi - the kernel does nothing for us in that regard. We also get the initial decoded video surfaces without any color banding, just the original untouched decoded data.
Is it now clear what this kernel fix is about?
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 1,066
Joined: Oct 2011
Reputation:
27
Soli
Posting Freak
Posts: 1,066
I think you misunderstand: I can live with double scaling/clamp with youtube, as long my video playback in Kodi is fine. It beats manually setting my TV to full rgb each time I launch Chrome from Kodi to browse around.
So my point was to let Intel clamp whatever they want, but leave a loophole for videoplayback where we tell the GPU to not touch anything. I know it's not possible today, but my real question was if this loophole could be implemented in the GPU driver (by Intel devs) or is it totally out of the question. In other words, would such a solution be possible to implement or would it not be possible because of hardware limitations?
Posts: 23,347
Joined: Aug 2011
Reputation:
1,085
fritsch
Team-Kodi Developer
Posts: 23,347
That's what the wayland guys want to do ... but yeah, as said, it's not there yet ... no API and no interface to tell them. No a hw limitation of course.
If you also use youtube. I would set the screen to full and use kodi's 8 bit dithering to upscale the content to full range -> best out of both worlds.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 6,746
Joined: Oct 2008
Reputation:
317
noggin
Posting Freak
Posts: 6,746
2016-01-11, 14:26
(This post was last modified: 2016-01-11, 14:27 by noggin.)
Question : Is it proposed that Wayland allows different areas of a screen, or screens (rectangular? irregular?) to have different colour spaces, with the final rendering deciding on the appropriate output space and converting non-native stuff? Presumably this gets complex when transparency gets involved? Or do modern screen renderers not work on a direct memory->raster mapping for output?
(I used to work in broadcast - where picture processing engines used to usually use one of two standards - read-side and write-side processing. Both had their merits and limitations, and back then a lot of the processing was done in hardware, or software controlled 'hardware' implemented in custom silicon)
Posts: 23,347
Joined: Aug 2011
Reputation:
1,085
fritsch
Team-Kodi Developer
Posts: 23,347
@noggin: Yes, that's what the intel dev told me. For more details ask daniels on #intel-gfx channel.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 23,347
Joined: Aug 2011
Reputation:
1,085
fritsch
Team-Kodi Developer
Posts: 23,347
The intel guy is the wayland guy.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 23,347
Joined: Aug 2011
Reputation:
1,085
fritsch
Team-Kodi Developer
Posts: 23,347
No, nobody is against it. But every single application on the planet needs to be changed. It won't be a solution that you can use "this year" or "next year". If you don't want to watch color perfect files for the time being - all fine :-)
I searched for a solution that given applications can use now.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 23,347
Joined: Aug 2011
Reputation:
1,085
fritsch
Team-Kodi Developer
Posts: 23,347
Only the first part. Not the xml.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.