2024-06-19, 01:37 AM
Yes. Neither your CPU/iGPU nor dGPU can handle tone mapping. But an Intel Arc GPU would be able to handle it and then some.
2024-06-19, 01:37 AM
Yes. Neither your CPU/iGPU nor dGPU can handle tone mapping. But an Intel Arc GPU would be able to handle it and then some.
2024-06-19, 03:09 AM
(2024-06-19, 01:37 AM)TheDreadPirate Wrote: Yes. Neither your CPU/iGPU nor dGPU can handle tone mapping. But an Intel Arc GPU would be able to handle it and then some. Thanks, I will look into those for sure. So to summarize this issue: My LG TV Jellyfin app can play Dolby Vision Profile 5 content without issue. On the same LG TV connected via HDMI to my PC, the Jellyfin Web Player, MPV Shim, and directly in Chrome cannot, and it is transcoded due to 'The video's range type is not supported'. Should I be opening a bug report for this on the github perhaps? Or is this some weird in between on passing this data over HDMI or something?
2024-06-19, 04:07 PM
Try this. With MPV Shim, set vo to "GPU-Next" and enable tone mapping. This should convert Dolby Vision 5's proprietary color space to HDR10. Same with other DV profiles.
For web, use MS Edge. Chrome doesn't handle HDR, that isn't HDR10, very well.
2024-06-19, 04:11 PM
2024-06-19, 05:41 PM
(This post was last modified: 2024-06-19, 05:42 PM by podonnell. Edited 1 time in total.)
(2024-06-19, 04:11 PM)theguymadmax Wrote:(2024-06-19, 03:09 AM)podonnell Wrote: Should I be opening a bug report for this on the github perhaps? I'm confused, my TV/device's internal Jellyfin player can decode DV 5 and display this content as intended. So it's not a device issue. My experience in Windows / over HDMI is incompatible. The only way I see this not being a bug is if the defect has something to do with HDMI. Is there any device or HDMI setup that can properly display this type of content? Is tone mapping going to convert this to SDR? If so, I don't like that idea as a solution.
2024-06-19, 05:47 PM
(This post was last modified: 2024-06-19, 05:50 PM by TheDreadPirate. Edited 1 time in total.)
See my post before theguymadmax about some things to try to get HDR to work on your setups.
But to madmax's point, that this isn't a bug. Your device/hardware might support it, but the software player might not. Or it might only support it in a particular container. Or it might only support it in Windows but not Linux or vice versa. Or it might only support particular DoVi profiles. Or it will support it but only if you configure things in a particular way. Like I stated earlier: DoVi compatibility is a mess. Also, tone mapping, is the process of converting HDR to SDR. When Jellyfin transcodes will always convert HDR to SDR with or without tone mapping. With tone mapping the colors will be correct. Without tone mapping it will be washed out. Though, work is ongoing to enable HDR to HDR transcoding (no ETA). Tone mapping is a fall back when there isn't a path to direct play the HDR content for whatever reason.
2024-06-19, 06:56 PM
(This post was last modified: 2024-06-19, 06:58 PM by theguymadmax. Edited 1 time in total.)
HDR10 - Open standard for HDR.
HDR10+ - Royalty-free standard for HDR. Dolby Vision - Proprietary standard for HDR made by Dolby. The device needs to be licensed by Dolby to play DV files. When you buy a TV, Firestick, Nvidia Shield, etc. those devices are licensed to play DV and the apps on them can play DV. Your computer does not have a license* so it can’t decode DV files properly, the best it can do is fallback to HDR(if supported) or tonemapped. It's not a Jellyfin issue but an issue with DV and Windows. There have been recent developments in playing DV files in Windows, but it is still very hacky and restrictive and certainly doesn’t work with Jellyfin. *or if it does, the app needs to have specific specifications such as using the built-in Windows media player with the official Dolby extensions
2024-06-19, 07:13 PM
(This post was last modified: 2024-06-19, 07:13 PM by TheDreadPirate. Edited 1 time in total.)
To hammer home theguymadmax's point about the hacky ways of getting DoVi to work, when you configure MPV Shim to use GPU-Next it is actually converting the proprietary color space that Dolby Vision Profile 5 uses (IPTPQc2) over to BT2020 PQ, which is the color space that HDR10 uses.
2024-06-20, 02:46 AM
Wonderful information, thank you both. Totallly get it now with the licensing bit, that makes a lot of sense.
I think I'm fully happy with dedicating my TV JF app to watching this content. I'll just need to avoid it on other devices, which is totally fine. |
|
|