HDR10 mkv with DV & HDR10+ metadata streams doesn't display Dolby Vision picture

Help and Support Vero V
1

I have just experienced this issue with an mkv, a HDR10 with DV & HDR10+ metadata streams. It triggers the Dolby Vision logo and plays the audio but displays a blank screen.
If I go into Settings>Player>Video and under HDR processing change it from Auto to Force HDR (no DV) and try again it plays triggering the HDR logo and I get sound and video.
My TV in an LG OLED so it supports HDR10 and Dolby Vision, but not HDR10+

Here is a debug log.
https://paste.osmc.tv/tarayoripe

The 25MB sample file I created from the start of the 23GB file and used for the debug is named
SMPTE ST 2094 App 4, Version HDR10+ Profile B sample.mkv
MediaInfo
General
Unique ID : 121275135162598439634524325578664751215 (0x5B3CBDCE7B91671F97C48909EEFEB06F)
Complete name : SMPTE ST 2094 App 4, Version HDR10+ Profile B sample.mkv
Format : Matroska
Format version : Version 4
File size : 28.5 MiB
Duration : 18 s 810 ms
Overall bit rate : 12.7 Mb/s
Frame rate : 23.923 FPS
Encoded date : 2025-07-19 22:33:39 UTC
Writing application : mkvmerge v91.0 (‘Signs’) 64-bit
Writing library : libebml v1.4.5 + libmatroska v1.7.1

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@High
HDR format : 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
Codec ID : V_MPEGH/ISO/HEVC
Duration : 18 s 810 ms
Bit rate : 11.9 Mb/s
Width : 3 840 pixels
Height : 1 604 pixels
Display aspect ratio : 2.39:1
Frame rate mode : Variable
Frame rate : 23.923 FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.081
Stream size : 26.7 MiB (94%)
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0050 cd/m2, max: 4000 cd/m2
Maximum Content Light Level : 1032 cd/m2
Maximum Frame-Average Light Level : 386 cd/m2

Audio
ID : 2
Format : E-AC-3 JOC
Format/Info : Enhanced AC-3 with Joint Object Coding
Commercial name : Dolby Digital Plus with Dolby Atmos
Codec ID : A_EAC3
Duration : 18 s 784 ms
Bit rate mode : Constant
Bit rate : 768 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Stream size : 1.72 MiB (6%)
Language : English
Service kind : Complete Main
Default : Yes
Forced : No
Complexity index : 16
Number of dynamic objects : 15
Bed channel count : 1 channel
Bed channel configuration : LFE
Dialog Normalization : -27 dB
compr : -0.28 dB
dialnorm_Average : -27 dB
dialnorm_Minimum : -27 dB
dialnorm_Maximum : -27 dB

Text #1
ID : 3
Format : UTF-8
Codec ID : S_TEXT/UTF8
Codec ID/Info : UTF-8 Plain Text
Duration : 2 s 695 ms
Bit rate : 20 b/s
Frame rate : 0.371 FPS
Count of elements : 1
Stream size : 7.00 Bytes (0%)
Title : CC
Language : English
Default : No
Forced : No

Text #2
ID : 4
Format : UTF-8
Codec ID : S_TEXT/UTF8
Codec ID/Info : UTF-8 Plain Text
Bit rate : 0 b/s
Count of elements : 0
Stream size : 0.00 Byte (0%)
Language : English
Default : Yes
Forced : No

Text #3
ID : 5
Format : UTF-8
Codec ID : S_TEXT/UTF8
Codec ID/Info : UTF-8 Plain Text
Bit rate : 0 b/s
Count of elements : 0
Stream size : 0.00 Byte (0%)
Title : Latin American
Language : Spanish (Latin America)
Default : No
Forced : No

Text #4
ID : 6
Format : UTF-8
Codec ID : S_TEXT/UTF8
Codec ID/Info : UTF-8 Plain Text
Bit rate : 0 b/s
Count of elements : 0
Stream size : 0.00 Byte (0%)
Title : Canadian
Language : French (CA)
Default : No
Forced : No

Menu
00:00:00.000 : en:Chapter 01

