Posts by HomerJau

I’m sure I read a recent Linux version (6.10 or maybe 6.9) add Meteor Lake support. So don’t use LE12 (only Linux 6.6).

Reset your AVR. My old Denon AVR-X7200W would not recognise DTS or Atmos, multichannel pcm etc over HDMI (stuck on ‘stereo’) about once every 18 months or so. A hard Reset would fix it.

The above was using various LibreElec builds on Intel NUCs. The AVR reset ‘fix’ was needed over about 6 years. I’ve not had any such issue using my new Denon 4800H but it’s happened on another Denon (AVR X3400H) I use in another room once in 6 years (Intel NUC/LibreElec).

In that 6 year period it been NUC5, NUC8 (I’m now using NUC11TNK and NUC12SWH LE12 and still have 2 x NUC8 for test builds)

Try setting output to HDMI not Display Port

Quote from chewitt

I've submitted this to merge support for LE13: https://github.com/LibreELEC/LibreELEC.tv/pull/9101

It can probably be backported to LE12 too .. but I'm being lazy this morning.

Could you please submit a merge request for LE12 branch?

Thanks!

NUC5 cannot decode HEVC via hardware and cannot do HDR:

https://wiki.libreelec.tv/hardware/intel-x86-64-generic

My LE12 crash issues solved. Solution: Do not use Grab Fanart addon in LE12

I tried to get crash logs on two NUCs but none existed. The other logs show nothing abnormal prior to crashes.

However, I did notice entries from the GrabFanart addon script just before the crash. I did a search to see if anyone reported issues with that addon and there is a memory leak in recent Python releases due to unsupported code:

Module "imp" deprecated since Python 3.12 · Issue #12 · robweber/script.grab.fanart

Since Python 3.12 the module "imp" is deprecated. Now I'm getting this error: 2024-06-05 09:03:19.624 T:1543846 error : EXCEPTION Thrown (PythonToCppException)…

github.com

BTW: LE12 crashing with memory full was reported on the Kodi forum, no solution was reported.

I then deleted Grab Fanart from two NUCs and ran the two movies that crashed last night on each NUC. They both played their complete movie to end with no crashes.

This also explains why CoreElec Kodi 21 runs (I didn’t install Grab Fanart addon) and LE11 uses an older Python version so Grab Fanart runs without its memory leak above.

But same network works with LE11 and CoreElec with Kodi 21 without issues. All 3 of my NUCs using LE12 crash.

I’m running a Kodi debug session now using my NUC8 LE12.

Update: Two different NUCs with latest LE12 both crash playing different movies after around 30 minutes or so.

I’ll create logs tomorrow and upload them.

chewitt Thanks for your reply. I now have solved my Intel NUC issues today with latest nightly and changing my NFS chunk size and Cache settings. I discovered the cache settings don’t seem to be applied until LibreElec is restarted.

With NFS and Cache chunk = 128kb, NFS set to v4 and cache size = 192MB I no longer get crashes when playing media or scanning my media into the music library. My NUC11pro with NVME SSD shows CPU at > 200% during the scan with debug enabled which I’ve never seen previously (my network is 2.5GBE, NUC - switch - NAS)

Why does latest LE12 nightly (Generic) not include updates to Linux and Mesa?

I have 3 different model Intel NUCs (8, 11 pro and 12 pro) that all crash to LibreElec boot screen when playing for a few minutes, video or music, on all recent LE12 builds). If I install LE11 no problems. CoreElec on AMlogic no problems. So I presume it’s Linux, NFS or Mesa. Log shows nothing.

Quote from Krobar

These test files are courtesy of HomerJau (Assuming it is the same user on QuadrophonicQuad):
https://drive.google.com/file/d/1dWB93r…iew?usp=sharing

Yea. That’s me.

Opening all the channels in that screen grab does not mean all the output channels are sending data. For the Android Kodi quad fix all the only 4 channels have data so the output is pure Quad, even though all the output channels are active (all but ‘quad’ are silent). Anyway the true test is to listen to each speaker not look at the AVR graphic.

I reported a bug that Kodi wouldn’t play quad (4.0) pcm files on Android. The fix was to send 5.1 (4.0 with two silent channels: L, R, s, s, Ls, Rs). That was implemented in Kodi 21 Android builds back in February and tested on Firestick 4K Max.

AudioTrack: Simplify Channel selection by fritsch · Pull Request #24554 · xbmc/xbmc

All major Android devices have issues opening more "fine grain" audio channel configurations besides Stereo, 5.1 or .7.1 - use AE's feature to silently add…

github.com

Small cache (64MB) and ‘Adaptive’, small chunk size (32kb) and NFS version 4 seems to solve my network problems with two Synology NAS (and I need to have both on, although that may have been fixed during betas).

After attempting a EDID fix I accidently discovered a fix:

Remove '3840x2160 24Hz' and '23.976' from whitelist and set both Kodi's 'Allow 3:2 pulldown' and 'Allow Double Refresh Rates' to ON (Enabled).

Now everything playing.

(The accidental discover after I reinstalled LE12 from scratch I found 23.976 played and 24Hz did not, I had forgotten to Whitelist 23.976).

I’m running ‘standard’ LE12 nightlies, I first noticed this a couple weeks ago when swapping NUCs around. I’m currently running nightly from 31 March.

