[quietvoid]

Are you saying you cannot get that file to play with the proper colors using any of the test builds?

What I mean is that it doesn't matter if Dolby Vision is enabled or not, the image is incorrect.
This is in the case that I force the device (in my case FireTV Stick 4K) to output Dolby Vision, not through playing a file.

In regular playback, Kodi never triggers Dolby Vision. So yes, that is what I'm saying.

[MrMagic]

This is in the case that I force the device (in my case FireTV Stick 4K) to output Dolby Vision, not through playing a file.

Ok, got it.

I guess that means the Kodi test builds are not (yet) compatible with the FireTV Stick for DV playback. I'm using a Shield 2019 Pro myself and sofar it works great. Watched an entire DV movie tonight without issues.

[quietvoid]

Yea, though @hoppel118 seems to have had the same issue on a Shield.

[hoppel118]

You should really be testing a profile 5 file, because the metadata is necessary to display properly.
Like I mentioned before, @peak3d did say a while back that using ffmpeg as a demuxer wouldn't work for Dolby Vision.

Ok, thanks for clarifying. Yesterday evening I played a bit with the Android settings (dv activated or deactivated) and one time I got all (P4, P5, P7 FEL, P7 MEL, P81) the makeMKV dv test files to work. But this was also sporadic. Never got the dv trigger to work again for all profiles. Sometimes only the P4 file works, sometimes only the P4 and the P5 files work and sometimes the other files work. I can’t get it to work constantly. But the result of my play is that all the profiles work with my setup.

• horrible colors with the P5 mkv test file

Which Kodi version are you testing with? I tested the P5_Dolby_Amaze mkv file with @fandangos latest Jenkins build (kodi-20201222-c43636da-master-arm64-v8a) and the file played beautifully on my Philips 48OLED935, showing the "Dolby Vision" logo at the start of playback.

@quietvoid Thanks for the clarification regarding the P5 profile. This way we have a good way to test if the DV metadata is actually being used

Are all 5 makeMKV test files working for you? What are your Shield and Kodi settings exactly?

I am testing with all builds ( @Maven @fandangos @sk83 ). All builds give me the same result. I use the same Kodi settings for all 3 dvh1 and the hevc builds.

Yea, though @hoppel118 seems to have had the same issue on a Shield.

I wouldn’t say that’s the same issue you have with your FireTV Stick. Which profile exactly is or isn’t working for you?


P7 FEL and P7 MEL is the relevant profile for mkv files, because this is what makeMKV gives us. In my understanding the other profiles are used by different streaming services (and mp4 files). Am I wrong?

@all Is here anybody who has an overview which profile is used for what/which streaming service?

Regards Hoppel

[MrMagic]

Are all 5 makeMKV test files working for you? What are your Shield and Kodi settings exactly?

At one point I was able to play all 5 files. All of them displayed video, although the P4 file sometimes had wrong / over-saturated colours (but not always).

But it's very erratic. The delay settings seems to have some influence. Looks like 3.5 seconds is the sweet spot where I have the most success.

At some point, all videos started to display only a black screen with sound and I had to restart the Shield to get it working again. Sometimes it just helps to switch DV off and back on again on the Shield.
 

• The Shield is set to 4K 59.940 Hz with Dolby Vision enabled. This automatically sets the custom display mode to "3840x2160 59.940 Hz, YUV 422 12-bit Rec. 2020, Dolby Vision and HDR10 ready"
  
• Match content colour space is enabled on the Shield
  
• Shield is connected through a Denon AVR-X2300W with HDMI passthrough enabled
  
• Philips 48OLED935 has HDMI Ultra enabled on the HDMI ports
  
