Display MoreThat's possibly the same "bug" that I saw in CoreElec NO when I was talking to Portisch. He pointed me to a line of code that checks if a certain bit in the Dolby Vision VSVDB (Vendor Specific Video Data Block) in the EDID of the display is not ON then this says that the display cannot do DV at 120Hz. I have an older TV that cannot do DV at 120Hz and one that can and the bit was different on both, that's how I found out about the bit.
The problem is, it seems that CoreELec NO is checking the GUI Hz wrongly and thinks the video that you are starting the playback is a 120Hz video even if it's the GUI that is 120Hz and not the video. Probably something about when the video starts the playback because I was seeing 2 or 3 times switching res and/or Hz in the kodi log.
I still have the picture of the bit it's this one:
https://drive.google.com/file/d/1UOvdWz…iew?usp=sharing
It says "reserved" but it's in fact called "Parity" and it'S a 120Hz compatibility bit for DV for the display. That picture is just from an older DV Header when it didn't yet serve any purpose.
I said to Portisch maybe this should be fixed but he just said use 60Hz in GUI so I did that on my AM9 Pro. I also think it may be from LibreElec 13 since CoreElec NO is a fork of LibreElec 13 if I am not mistaking. So that's why we see it here too maybe?
On my AM6B+ with CoreElec NG I do NOT have that problem and am using 1080p 120Hz and DV works fine so they changed or added the check for this bit in CoreElec NO / LibreELec 13.
Portisch replied with the line of code for the check here:
https://discourse.coreelec.org/t/amlogic-no-discussion/46663/3668
The line of code is here:
https://github.com/CoreELEC/commo…id_parse.c#L888
I don't see "common_drivers" in LibreELec's git repos though... I will try to put 1080p 120Hz and see if I have the same problem.
...
tested and I do NOT have a problem playing back DV while my GUI is at 1080p 120Hz. This may be a CoreElec NO only problem and maybe this has nothing to do with bang gun 's problem? It sure looks like the same problem from what he his experiencing though but I don't experience that like I did on CoreElec NO. Also, if I do a search for "dv->parity" in LibreElec's repo I find nothing.
Which file were you trying to play bang gun ?
Not sure if I followed everything you mentioned there. Anyway as far as I can tell it used to happen on any file with Dolby Vision though I usually refer to the (in)famous DV FEL All Layers Test (Womxn at 80s) file. The issue is somewhat more annoying then I initially surmised because detection happens every time Kodi starts. Which means if you use add-ons like vacuumtube which exit and restart Kodi on exit I need to ensure it stays fixed on 60Hz to ensure Dolby Vision files will play back. I'm not nearly technical enough to understand any of this but it feels like Kodi simply won't play back the file cause on initial startup of the app it has decided the TV is incapable of playing back dolby vision (as a false negative in this case). Would there be a not so elegant solution as to ignore this detection and still force DV playback maybe as a setting toggle in the options. Of course it would be nicer if DV detection could be improved I could try to send logs if that helps but all I can see is only a simple DV=0 or DV=1 mention in the log files not sure if that's too helpful
