Jump to content

VAAPI tone mapping works well for one movie.


Recommended Posts

Posted (edited)

I have an interesting scenario where VAAPI with its defaults tone mapping works well for one movie but for all other movies I've tested so far, fails and fall back to software transcoding.

On the other hand, QuickSync tone mapping doesn't look nearly as good as when VAAPI tone mapping works. I had another thread Here about it. 

I have attached two logs below.

 

ffmpeg-transcode-5deec11f-ea1c-4fde-9977-0486ec8eb0e9_1.txt ffmpeg-transcode-298f9ef6-203a-44ec-a5fa-d3fe6fad5d2e_1.txt

Edited by jdazzle44
Happy2Play
Posted

Devs will have to explain the technical aspect of the failure.

 

22:57:17.702 [tonemap_vaapi@f2 @ 0x1e83640] No mastering display data from input
22:57:17.703 Error while filtering: Invalid argument
22:57:17.703 Failed to inject frame into filter network: Invalid argument
22:57:17.703 Error while processing the decoded data for stream #0:0
22:57:17.717 Conversion failed!

 

Posted

The VAAPI tone mapping doesn't work when there's no HDR metadata included in the video. IIRC we have a workaround for this in the beta channel.

What you can do is install the "Diagnostics Plugin" from the catalog. It lets you configure tone mapping for VAAPI and QuickSync.

Posted
3 hours ago, softworkz said:

The VAAPI tone mapping doesn't work when there's no HDR metadata included in the video. IIRC we have a workaround for this in the beta channel.

What you can do is install the "Diagnostics Plugin" from the catalog. It lets you configure tone mapping for VAAPI and QuickSync.

Thanks. I have been messing around with the QuickSync tone mapping settings using the Diagnostics plugin but most of the results are the same. I was just surprise that VAAPI with native HW tone mapping look really well for that one movie and was curios as to why.

I'll check out the beta channel.

Posted

The native VAAPI tone mapping is not configurable like the others tone mapping implementations.

Other users have found it often too dark. It depends on too many things unfortunately.

BTW: you can use the OpenCL tone mapping that is available for QuickSync with VAAPI as well. VAAPI at least decodes certain HDR metadata (which can also influence the OpenCL tone mapping).

Only in the very next beta, decoding of HDR side data is implemented for QuickSync. This could also make a change in certain cases.

Posted
1 hour ago, softworkz said:

The native VAAPI tone mapping is not configurable like the others tone mapping implementations.

Other users have found it often too dark. It depends on too many things unfortunately.

BTW: you can use the OpenCL tone mapping that is available for QuickSync with VAAPI as well. VAAPI at least decodes certain HDR metadata (which can also influence the OpenCL tone mapping).

Only in the very next beta, decoding of HDR side data is implemented for QuickSync. This could also make a change in certain cases.

I’ll test OpenCL with VAAPI and see how it compares to QuickSync. 
 

For my library I keep a 1080p copy of my 4K movies as time mapping isn’t where I’d like it to be yet but I’m very excited for the future of it. 
 

I can do six 4k to 1080p transcode with throttle off. With throttle I expect it to be a lot higher. That’s amazing for an IGPU!

  • Like 1
Posted
35 minutes ago, jdazzle44 said:

For my library I keep a 1080p copy of my 4K movies

That's always the best option.

35 minutes ago, jdazzle44 said:

as time mapping isn’t where I’d like it to be yet but I’m very excited for the future of it. 

Improvements can and will be made but it will never be equal to the SDR versions produced by the studios.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...