Dolby Vision Profile 8.1 with HDR10+ not working on LG webOS client

[Jollyrolly]

Hi there,

long time JF user here with clients on LG WebOS, AppleTV4k and Ugoos AM6b+ who started with xbmc on xbox360 around 20 years ago ;-)

Server: 10.10.7 on Windows 10 (Intel i3-12100, all SSD)
Client: LG WebOS (Version 23.22.02) on LG OLED48A29LA

Problem:
I have an issue with some Dolby Vision Profile 8.1 files not working on LG WEBOS. 
All files are:
- showing the Dolby Vision logo on TV
- are listed profile 8.1.
- are using ffmpeg remux

these two examples just show a completely green or black screen: 
  not_working_green_screen.txt (Size: 58.92 KB / Downloads: 23)
  not_working_black_screen.txt (Size: 119.82 KB / Downloads: 15)

Those two are working fine:
  working_bm.txt (Size: 101.07 KB / Downloads: 13)
  working_tlou.txt (Size: 29.21 KB / Downloads: 10) .

This is the server log:
  jf_log.txt (Size: 42.17 KB / Downloads: 15)

I'm not sure where I should look for differences in those logs and am glad for any help.

Kind regards

[bitmap]

A mediainfo output or ffprobe might prove me wrong, but there doesn't appear to be HDR fallback metadata that I can see. First, webOS TVs don't like DV in MKV files, so you would want to manually remux those to MP4 with external subs if you want to keep DV. Otherwise, webOS client will always try to fall back to HDR.

Nothing is being transcoded here, so that's probably the culprit. Do you have hardware acceleration or anything enabled? Can you try one of the non-working media and try to trigger a transcode? I believe you can do this with the settings in the webOS player (Quality: Auto --> something lower than the bitrate of the media).

[Jollyrolly]

A mediainfo output or ffprobe might prove me wrong, but there doesn't appear to be HDR fallback metadata that I can see.

Media info is showing DV with HDR10 on all four files. Example from one that is not working:

Video
Title: 4K HEVC Dolby Vision Profile 8.1 (HDR10)
Codec: HEVC
Profile: Main 10
Level: 150
Resolution: 3840x2160
Aspect ratio: 16:9
Interlaced: No
Framerate: 23.976025
Bitrate: 14608 kbps
Bit depth: 10 bit
Video range: HDR
Video range type: DOVIWithHDR10
DV title: Dolby Vision Profile 8.1 (HDR10)
DV version major: 1
DV version minor: 0
DV profile: 8
DV level: 6
DV rpu preset flag: 1
DV el preset flag: 0
DV bl preset flag: 1
DV bl signal compatibility id: 1
Color space: bt2020nc
Color transfer: smpte2084
Color primaries: bt2020
Pixel format: yuv420p10le
Ref frames: 1
 

Do you have hardware acceleration or anything enabled? [...] and try to trigger a transcode

I don't have hw acceleration enabled. Triggering the transcode by limiting bandwith results in fallback to HDR on the file that is not working.

BUT:

you would want to manually remux those to MP4 with external subs if you want to keep DV. Otherwise, webOS client will always try to fall back to HDR.

Jellyfin 10.9.0 introduced "Support for Dolby Vision playback remuxing" and it's exactly doing that on all four files, no transcode or manual remuxneccessary anymore, Screenshot from within JF:
The media is in an incompatible file container (MKV, AVI, WMV, etc) but both the video stream and audio stream are compatible with the device. The media will be repackaged losslessly on the fly before being sent to the device.
That's the reason why I upgraded my JF instance in the first place. ;-) It's doing the remux on all 4 files, all are 8.1 DV with HDR10 - only that 2 of them aren't working as intended (DV Logo is showing but black/green screen) and I cannot make out what the difference to the working ones is

[Jollyrolly]

I identified the reason by comparing severeal working/not working files.

All files that have DolbyVision 8.1 with HDR10+ are not working. I guess it's because the jellyfin remuxes dynamic metadata 2094 to static smpte 2084

Example:
Media Info: Dolby Vision, Version 1.0, Profile 8.1, dvhe.08.06, BL+RPU, no metadata compression, HDR10 compatible / SMPTE ST 2094 App 4, Version HDR10+ Profile B, HDR10+ Profile B compatible
remux: ColorSpace":"bt2020nc","ColorTransfer":"smpte2084","ColorPrimaries":"bt2020","DvVersionMajor":1,"DvVersionMinor":0,"DvProfile":8,"DvLevel":6,"

I guess it's exactly the same as Black screen at Dolby Vision, I have a theory with a HDR10+ Bug

Am I reading correctly that this will be fixed in 10.11.: Improve dynamic HDR metadata handling?

[Jollyrolly]

yesterday sth. funny happend. While testing I suddenly got HDR instead DV from the jellyfin "on the fly remux":

fallback hdr remux and working:
ffmpeg -analyzeduration 200M -probesize 1G -ss 01:04:01.462 -fflags +genpts  -i file:"E:\xyz.mkv" -map_metadata -1 -map_chapters -1 -threads 0 -map 0:0 -map 0:1 -map -0:s -codec:v:0 copy -tag:v:0 hvc1 -bsf:v hevc_mp4toannexb -start_at_zero -codec:a:0 copy -copyts -avoid_negative_ts disabled -max_muxing_queue_size 2048 -f hls -max_delay 5000000 -hls_time 6 -hls_segment_type mpegts -start_number 640 -hls_segment_filename "C:\ProgramData\Jellyfin\Server\cache\transcodes\63c55d6767590d6a46d7f0a7fe94ba15%d.ts" -hls_playlist_type vod -hls_list_size 0 -y "C:\ProgramData\Jellyfin\Server\cache\transcodes\63c55d6767590d6a46d7f0a7fe94ba15.m3u8"

After restarting jellyfin app it went back to the (not working) DV remux:
ffmpeg -analyzeduration 200M -probesize 1G -ss 01:12:31.096 -fflags +genpts  -i file:"E:\xyz.mkv" -map_metadata -1 -map_chapters -1 -threads 0 -map 0:0 -map 0:1 -map -0:s -codec:v:0 copy -tag:v:0 dvh1 -strict -2 -bsf:v hevc_mp4toannexb -start_at_zero -codec:a:0 copy -copyts -avoid_negative_ts disabled -max_muxing_queue_size 2048 -f hls -max_delay 5000000 -hls_time 6 -hls_segment_type mpegts -start_number 725 -hls_segment_filename "C:\ProgramData\Jellyfin\Server\cache\transcodes\275787677582c28c7cd6c45a4acdca90%d.ts" -hls_playlist_type vod -hls_list_size 0 -y "C:\ProgramData\Jellyfin\Server\cache\transcodes\275787677582c28c7cd6c45a4acdca90.m3u8"

Dunno if that is of any help