[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