[tRiBUN]

Hi,

actually I have several issues with Kodi and my Google TV Streamer.
First is some weired loosing config files (Different Topic / Post).
Second thing is for about 5 weeks or so DolbyVision files show only black screen. Not sure if there was any update (Google or even Kodi).

The Google TV Streamer is able to play DolbyVision, and in most apps (e.g. Disney+) it is running fine. Also in Kodi the Aerial Addon is able to run in DolbyVision. Only MKV files, also files which worked before, show a black screen. My TV does show the mode change to DolbyVision and audio is working but no video.
Disabling DolbyVision is a workaround, so DolbyVision MKVs can run in simple HDR mode but with much lower brightness than DolbyVision.

I've read a lot about some adjusted ExoPlayer and external player setup, but I'm not able to find these adjusted APK and I guess it should not be neccessary as the Streamer is able to play DolbyVision or is even runs fils internally wth this ExoPlayer. The texts were a bit confusing me.

Anyway does anyone have a hint or solution for this?

[Hitcher]

To receive meaningful assistance you will need to provide a full debug log.

The instructions are here... debug log (wiki)

If you are using the Basic Method, then ensure the following is applied...
1.Enable debugging in Settings>System Settings>Logging,
2.Restart Kodi
3.Replicate the problem.
4.Upload the log to Kodi Paste Site manually or use the Kodi Logfile Uploader. (wiki) With either method post the link to the log back here.

If you are using the Advanced Method ensure you have correctly created and applied the advancedsettings.xml file (wiki)

In both instances, you should see the word DEBUG throughout the log.

Note: Full logs only. No partial or redacted logs
Do NOT post your logs directly into the forum. Use the Kodi Paste Site. Post the link to your pasted log in the forum

[tRiBUN]

Thanks for the hint. Sure without log it is a bit ...

Especially one entry is quite often in the log but I'm not sure if this is the real cause.

2024-12-07 12:19:29.219 T:24304 debug : ffmpeg[0xf24b4b40:
: [swscaler] No accelerated colorspace conversion found from yuv420p to bgra.]

DolbyVision Activated Log

[fritsch]

Thanks for the hint. Sure without log it is a bit ...

Especially one entry is quite often in the log but I'm not sure if this is the real cause.

2024-12-07 12:19:29.219 T:24304 debug : ffmpeg[0xf24b4b40:
: [swscaler] No accelerated colorspace conversion found from yuv420p to bgra.]

DolbyVision Activated Log

That part of the log only talks about thumbnail processing where a jpeg (yuv420p) cannot be converted in accelerated manner to bgra, which we use in our textures.

Your issue seems to be your SMB share ... VideoPlayer hits EOF.
Did you change that recently? Change SMB version?

Try NFS instead.

[tRiBUN]

Moin fritsch,
thanks for getting into it.

No, my NAS is still the same SMB2 minimum and SMB3 maximum Version. I would like not to activate NFS anywhere in my home (I prefere user login via SMB).
At least the video shows up if I deactivate DolbyVision in Kodi, so with same SMB Login settings, which gives me some more doubt that NFS would make a difference or do you think so?

Not sure why it says end of file but close to this log entry it also says something about the profile which I don't understand. Only, as far as I know, profiles are needed to use the correct collormapping and brightness settings. But with my not existing knowledge in this case, I don't know what to do with this information.

Code:

2024-12-07 12:19:16.002 T:24518 error <general>: CDVDVideoCodecAndroidMediaCodec::Open profile not supported: 256

Until next log entry the file was running (Audio only) until I stopped it. Via remote not via On Screen, as this was not visible too.

2024-12-07 12:19:28.549 T:24518 debug : Thread VideoPlayer -1222565440 terminating:

[fritsch]

Please read your log to the end.

Kodi is trying all decoders in a row, the log you cite is for all of them failing to open your dv codec, which is perfectly fine.
It continues here:

2024-12-07 12:19:16.002 T:24518    info <general>: CDVDVideoCodecAndroidMediaCodec::Open Testing codec: c2.mtk.dvhe.sth.decoder
2024-12-07 12:19:16.060 T:24518   debug <general>: CDVDVideoCodecAndroidMediaCodec::InjectExtraData
2024-12-07 12:19:16.102 T:24518    info <general>: CDVDVideoCodecAndroidMediaCodec::Open Using codec: c2.mtk.dvhe.sth.decoder
2024-12-07 12:19:16.102 T:24518   debug <general>: CDVDVideoCodecAndroidMediaCodec::UpdateFpsDuration fpsRate:24000 fpsscale:1001, fpsDur:41708
2024-12-07 12:19:16.103 T:24518   debug <general>: CVideoPlayerVideo::OpenStream - open stream with codec id: 173

And succesfully opens your dvhe decoder and does its job  or tries to - all good from kodi side of things.
There are some DV formats where the mtk chips have issues with ... can't remember the exact DV profile though.

So - if you post a working log with another DV file - we can cross verify. In general - as it worked before - kodi did not change in stable version for many months ... unlikely the issue comes from kodi.

@quietvoid might be able to tell.

[tRiBUN]

Well reading, understanding or just gussing about the log file entires is a big difference for me
Sorry, I can only guess with, lets say, partial dangerous knowledge

Anyway with your tipp of comparison I activated DolbyVision again and started a much older file (Finch). It worked
Another try (Transformers) didn't work. Switching off DolbyVision and so it worked with HDR10.

All of this above in another Log file. Hope you can compare it so I understand why latest / some / most files do not work.

[fritsch]

No difference in that format that I can see. Might want to post the mediainfo output of the non working one, maybe that gives a clue.

[tRiBUN]

Both files have some differences and so I hope these help for diagnose and btw. thanks for still trying to help.
Finch Media Info
Transformers Media Info

[izprtxqkft]

this issue has similarities to reports of issues on the fire stick 4k max with the cousin MediaTek MT8696T
that led to having the dolby vision compatibility added to kodi in the first place

possibly something to do with non-standard resolutions but i believe that was an entirely different issue

i wasn't following all the issues on that device but this does sound similar

-----

not sure why you re-encoded to profile 8 with a non-standard resolution but i would recommend a re-copy from disc
re-test without re-encoding, profile 7 and a standard resolution

it may shine some light on what's going on here

[fritsch]

Both files have some differences and so I hope these help for diagnose and btw. thanks for still trying to help.
Finch Media Info
Transformers Media Info

Both link to Finch only.

[quietvoid]

Your file probably has HDR10+ with Dolby Vision.
Disable HDR10+ in the expert settings.

[tRiBUN]

this issue has similarities to reports of issues on the fire stick 4k max with the cousin MediaTek MT8696T
that led to having the dolby vision compatibility added to kodi in the first place

possibly something to do with non-standard resolutions but i believe that was an entirely different issue

i wasn't following all the issues on that device but this does sound similar

-----

not sure why you re-encoded to profile 8 with a non-standard resolution but i would recommend a re-copy from disc
re-test without re-encoding, profile 7 and a standard resolution

it may shine some light on what's going on here

Thanks for that tipp. The thing is I didn't do the copy directly from my Disc, so I have not this details.

[tRiBUN]

Both files have some differences and so I hope these help for diagnose and btw. thanks for still trying to help.
Finch Media Info
Transformers Media Info

Both link to Finch only.

Corrected link / content

[tRiBUN]

Your file probably has HDR10+ with Dolby Vision.
Disable HDR10+ in the expert settings.

It sounds bit odd to me but hey it worked.
Of course HDR10 files now start as DolbyVision but that looks fine for me.
Thanks a lot quietvoid