[qp9013625]

Since you said you can explain things to me (us), I'd like to ask another question:

Besides the performance issue, this putSurface method always scaled the limited color range of the original files to FULL RGB. Introducing Banding or even worse it was scaled twice, e.g. back to limited, by the driver itself. All this won't happen anymore, cause the new zero copy approach allows us to directly render the decoded NV12 surface with our own shader. So all color conversions are in our hands now. You can savely use "Prefer VAAPI Render Method" set to on again and don't need to waste CPU cycles with bypassing this Method. All colors will be fine. If you have a Limited Range TV - you need to set "Use Limited Range" to On additionally. Also make sure that your GPU itself is running at full range, which this howto and also all OpenELEC images will do by default.

Why, in that case, would you have to set your GPU (driver) to output at full range?

You said the issue was that the limited range video was expanded to full range.

You said this would no longer happen.

But then why set the driver to output at full range?

Why can't we leave the GPU output (driver) at limited range if this no longer happens?

Wouldn't it make more sense to leave everything at limited range (when using a limited range TV)?

If we set the GPU (driver) to output at full range, then we are expanding the limited range image to full range again and it's then being reduced to limited range again by the TV, right? So we have a "double scale" again...

Or don't we?