• Kodi -> System -> Display is set to:
  • Resolution: 3840x2160p
    
  • Refresh rate: 59.94
    
  • Delay after change of refresh rate: 3.5 seconds
    
  • Whitelist: Only selected all 3840x2160 resolutions (so I can use the Shield's AI upscaling for 1080p material)
    
  • Allow 3:2 pulldown refresh rates: Disabled
    
  • Allow double refresh rates: Disabled
    
• Kodi -> Player -> Videos
  • Adjust display refresh rate: On start/stop
    
  • Sync playback to display: Disabled
    
  • Render method: Auto detect
    
  • Enable HQ scalers for scaling above: 100% (so the Kodi scalers are not used and I can use the Shield's AI upscaling)
    
  • Allow HA - Mediacodec (Surface): Enabled
    
  • Allow HA - Mediacodec: Enabled
    
  • Use display HDR capabilities: Enabled
    

[rob87]

@MrMagic

Your have some interesting options set. I will check some as well.

I just dont understand why you have the whitelist active at 4k. There should not be any scaling anyway. Or do you have another reason for this?

Sry for offtopic

[quietvoid]

I wouldn’t say that’s the same issue you have with your FireTV Stick. Which profile exactly is or isn’t working for you?

P7 FEL and P7 MEL is the relevant profile for mkv files, because this is what makeMKV gives us. In my understanding the other profiles are used by different streaming services (and mp4 files). Am I wrong?

@all Is here anybody who has an overview which profile is used for what/which streaming service?

Regards Hoppel

I meant the color issue with profile 5, I can't play any Dolby Vision *files* at all in Kodi
Otherwise, yes only profile 7 is relevant but it is important to figure out if the output is correct. It's harder to compare regular HDR10 and Dolby Vision than it is with profile 5.

Most (if not all) streaming services use profile 5.

[m2k1980]

for all that having sometimes problems on the shield getting DV triggered correctly, maybe this could be helpfull. i have sometimes problems using DV on other apps, if the netflix or the disney app is started. for ex. netflix app is started but in background, because i used it some hours ago, if itry open a DV movie in disney+, dv will not triggered and the movie starts only in hdr.
so maybe you should close all apps with the nvidia taskmanager before trying or experimenting with DV on kodi.

maybe its usefull, it just only an idea to prevent issues.

[fandangos]

Exactly.
The Shield firmware has some bugs.

That has nothing to do with Kodi.

Even if Dolby Vision show as enabled it might not work.
You need to restart the Shield.

Here I have an EDID manager between my receiver and the tv. If I just turn it off and on again this will fix the problem.

[sk83]

I am testing with all builds ( @Maven @fandangos @sk83 ). All builds give me the same result. I use the same Kodi settings for all 3 dvh1 and the hevc builds.

Yea, though @hoppel118 seems to have had the same issue on a Shield.

Regards Hoppel

Regarding my build, it's using the dvhe decoder for profile 7 and below, and the dvh1 decoder for profiles over 7(ie. profile 8).

I'm also experiencing the problems you describe, with what seems like sporadic problems playing DV files - but I also experience this in other apps on the Shield.
For example, I have an exoplayer-based screensaver which plays the Apple Aerial DV files in random order. Sometimes, especially on the underwater videos, the colors become "shifted", and I have to restart the Shild to make everything work right. This makes me believe that the DV implementation on the Shield itself has some bugs.

Anyways, here are three different builds with different decoder configs:

All dvhe:
https://ufile.io/qwgtb5xj
All dvh1:
https://ufile.io/v0irsptw
dvhe up to and including profile 7, dvh1 for profile 8:
https://ufile.io/yu2otkfx

[MrMagic]

I did some googling regarding the difference between dvhe and dvh1 and found this PDF which has the following table in it:
 

Code:

Attribute     Value          Description

Codec_type    dvhe, hev1     dva* represents AVC-based Dolby Vision.
              dvh1, hvc1     dvh* represents HEVC-based Dolby Vision.
              dvav, avc3     avc* represents AVC.
              dva1, avc1     he** and hv** represent HEVC.

The table is confusing though, because it talks about he** and hv** both representing HEVC, but the description column talks about dva* in the row with values dvhe,hev1.

Also found this PDF about live streaming formats: https://professional.dolby.com/siteasset...r-2018.pdf

You guys probably already know about this, but I thought I would post it anyway

[sk83]

Anyways, here are three different builds with different decoder configs:

All dvhe:
https://ufile.io/qwgtb5xj
All dvh1:
https://ufile.io/v0irsptw
dvhe up to and including profile 7, dvh1 for profile 8:
https://ufile.io/yu2otkfx

OK, I was getting tired of compiling just for the sake of tweaking the decoders and timeout values.

This build reads the relevant settings from advancedsettings.xml:
https://ufile.io/s07ym02a

If the settings aren't present in advancedsettings.xml, default values are "amc-dvhe" for profile 7 and lower, "amc-dvh1" for profile 8, 5000 for inputbuffer timeout and 10000 for outputbuffer timeout.

Settings syntax:

Code:

<advancedsettings>
  <dv_decoder>
    <dvProfile7Format>amc-dvhe</dvProfile7Format>
    <dvProfile8Format>amc-dvh1</dvProfile8Format>
  </dv_decoder>
  <dequeue_timeout>
    <inputbuffer>25000</inputbuffer>
    <outputbuffer>25000</outputbuffer>
  </dequeue_timeout>
</advancedsettings>


[blackreign66]

Anyways, here are three different builds with different decoder configs:

All dvhe:
https://ufile.io/qwgtb5xj
All dvh1:
https://ufile.io/v0irsptw
dvhe up to and including profile 7, dvh1 for profile 8:
https://ufile.io/yu2otkfx

OK, I was getting tired of compiling just for the sake of tweaking the decoders and timeout values.

This build reads the relevant settings from advancedsettings.xml:
https://ufile.io/s07ym02a

If the settings aren't present in advancedsettings.xml, default values are "amc-dvhe" for profile 7 and lower, "amc-dvh1" for profile 8, 5000 for inputbuffer timeout and 10000 for outputbuffer timeout.

Settings syntax:

Code:

<advancedsettings>
  <dv_decoder>
    <dvProfile7Format>amc-dvhe</dvProfile7Format>
    <dvProfile8Format>amc-dvh1</dvProfile8Format>
  </dv_decoder>
  <dequeue_timeout>
    <inputbuffer>25000</inputbuffer>
    <outputbuffer>25000</outputbuffer>
  </dequeue_timeout>
</advancedsettings>


Cool!!!! I'm going to test this build along with advancedsettings. Thank you

[MrMagic]

OK, I was getting tired of compiling just for the sake of tweaking the decoders and timeout values.

This build reads the relevant settings from advancedsettings.xml:
https://ufile.io/s07ym02a

Very nice! I hope @fandangos can add this to his Matrix builds too. I prefer Matrix because of the Dark Grey subtitle color option

[fandangos]

I'm following this thread closely.

If a good value is found for timeout and preferred renderer is set, I can change my commit to it.

Still I believe this is caused by some bugs in the shield firmware and no value or render method will solve it.

Maybe, what is needed is some kind of clear memory after the movie ends or any way to properly kill the renderer.
Or even a hdmi state or EDID recheck if possible.