Is your HD Live TV resolution whitelisted?
havnt touched the whitelist, never do.
Matt
Iâve heard of several livetv issues so you are not the only one. Iâm bot using Live TV so need to wait for @afl1 to look at it.
1 Like
Thank you. It was quite repeatable earlier. Now, it does not crash when gui set to 1080p.
With April 14th build this morning when watching 4k content display switches to 4k mode yet content is shrunk to a small rectangle approx 1/4th the screen (I assume 1080 box) on top left corner. Rest of the display is blank. Have Sony 690e display.
If I set display resolution to 4k the same thing happens. With the prior build it was fine. Also noticed same in Ray test build from April 13th.
One thing I noticed is with suspend on âTV offâ enabled when resuming UI is really slow to draw images from that point forward. Feels like loading data from SD slows way way down until reboot. Booting off a 64GB sandisk SD.
Here is kernel message log of same. After reboot all works just fine.
[ 1653.211646@5] sd: req failed (CMD18): -84, retrying...
[ 1653.212244@0] meson-mmc: sd: warning... data crc, vstat:0xe1f0040f, virqc:3ff f
[ 1653.212247@0] meson-mmc: @ cmd 18 arg 6c4218c with ffffffc0dd3869a8; stop 0, status 4
[ 1653.212249@0] meson-mmc: sd: err: wait for irq service, bus_fsm:0x8
[ 1653.212257@2] meson-mmc: meson_mmc_irq_thread_v3 551 sd: cmd:18
[ 1653.212271@0] meson-mmc: sd: warning... response crc,vstat:0xa1ff2400,virqc:3 fff
[ 1653.212283@5] sd: req failed (CMD18): -84, retrying...
[ 1653.212923@0] meson-mmc: sd: warning... data crc, vstat:0xe1f0040f, virqc:3ff f
[ 1653.212929@0] meson-mmc: @ cmd 18 arg 6c4218c with ffffffc0dd3869a8; stop 0, status 4
[ 1653.212932@0] meson-mmc: sd: err: wait for irq service, bus_fsm:0x8
[ 1653.212941@2] meson-mmc: meson_mmc_irq_thread_v3 551 sd: cmd:18
[ 1653.212955@0] meson-mmc: sd: warning... response crc,vstat:0xa1ff2400,virqc:3 fff
[ 1653.212966@5] sd: req failed (CMD18): -84, retrying...
[ 1653.213596@0] meson-mmc: sd: warning... data crc, vstat:0xe1f0040f, virqc:3ff f
[ 1653.213601@0] meson-mmc: @ cmd 18 arg 6c4218c with ffffffc0dd3869a8; stop 0, status 4
[ 1653.213603@0] meson-mmc: sd: err: wait for irq service, bus_fsm:0x8
[ 1653.213611@2] meson-mmc: meson_mmc_irq_thread_v3 551 sd: cmd:18
[ 1653.213615@2] meson-mmc: Command retried failed line:585, cmd:18
[ 1653.213626@0] meson-mmc: sd: warning... response crc,vstat:0xa1ff2400,virqc:3 fff
[ 1653.213646@0] meson-mmc: sd: warning... response crc,vstat:0xa1ff2400,virqc:3 fff
[ 1653.213648@0] meson-mmc: sd: err: wait for irq service, bus_fsm:0x8
[ 1653.213656@2] meson-mmc: meson_mmc_irq_thread_v3 551 sd: cmd:13
[ 1653.213658@2] meson-mmc: meson_mmc_irq_thread_v3() 567: set 1st retry!
[ 1653.213672@0] meson-mmc: sd: warning... response crc,vstat:0xa1ff2400,virqc:3 fff
[ 1653.213674@0] meson-mmc: sd: err: wait for irq service, bus_fsm:0x8
[ 1653.213681@2] meson-mmc: meson_mmc_irq_thread_v3 551 sd: cmd:13
[ 1653.213695@0] meson-mmc: sd: warning... response crc,vstat:0xa1ff2400,virqc:3 fffYou have overscan setup in your guisettings.xml. I had the same. Stop Kodi and edit your guisettings.xml. i used my settings from Helix time.
1 Like
It works, thanks!
Just had the same.
In GUI settings all 4k resolutions had overscan set to 1920x1080.
Changed to 3840 and 4096 for the respective resolutions and working again now.
Is h265 12-bit video supported.
CoreELEC-Alex:/sys/devices/virtual/amhdmitx/amhdmitx0 # cat dc_cap 420,12bit 420,10bit 420,8bit 444,12bit 444,10bit 444,8bit 422,12bit 422,10bit 422,8bit rgb,12bit rgb,10bit rgb,8bit
It looks like it should be but when selecting a video file I just get audio. If I select the file again whilst itâs playing, it takes me into the video playback but just a black screen.
1 Like
I never saw a 12bit hevc video. AML decoder supports 10bit. Donât think 12bit is support. Donât mistake it with color depth. This is supported on some TVs.
Ah my bad.
I know it never worked on the c2 but was hopeful when I saw 12 bit mentioned in the dc_cap.
I only have a couple, I think itâs only anime that have started using yuv420p12 for h265 releases.
1 Like
dc_cap is related to hdmitx and edid info from your display not the video decoder.
It pretty much just lists the colour depth and chroma sampling that your display claims to support.
edit: Itâs not even a good indicator of what the display can support, itâs mostly just what the display says it will try to deal with.
Just streamed my 1:1 copy of aquaman. Picture and audio flawless 
Just a small update to this - The Media-build drivers in this build now pick up my 292e DVB dongle properly. However changing to the media-build drivers also stops the official HK remote from working.
If I change back to the CoreELEC default drivers the official remote works again (sluggishly - not nearly as zippy as my USB airmouse/remote or previous s905 boxesâ stock remotes) but of course then my DVB dongle is not picked up.
Thanks. Iâm working on it.
2 Likes
@Daaave this is your third or fourth time reporting this issue, as I said before it will be looked into.
We are not blind to issues when people report them.
There was an important update. Ray had previously said it might be to do with Crazycat and I was informing him that the Media Build drivers do the same thing. I didnât want him to waste time looking at Crazycat specifically.
I am well aware how busy you all are, just didnât want anyone wasting time looking in the wrong direction on this.
1 Like
All good here. People want a working device. I can understand that
1 Like
We already know what the issue is, itâs just getting the time to get round to addressing it.
Fixing issues and testing changes is very time consuming.
Ok sry. Just trying to be helpful.
3 Likes