From a look at the debug file it looks like the issue is that the file is SMPTE ST 2094 App 4 but in the debug log it is being identified as smpte2084.
Stream #0:0: Video: hevc (Main 10), yuv420p10le(tv, bt2020nc/bt2020/smpte2084), 3840x1604 [SAR 1:1 DAR 960:401], 23.98 fps, 23.98 tbr, 1k tbn (default)

I can upload the 25MB sample file if someone can tell me where/how.

1 Like
4

Do you have a Google Drive? Just upload it and allow access to all.

I think I know what’s going on but need that clip to confirm.

Also: do you have something between Vero and the TV? AVR?

5

I have a hdfury avr key between the Vero V and my TV because my avr is old and the hdmi ports only support 1080p60.

I’ll make the sample available on Google drive this afternoon when I get on my laptop.

6

Sample file Google Drive link

2 Likes
7

Same behaviour for me, with this sample audio OK, video blank/black
(but detects DV), with: Vero V > AVR > LG OLED

For the sample, Media Info says :

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

8

Can you post /sys/class/amhdmitx/amhdmitx0/edid please?

For the record, it plays as DV on my Philips, but if I turn off DV it plays as HDR10, not HDR10+ as it should. But I think I know why. (fixed)

9

cat /sys/class/amhdmi/amhdmi0/edid results in No such file or directory
did you mean
cat /sys/class/amhdmitx/amhdmitx0/edid
that gives
osmc@verov:~$ cat /sys/class/amhdmitx/amhdmitx0/edid
Rx Manufacturer Name: GSM
Rx Product Code: 0001
Rx Serial Number: 01010101
Rx Product Name: LG
Manufacture Week: 1
Manufacture Year: 2018
Physical size(mm): 1600 x 900
EDID Version: 1.3
EDID block number: 0x1
blk0 chksum: 0x62
Source Physical Address[a.b.c.d]: 1.1.0.0
YCC support 0x03, VIC (native 97):
ColorDeepSupport 0xb8 10/12/16/Y444 1/1/0/1
97 96 16 31 102 101 4 19 5 20 3 2 18 32 33 34 21 1 93 94 95 98 99 100 63 64 95 94 93 98
Audio {format, channel, freq, cce}
{1, 1, 0x7f, 0x07}
{1, 5, 0x7f, 0x07}
{1, 7, 0x7f, 0x07}
{2, 5, 0x07, 0x55}
{7, 5, 0x1f, 0xc0}
{10, 7, 0x06, 0x00}
{12, 7, 0x54, 0x00}
{11, 7, 0x7e, 0x01}
Speaker Allocation: 0x5f
Vendor: 0x000c03 (HDMI device)
MaxTMDSClock1 300 MHz
Vendor2: 0xc45dd8
MaxTMDSClock2 600 MHz
vLatency: Invalid/Unknown
aLatency: Invalid/Unknown
i_vLatency: Invalid/Unknown
i_aLatency: Invalid/Unknown
Colorimetry: 0xc0
SCDC: 1
RR_Cap: 0
LTE_340M_Scramble: 0
DolbyVision1 HDR/13 DeepColor
checkvalue: 0x62b00000
osmc@verov:~$

10

Thanks, but that was a question for @thechrisgregory. I want to see if he also has

11

Here’s my EDID (looks to be DolbyVision2 HDR/13 DeepColor)

Rx Manufacturer Name: GSM
Rx Product Code: c0c8
Rx Serial Number: 01010101
Rx Product Name: LG
Manufacture Week: 1
Manufacture Year: 2020
Physical size(mm): 1600 x 900
EDID Version: 1.3
EDID block number: 0x1
blk0 chksum: 0x19
Source Physical Address[a.b.c.d]: 2.1.0.0
YCC support 0x03, VIC (native 97):
ColorDeepSupport 0xb8 10/12/16/Y444 1/1/0/1
97 96 102 101 16 31 4 19 5 20 3 2 18 32 33 34 21 93 94 95 98 63 64 95 94 93 98 374 373
Audio {format, channel, freq, cce}
{1, 1, 0x57, 0x07}
{2, 5, 0x07, 0x50}
{10, 7, 0x07, 0x01}
{12, 7, 0x04, 0x03}
Speaker Allocation: 0x00
Vendor: 0x000c03 (HDMI device)
MaxTMDSClock1 300 MHz
Vendor2: 0xc45dd8
MaxTMDSClock2 600 MHz
ALLM: 1
vLatency: Invalid/Unknown
aLatency: Invalid/Unknown
i_vLatency: Invalid/Unknown
i_aLatency: Invalid/Unknown
Colorimetry: 0xc0
SCDC: 1
RR_Cap: 0
LTE_340M_Scramble: 0
DolbyVision2 HDR/13 DeepColor
checkvalue: 0x19a60000

12

Thanks. Can we go one deeper and get rawedid from you, then?

13

… get rawedid from you, then?

00ffffffffffff001e6dc8c001010101011e010380a05a780aee91a3544c99260f5054a1080031404540614071408180d1c00101010108e80030f2705a80b0588a0040846300001e6fc200a0a0a055503020350040846300001e000000fd0018781e873c000a202020202020000000fc004c472054562053534352320a20011902035ff25761606665101f04130514030212202122155d5e5f623f402c0957071507505707016704036e030c002100b83c2400800102030468d85dc40178800302e200cfe305c000e3060d01e30e7675e20f0feb0146d0004803768a66727c0000000000000000000000000000000000000000000000000000000000000000a6

14

Oh dear. That means there’s something other than my theory at play here.

16

Hi

Hopefully the issue is now addressed.

I’d appreciate it if you could test this and provide feedback before we potentially release this as an update to other users. To test this update:

  1. Login via the command line
  2. Run the following command to add the staging repository:
    echo 'deb http://apt.osmc.tv bullseye-devel main' | sudo tee /etc/apt/sources.list.d/osmc-devel.list
  3. Go to My OSMC → Updater → Manual Controls → and select Check for Updates now. When prompted to do so on screen, please choose to install the update.
  4. Your system should have have received the update.

Please see if the issue is resolved.

I also recommend you remove /etc/apt/sources.list.d/osmc-devel.list after updating.

This will deactivate the staging repository. You can do so with the following command:
sudo rm /etc/apt/sources.list.d/osmc-devel.list.

Please note that we will automatically disable this update channel after 14 days on your device in case you forget to do so to ensure that your system reverts to the stable update channel.

1 Like
22

I have updated my Vero V with the staging repository and can confirm that kodi now displays the video as Dolby Vision for both the sample and the full 23gb original file, I even watched the first five minutes and skipped around a bit.

in case you forget to do so to ensure that your system reverts to the stable update channel

Um, may I have the command for that please? (Not that I’m going to revert until I’ve watched the entire film tomorrow evening.)

23

Great news! Don’t worry about ‘reverts’. It doesn’t do that immediately. If you issue this command now:

Nothing will happen until the next release which will include this fix.

24

Already deleted the file. Thank you very much for the impressive speed at figuring out what was going on and creating a fix. (This is a major part of why I spend my money on devices with good reputations for after sale support).

Is it possible to get a very short layman’s explanation of what was going on? I’m a very curious person by nature and it’s kinda bugging me not knowing.

2 Likes
25

DV metadata comes in many flavours, mostly ‘version 2.9’ or ‘version 4.0’. Your TV doesn’t understand 4.0. So files with version 4.0 metadata have to be filtered to remove it. Nothing to do with HDR10+ as it turns out.

2 Likes
26

And for this reason people shouldn’t just say they have an LG OLED.
They should specify year and/or generation.
LG OLEDs C8 and prior are CMv2.9; C9 and later are CMv4.0.

2 Likes
27

I just came across that little nugget while looking up what the difference was. I did save something like £1k by buying the previous years model (a C8).

I’m happy my TV is still good after six years, I’d heard stories about burn in and pixels going bad that I was a little concerned. I did have to run pixel refresher manually last night to fix a stuck pixel (haven’t done that in over a year), maybe the universe is telling me to start saving up.

I’m probably overdue for a receiver upgrade too, and the latest oleds have higher nits…

28

I have LG C3 OLED which is newer than C8 and have the same issue with the sample file - black screen with sound and Dolby Vision logo