CCWGTV 4K Tonemapping QSV vs VAAPI

[mhutchison 5]

Pulling my hair out with the Transcoding/Tone Mapping issue with Coffee Lake/9500T on Linux. LMDE.

The first 4.10.0.1 beta fixed it. So I thought I was done. But, today realized that full QSV(OpenCL or QS) makes Tone Mapping on CCWGTV 4Ks look washed out compared to the internal tonemapping the GTV can do, no matter what algorithms. But the internal tone mapping of the GTV only works if it gets direct play.

After trying 4.8.10.0 again, all colors were indistinguishable from internal tonemapping of a full bitrate HDR video on the GTV. But, it defaults to VAAPI. There in lies why.

A full VAAPI workflow shows correct colors on the GTV when transcoding. 

Full QuickSync (OpenCL or QS) seems to be fine on Windows Chrome, iPad OS, Emby Android on S25U.

Also, the Tonemapping settings seem to be switched somehow. Have noticed this in multiple versions.

Disabling VAAPI makes TM go through VAAPI when QS encoders/decoders are disabled. Disabling QS makes it go through QS not OpenCL TM when QS encoders/decoders are enabled.

VAAPI CPU usage seems about the same as QS.

All this to make sure tone mapping will work in all cenarios.

On 4.10.0.2 now.

[Luke 42077]

 

Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks!