[quietvoid]

Oh, yeah, are you using a fire stick?
Have you ever figured out what is needed for it? 

Maybe it's just a matter of figuring the right decoder name.

I still believe it's related to ffmpeg removing something, or doing something differently.
peak3d did his tests on a fire stick a while back and that was his conclusion (ffmpeg couldn't be used to demux because it's injecting "metadata" separately).

The decoder used is already correct, there's just a missing piece that makes the device not use the Dolby Vision data at all.
Have not figured out what this metadata is about, as the ffmpeg logs show the RPU NAL is skipped regardless of using ffmpeg or not.

The same behavior seems to affect Sony's Android TV sets.

[fandangos]

And Plex works with fire stick?

[quietvoid]

Yep. ExoPlayer alone as well.
However both use ExoPlayer, ffmpeg is not involved in client side processing.

[fandangos]

That's interesting.

So, that code we have for ffmpeg supporting mkv DV isn't used by plex when playing on Android?
That's only used on plex servers?

So, Plex, Emby all use Exo?

That's kinda lazy.

[MrMagic]

That's interesting.

So, that code we have for ffmpeg supporting mkv DV isn't used by plex when playing on Android?
That's only used on plex servers?

So, Plex, Emby all use Exo?

That's kinda lazy.

Yep, in the Plex client it even shows "ExoPlayer" when you call up the Playback Info screen on the Shield.

Although if you choose to use the old player in Plex, DV is still triggered. But I don't know what that player is based on.

[fandangos]

Well, when the wheel already exists.. you don't need to invent it. (Not sure how that translates to English) LoL

Let's wait for ffmpeg team.
Maybe when we have an official commit it might work for fire stick and android tvs too.

[blackreign66]

Been away for a while, much to do at work. Here's an 18.9 build with a default input buffer timeout value of 10000 and with WaitForFrame value increased to 250.
Anyway, I haven't had any trouble the last weeks with any of the builds we tested. Two things to consider:
- I've not watched any profile 7 content, only profile 8
- I've set minimum SMB version to 3. This seems to have improved network speeds an responsiveness a bit.

18.9 build

Have you added this commit?
https://github.com/fandangos/Kodi-HDR-Ed...00a29R1382

Line 1382 is the function stoping playback before it hangs/crashes.

No, that one escaped me. Here's an updated build with this fix implemented:


https://ufile.io/h6acjgk2

Are you able to play profile 7 DV movies with this version without stuttering? Just wondering if its something on my end that's causing stuttering whenever I play a dv movie. The previous version you posted didn't stutter at all.

[deejay59]

@fandangos I see Kodi 19 have reached RC1. Is there a posibility you will do builds based on the major milestones? (RC's and stable i mean) until your great work hopefully gets included in the early Kodi 20 builds

Updated up to today 17/01/2021 (DD/MM/YYYY)

64 bits version (Kodi19DV-RC1-64bits.apk)
https://mega.nz/file/SIMzXQzC#3twHreYliO...5Rr5rsET_w

32bits version (Kodi19DV-RC1-32bits.apk)
https://mega.nz/file/TIknHQ6Y#XPuJ4XLIh5...Ym3vkWBcbw

Dolby Vision code is exactly the same. No updates. No changes.

I'm building using my git here:
https://github.com/fandangos/Kodi-HDR-Ed...ee/updated

Branch: updated

Big Thanks! very good job!

[MrMagic]

Let's wait for ffmpeg team.
Maybe when we have an official commit it might work for fire stick and android tvs too.

DV already works on Philips TVs with Android (at least on my 48OLED935).

I just tried your latest 32-bit build on it and the only issue I see is that sometimes the screen stays black when switching between the various MKV test files with different profiles.

Profile 7 MKVs with full rips always seem to work just fine though.

[teof13]

Is DV working on Sony Android TVs too?

[quietvoid]

Is DV working on Sony Android TVs too?

Try it for yourself..
Only mention I remember: https://github.com/xbmc/xbmc/issues/1889...-752788833

[Fehritale]

I have just read something interesting in the Shield forum.
They acknowleged that there is still a bug in the DV decoder, discovered by/with the Plex team.
Forum link

Could this have something to do with the issues mentioned here, that very rarely the playback does not start?

[fandangos]

Posted there and it would be a good idea if other people do the same.

Also there's a new firware from yesterday. It might be a good idea to redo the testing and check if they silently fixed DV playback.

[MrMagic]

Posted there and it would be a good idea if other people do the same.

Also there's a new firware from yesterday. It might be a good idea to redo the testing and check if they silently fixed DV playback.

Nvidia has actually confirmed they could reproduce the issue that Plex reported only 3 hours ago:

https://www.nvidia.com/en-us/geforce/for...y/2980521/

So this means it's not fixed in the 8.2.2 build, because they are still looking into it.

[quietvoid]

I've been debugging playback for my Firestick, the metadata doesn't seem to be skipped by ffmpeg.
For profile 5, at least setting the MediaFormat to output PQ makes the TV switch to HDR10, but never Dolby Vision.

I've tried setting the profile, level, codecs-string, nothing makes a difference.
The decoding also starts only after the first demuxed buffer conversion, which contains the metadata NAL unit.
So it should be contained into the very first buffer sent to the decoder.

The only thing that might differ is the buffer format the decoder expects, but there's no documentation.
Running out of ideas as to why it fails to work.

Anyways, as I type this I discover a way to make it trigger Dolby Vision. Setting the NAL header length to 4 for the unit.
All the mp4, mkv samples work perfectly except for FEL. As expected.