Jump to content

Conversion failure with HDR10 vaapi


PaoloPinkel
Go to solution Solved by PaoloPinkel,

Recommended Posts

This works for me on a 920+ converting HDR 4K media with tone mapping.

It might be something media specific.

Can you show us the Media Info (bottom of detail screen) for this media?

Link to comment
Share on other sites

Could you try a conversion on a couple of other HDR10 files to see if this is isolated or not?

Link to comment
Share on other sites

PaoloPinkel

Yes, I tried a conversion with a file where it has run before. The conversion is still running... 

Link to comment
Share on other sites

PaoloPinkel

 

The conversion with another HDR file was successfully performed. Why does this one file not work?

 
Link to comment
Share on other sites

There are multiple ways how HDR side data can be encoded in an HEVC video. ffmpeg doesn't support all of them and VAAPI native tone mapping doesn't work when this data is not available.

What you can do is to install the diagnostics plugin and choose OpenCL tone mapping for VAAPI. This can work even without HDR side data.

Link to comment
Share on other sites

47 minutes ago, softworkz said:

What you can do is to install the diagnostics plugin and choose OpenCL tone mapping for VAAPI. This can work even without HDR side data.

Is that better in general than using QuickSync?

Link to comment
Share on other sites

37 minutes ago, cayars said:

Is that better in general than using QuickSync?

The OpenCL tone mapping is exactly the same but QuickSync is usually faster. 

Link to comment
Share on other sites

So any reason not to just enable Quicksync and move it to the top of the list for each codec type?

Link to comment
Share on other sites

13 minutes ago, cayars said:

So any reason not to just enable Quicksync and move it to the top of the list for each codec type?

Should be fine, except for MPEG2Video where QuickSync has issues sometimes.

  • Thanks 1
Link to comment
Share on other sites

PaoloPinkel

@softworkz

your diagnostics plugin does not open, no matter if desktop (chrome and edge) or android app.

1150238698_2021-07-3110_40_20.thumb.jpg.318ab437771616626702649a15e37e21.jpg

Link to comment
Share on other sites

Thanks for the log. Can't see anything wrong there.

Could you please go to the server dashboard in Chrome browser, press F12 to open the dev tools, try to access the diagnostic options and then watch for any errors in the javascript console?

Link to comment
Share on other sites

Thanks a lot, that's actually the culprit. It's a change for which the Diag Plugin has already been updated in the beta channel, but I missed that this change has also made it into the 4.6.4.0 release.

Please restart your Emby Server. It should auto-detect the update for the plugin. Then another restart to complete the update and you should be ready to go. 

Edited by softworkz
Link to comment
Share on other sites

  • Solution
PaoloPinkel

Hi softworkz,

perfect, the conversion is running! Many thanks also to cayars. Great support from you.

  • Thanks 1
Link to comment
Share on other sites

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...