It may not be a LE issue as when the NUC is switched on the Intel NUC boot splash appears to be in HDR mode. But this issue only occurs when it’s directly connected to the TV, never when it’s connected via my AVR.

When I connect my Intel NUC direct to my 4K Sony TV the display is always in HDR mode (HDR always on). It never switches off.

When same NUC is connected via my AVR to TV all runs as expected, HDR is only activated when I play HDR media and off when playback stopped.

How can I solve the direct connection ‘HDR always on’ issue? (I want to use ARC to my AVR)

LE 12 Beta1 build in all tests below, with 4k resolutions 'white' listed, latest firmware (same issues with all recent nighlies)

I have a NUC11TNKi3 which works perfectly with latest Denon AVR4800H with LG CX 4k TV.

Same NUC11TNKi3 with my Denon AVR3400H and Sony A8F 4K TV plays everything except 4K (always shows blank screen for any 4K file) and is completely unresponsive. Both AVR and TV are HDMI 2.0b

My old NUC8BEHi3 with my Denon AVR3400H and Sony A8F 4K TV plays everything including 4K perfectly.

Looking at the NUC11TNKi3 logs there is an EDID error:

2024-03-21 13:05:45.992 T:1079 debug <general>: CDRMUtils::OpenDrm - opened render node: /dev/dri/renderD128
2024-03-21 13:05:46.021 T:1079 info <general>: CDRMUtils::FindConnector - using connector: HDMI-A-1
2024-03-21 13:05:46.021 T:1079 info <general>: CDRMUtils::FindEncoder - using encoder: 307
2024-03-21 13:05:46.021 T:1079 debug <general>: CDRMUtils::FindCrtc - original crtc mode: 1920x1080 @ 60 Hz
2024-03-21 13:05:46.021 T:1079 info <general>: CDRMUtils::FindPlanes - using crtc: 98
2024-03-21 13:05:46.021 T:1079 debug <general>: CDRMUtils::FindPlanes - using video plane 31
2024-03-21 13:05:46.021 T:1079 debug <general>: CDRMUtils::FindPlanes - using 10bit gui plane 40
2024-03-21 13:05:46.021 T:1079 debug <general>: CDRMAtomic::InitDrm - initialized atomic DRM
2024-03-21 13:05:46.021 T:1079 error <general>: [display-info] Error parsing EDID:
2024-03-21 13:05:46.021 T:1079 error <general>: [display-info] ----------------------------------------------
2024-03-21 13:05:46.021 T:1079 error <general>: [display-info] Block 1, CTA-861 Extension Block:
2024-03-21 13:05:46.021 T:1079 error <general>: [display-info] Speaker Allocation Data Block: Deprecated bit F16 must be 0.
2024-03-21 13:05:46.021 T:1079 error <general>: [display-info] Colorimetry Data Block: Reserved bits MD0-MD3 must be 0.
2024-03-21 13:05:46.021 T:1079 error <general>: [display-info]
2024-03-21 13:05:46.021 T:1079 error <general>: [display-info] ----------------------------------------------
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] make: 'DENON, Ltd.' model: 'DENON-AVR'
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] supports hdr static metadata type1: true
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] supported eotf:
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] traditional sdr: true
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] traditional hdr: false
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] pq: true
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] hlg: true
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] luma min: '0' avg: '0' max: '0'
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] supported colorimetry:
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] xvycc_601: true
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] xvycc_709: true
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] sycc_601: true
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] opycc_601: true
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] oprgb: true
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] bt2020_cycc: false
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] bt2020_ycc: true
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] bt2020_rgb: true
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] st2113_rgb: false
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] ictcp: false
2024-03-21 13:05:46.148 T:1079 debug <general>: CWinSystemGbm::InitWindowSystem - initialized DRM
2024-03-21 13:05:46.149 T:1079 info <general>: Found resolution 1920x1080 with 3840x2160 @ 60.000000 Hz
2024-03-21 13:05:46.149 T:1079 info <general>: Found resolution 1920x1080 with 4096x2160 @ 60.000000 Hz
2024-03-21 13:05:46.149 T:1079 info <general>: Found resolution 1920x1080 with 4096x2160 @ 59.940063 Hz
2024-03-21 13:05:46.149 T:1079 info <general>: Found resolution 1920x1080 with 4096x2160 @ 50.000000 Hz
2024-03-21 13:05:46.149 T:1079 info <general>: Found resolution 1920x1080 with 4096x2160 @ 24.000000 Hz
2024-03-21 13:05:46.149 T:1079 info <general>: Found resolution 1920x1080 with 4096x2160 @ 23.976025 Hz
2024-03-21 13:05:46.149 T:1079 info <general>: Found resolution 1920x1080 with 3840x2160 @ 59.940063 Hz
2024-03-21 13:05:46.149 T:1079 info <general>: Found resolution 1920x1080 with 3840x2160 @ 50.000000 Hz
2024-03-21 13:05:46.149 T:1079 info <general>: Found resolution 1920x1080 with 3840x2160 @ 30.000000 Hz

Can anyone help me to resolve this issue please?

Da Flex The wiki should be updated. It still has ‘config.txt’ with no reference to ‘cmdline.txt’