With 8.95.4.42 i no longer have the option to set Kodi to 3840x2160@60Hz, i was using a recent nightly build (from Nov 5 i think) and didn’t have this problem. Anything special you need me to set so i can post logs?
EDIT: Just tested nightly_20181108 from @relkai and i can set 3840x2160@60Hz just fine
The nightlies doesn’t include the auto switching patches from OSMC and are still using the old method.
The version of cdu13a is much more advanced regarding colorspace/bit rate/refresh rate/resolution switching, but heavily relies on correct EDID information provided by TVs/AVRs.
Therefore we know, this refresh rate is working fine in the nightlies, but e.g. doesn’t automatically switch to HDR like cdu13a’s version.
Sorry, but I find this confusing. Which is the version of cdu13a?
IMHO the nightly version should be the bleeding edge version for you and users to test stuff. Nightly implies that breakage is to be expected and anyone testing it should be aware of that, as opposed to the release versions.
i don’t see the latest release versions as “screwups”, either. There are no grave coding errors as such, but they rather reveal that TV hardware is not as standardized as commonly thought. So release versions should be treated as permanent beta versions.
If anybody needs to have a wifey factor, i.e. total availabilty, you may need to be reminded that the underlying KODI itself of current versions is not a stable version. You should stick to tried and trusted KODI Krypton for AMLOGIC which works just fine.
The version of cdu13a is the one from this thread (8.95.4.42).
It is behind the nightlies in other aspects, because it doesn’t include the newest commits.
Therefore the nightlies are still “bleeding edge” except for the auto switching patches.
Because cdu13a heavily develops the auto switching feature at the moment, it makes sense to have all tests being done against the same GitHub commit and only his newest changes added.
It is a different development branch to test just this one specific feature.
If it was included in the nightlies, there could have been different results because of other commits.
As soon as all bugs are sorted out, it will be merged to the stable/nightly builds, of course.
@HeresJohnny The 8.95.4.42 release is a continuation of trying to fix a feature that never quite worked right in the 8.95.4.x releases.
The nightly builds as you say are bleeding edge, but they are the bleeding edge of what will be the next release. That auto switching feature has since been removed from the master branch of the CoreELEC code until it can be made to work better. Since it currently is not expected to be part of the next release, it no longer appears in the nightly builds.
Im a little bit confused. In a further Version i dont have the 30hz Problem in Kodi. Before 8.95.4 i have >4K60Hz in Kodi.
On TV and AVR i dont have change some Settings. So i think it is a Problem (?) with new Coreelec or Kodi >Feature.
Whats your Opinion?
Same issue here. My TV is 2017. Before 8.95.4 it worked fine. Problem sticking at 8.95.3 is that you cannot install some addons using the older version because of dependency issues.
I just looking at the settings on my Denon AVR to see if there is anything i can change
It would be interesting to know whether it’ll also switch into 10 bit mode correctly.
What you should see is a 10bit YUV422 signal when viewing 4K HDR/10 bit content.