CoreELEC 8.95.4.42

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.

I made a add-on this worked to back 4Kh50/60 8.95.4.2 / 8.95.4.3 / 8.95.4.4.

@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.

Black Screen is not fixed for me.
1080p is OK, 2180p not.

Use a H96pro+, Sony 65XF9500 and a Denon x1400.

root@192.168.1.138's password:
##############################################
#                  CoreELEC                  #
#            https://coreelec.org            #
##############################################

CoreELEC (official): 8.95.4.42 (S912.arm)
CoreELEC-WZ:~ # cat /sys/devices/virtual/amhdmitx/amhdmitx0/edid
Rx Brand Name: DON
Rx Product Name: DENON-AVR
Manufacture Week: 0
Manufacture Year: 2017
Physical size(cm): 144 x 81
EDID Version: 1.3
EDID block number: 0x1
blk0 chksum: 0x35
Source Physical Address[a.b.c.d]: 3.5.0.0
YCC support 0x03, VIC (native 255):
ColorDeepSupport 0xb8 10/12/16/Y444 1/1/0/1
97 96 93 94 95 98 31 16 20 5 19 4 32 34 60 62 18 22 3 7 17 21 2 6 1 101 102 14 3                  5 15 36 95 94 93 98 353 352 357 358
Audio {format, channel, freq, cce}
{1, 7, 0x7f, 0x07}
{7, 5, 0x1e, 0x00}
{2, 5, 0x07, 0x00}
{11, 7, 0x7e, 0x03}
{10, 7, 0x06, 0x03}
{12, 7, 0x7e, 0x03}
{11, 7, 0x7e, 0x01}
Speaker Allocation: 0x5f
Vendor: 0xc03
MaxTMDSClock1 300 MHz
Vendor2: 0xd85dc4
MaxTMDSClock2 600 MHz
ColorMetry: 0xdf
SCDC: 1
RR_Cap: 0
LTE_340M_Scramble: 0
  DolbyVision2  HDR  DeepColor
checkvalue: 0x35250000
CoreELEC-WZ:~ # cat /sys/devices/virtual/amhdmitx/amhdmitx0/disp_cap
480p60hz
576p50hz
720p60hz
1080i60hz
1080p60hz
720p50hz
1080i50hz
1080p30hz
1080p50hz
1080p24hz
2160p30hz
2160p25hz
2160p24hz
smpte24hz
smpte50hz
smpte60hz
smpte50hz420
smpte60hz420
2160p50hz
2160p60hz
2160p50hz420
2160p60hz420

@noxx can I get one more piece of information from you. the output of

cat /sys/devices/virtual/amhdmitx/amhdmitx0/rawedid

thanks,

here

CoreELEC (official): 8.95.4.42 (S912.arm)
CoreELEC-WZ:~ # cat /sys/devices/virtual/amhdmitx/amhdmitx0/rawedid
00ffffffffffff0011ee530001010101001b0103809051780a0dc9a05747982712484c2108008180a9c0714fb300010101010101010108e80030f2705a80b0588a009f295300001e023a801871382d40582c45009f295300001e000000fc0044454e4f4e2d4156520a202020000000fd00173e0e883c000a2020202020200135020379f05f61605d5e5f621f101405130420223c3e12160307111502060165660e230f24350f7f073d1ec01507505f7e03570603677e035f7e01835f00006e030c003500b83c2f00800102030467d85dc401788001e50f03000006e3060d01eb0146d000450b908660768fe305df01e200cbe61146d000f00100000000000025

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

Hello,

i became a test version of coreelec. This Version works very fine.
The Version 9.95.5 will be stable within i hink.

I have checked my Denon AVR X2300W and i believe any video conversion is off.

I think you have to set “Video Mode” to “Bypass”!

Paul

@cdu13a

Result! Issue resolved in CoreELEC-S905.arm-9.0-devel-1541942153.tar (funhouse).

Can confirm 2160p@60hz and no black screen issues running through Denon AVR

Nice work

You need to set your AVR to “Bypass” as paul69 said, otherwise you may not get HDR and won’t get 10bit output.

I tried on bypass and it made no difference to the 2160p@60hz, switched back to auto but will set it to bypass to make sure HDR works correctly.

That development release works on Auto for 2160p@60hz through my Denon AVR.

Thanks

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.

@TheCoolest

Its looking good so far. See https://discourse.coreelec.org/t/no-60hz-at-3840x2160p/2300

Hi.

Works fine with mecool k1 pro -> Yamaha RX-A3070 -> LG65UH6159, HDMI pass through on Amp, Deep Colour checked on TV.

Problem with 2160p/50Hz solved, thanks.

##############################################

CoreELEC

https://coreelec.org

##############################################

CoreELEC (official): 8.95.4.42 (S905.arm)
CoreELEC:~ # cat /sys/devices/virtual/amhdmitx/amhdmitx0/disp_cap
480p60hz
576p50hz
720p60hz
1080i60hz
1080p60hz
720p50hz
1080i50hz
1080p30hz
1080p50hz
1080p25hz
1080p24hz
2160p30hz
2160p25hz
2160p24hz
smpte24hz
2160p50hz
2160p60hz
2160p50hz420
2160p60hz420
CoreELEC:~ # cat /sys/devices/virtual/amhdmitx/amhdmitx0/edid
Rx Brand Name: GSM
Rx Product Name: LG
Manufacture Week: 1
Manufacture Year: 2016
Physical size(cm): 160 x 90
EDID Version: 1.3
EDID block number: 0x1
blk0 chksum: 0xae
Source Physical Address[a.b.c.d]: 3.3.0.0
YCC support 0x03, VIC (native 255):
ColorDeepSupport 0xb8 10/12/16/Y444 1/1/0/1
97 96 16 31 4 19 5 20 3 2 18 32 33 34 21 1 93 94 95 98 95 94 93 98 353 352
Audio {format, channel, freq, cce}
{1, 1, 0x7f, 0x07}
{1, 7, 0x7f, 0x07}
{2, 5, 0x07, 0x00}
{7, 6, 0x1f, 0x00}
{9, 5, 0x02, 0x00}
{10, 7, 0x06, 0x01}
{12, 7, 0x7e, 0x01}
{11, 7, 0x7e, 0x03}
Speaker Allocation: 0x5f
Vendor: 0xc03
MaxTMDSClock1 300 MHz
Vendor2: 0xd85dc4
MaxTMDSClock2 600 MHz
ColorMetry: 0xc0
SCDC: 1
RR_Cap: 0
LTE_340M_Scramble: 0
HDR DeepColor
checkvalue: 0xae870000
CoreELEC:~ #

Where can I find the version with Kodi v18 Leia (Beta 5)?