• 1
  • 20
  • 21
  • 22(current)
  • 23
  • 24
  • 31
Kodi + Shield + Dolby Vision
(2021-01-05, 02:09)fandangos Wrote: We are using a implementation that we had to cherry pick by the plex team on ffmpeg.
FFmpeg does not support dv mkv yet.

That will be a major thing. Is there any coonection from the Kodi team to FFmpeg team? How can we push the mkv dv support in FFmepg?
(2021-01-05, 16:48)Commander71 Wrote:
(2021-01-05, 02:09)fandangos Wrote: We are using a implementation that we had to cherry pick by the plex team on ffmpeg.
FFmpeg does not support dv mkv yet.

That will be a major thing. Is there any coonection from the Kodi team to FFmpeg team? How can we push the mkv dv support in FFmepg?

We don't. 
This has been addressed in this thread. The way the code exists now it's not something ffmpeg team wants to use, or something along those lines.
(2021-01-05, 01:17)hoppel118 Wrote: Do you or anybody else here know where to look at for FEL/MEL information? 

BDInfo tools for Blu-ray Disc or remuxes
(2021-01-05, 01:17)hoppel118 Wrote: Do you or anybody else here know where to look at for FEL/MEL information? 

Regards Hoppel

MakeMKV will show it, both if you open a disc, or a DV .mkv.
(2021-01-05, 23:21)Epedemic Wrote: MakeMKV will show it, both if you open a disc, or a DV .mkv.

Ok, thanks! This was easy... Wink
frontend: nvidia shield tv 2019 pro | apple tv 4k | sonos arc 5.1.2 | lg oled65c97la
backend: supermicro x11ssh-ctf | xeon | 64gb ecc | wd red | zfs raid-z2 | dd max s8

software: debian | proxmox | openmediavault | docker | kodi | emby | tvheadend | fhem | unifi
(2021-01-05, 00:02)fandangos Wrote: A good starting point would be: with kodi with all default settings, play a file:
it works? good.
Change a setting. It works? It does not work.

So the problem is how the settings interact with the video file and not the video file or kodi itself. 

Starting and stopping a player 25 times in a row is not a a real world use case. 
A car can drive fine but if you turn it on, drive 2 meters, turn it off, turn it on, drive 2 meters repeat.. this is not how you drive a car and it may fail LoL

Not sure if that makes sense but I don't think it's something worth pursuing to fix.

What I think it's worth investigating is P7MEL, that's a profile used for remux correct?
Can you name one movie that has this profile so I can hunt it and test here?

Also does P7MEL crashes/hangs if you just start the shield and play?

Here you find the next test results: https://github.com/xbmc/xbmc/pull/18965#...-755796326
frontend: nvidia shield tv 2019 pro | apple tv 4k | sonos arc 5.1.2 | lg oled65c97la
backend: supermicro x11ssh-ctf | xeon | 64gb ecc | wd red | zfs raid-z2 | dd max s8

software: debian | proxmox | openmediavault | docker | kodi | emby | tvheadend | fhem | unifi
you all test so much, which is very nice, but i am wondering why nobody wants to take a look at the logcat output from the shield. there is normaly much more information about whats going on and whats going wrong. i remember, every time when something wasnt working correctly on the shield, @peak3d  always wanted the logcat output with the same timestamps from the debug log, to see whats really happened.
i hope he will come back soon, and help for making improvements for kodi/android
I would put my money on:

E OMXNodeInstance: getConfig(0x4ada7a20:Nvidia.DOVI.decode, ConfigAndroidVendorExtension(0x6f100004)) ERROR: UnsupportedIndex(0x8000101a)
You'd think, but even in a working ExoPlayer log there are a *ton* of errors like that. Smile
The same on my Firestick, but it works in ExoPlayer:
OMXNodeInstance: setParameter(1190049:MTK.DECODER.DVHE.STN, ??(0x6f60000d)) ERROR: UnsupportedIndex(0x8000101a)
OMXNodeInstance: setConfig(1190049:MTK.DECODER.DVHE.STN, ConfigPriority(0x6f800002)) ERROR: UnsupportedIndex(0x8000101a)
(2021-01-07, 21:06)quietvoid Wrote: You'd think, but even in a working ExoPlayer log there are a *ton* of errors like that. Smile
The same on my Firestick, but it works in ExoPlayer:
OMXNodeInstance: setParameter(1190049:MTK.DECODER.DVHE.STN, ??(0x6f60000d)) ERROR: UnsupportedIndex(0x8000101a)
OMXNodeInstance: setConfig(1190049:MTK.DECODER.DVHE.STN, ConfigPriority(0x6f800002)) ERROR: UnsupportedIndex(0x8000101a)

But in Kodi it results in this:

https://github.com/xbmc/xbmc/blob/master....cpp#L1106

m_indexInputBuffer = -1;

If really got the time and interested I can send you a 20mb logcat which has a single failure. So it's easy to read.

This is beyond my skills to fix it to be honest.
I have no idea what it's all about either, lol.
You could keep it in case someone knows more.
Does someone want to give this one a try?

https://mega.nz/file/PI9gzQIK#ILMyRD68u4...id2jIqdw4g

Smile
(2021-01-08, 21:21)fandangos Wrote: Does someone want to give this one a try?

https://mega.nz/file/PI9gzQIK#ILMyRD68u4...id2jIqdw4g

Smile

I will check it later tonight. Do you prefer special settings? Default settings + display buffer 2, anything else?

Regards Hoppel
frontend: nvidia shield tv 2019 pro | apple tv 4k | sonos arc 5.1.2 | lg oled65c97la
backend: supermicro x11ssh-ctf | xeon | 64gb ecc | wd red | zfs raid-z2 | dd max s8

software: debian | proxmox | openmediavault | docker | kodi | emby | tvheadend | fhem | unifi
(2021-01-08, 22:36)hoppel118 Wrote:
(2021-01-08, 21:21)fandangos Wrote: Does someone want to give this one a try?

https://mega.nz/file/PI9gzQIK#ILMyRD68u4...id2jIqdw4g

Smile

I will check it later tonight. Do you prefer special settings? Default settings + display buffer 2, anything else?

Regards Hoppel

Display buffer set to 3.

Try first a few times without display refresh rate.

And then try with display refresh and zero delay.
Ok, thanks, will try that later. Wink
frontend: nvidia shield tv 2019 pro | apple tv 4k | sonos arc 5.1.2 | lg oled65c97la
backend: supermicro x11ssh-ctf | xeon | 64gb ecc | wd red | zfs raid-z2 | dd max s8

software: debian | proxmox | openmediavault | docker | kodi | emby | tvheadend | fhem | unifi
  • 1
  • 20
  • 21
  • 22(current)
  • 23
  • 24
  • 31

Logout Mark Read Team Forum Stats Members Help
Kodi + Shield + Dolby Vision0