Posts by chewitt

  • Intel Alder Lake 2160p @ 23.976 Hz passthrough HD Audio dropouts (i7-1270p/N100)

    The current workaround is a script (re)configuring the DRM layer from userspace. If someone can come up with a kernel patch to avoid hacking things from userspace: a) we'll know what area of kernel driver code to focus Intel devs on, b) i'll accept/merge a temporary patch to see what issues arise: the patch probably needs to cap bits-per-pixel and those calculations are used for lots of things so there is potential for unintended fallout and the 'simple' change might not be simple.

  • Nightly Builds

    LE 12.2 and 13.0 have dropped the legacy nvidia driver, and the number of ‘newer’ cards in active use is tiny (we have been telling people not to use nvidia cards for a decade; people have listened) so we may simply drop nvidia support completely and have a more simple life. It will suck to do that, but as nvidia continues to either ignore standards or implement them with some catch that eliminates LE use, so be it.

  • [x86-64] No 2160p on JVC Projector

    I'm wondering if the audio glitch is similar to the N100 issues here: https://github.com/LibreELEC/LibreELEC.tv/pull/8588 - the script in that PR is not going to be merged as it's too much of a hack, but you could copy/paste it locally and experiment. It basically finds the active DRM connector and limits the max bits-per-pixel to 10-bit as 12-bit seems to cause issues. The root cause is unknown but I have a hunch it's related to bandwidth and UHD video + HD audio maxes out something resulting in audio dropouts.

    You might want to add something like video=HDMI-A-1:1920x1080M@60 to kernel boot params in syslinux.cfg in case (for reasons unknown) the box is trying to use a problematic 4K mode. This will clamp initial kernel DRM output to 1080@60 to stop that. There's no impact on Kodi switching to 4K during playback later.

  • Can i do "Create System and Kodi Backup" with a SSH Command?

    There's no shortcut/script for it, but the backup process we use in the LE settings add-on is just a 'tar' command. If the box is only hosting Tvheadend you only need to stop Kodi and then tar the contents of /storage/.kodi/userdata/addon_data and any other dirs that you've used in your TVH configuration as the rest of the OS and Kodi should be using default settings.

    NB: If you are thinking to update to LE 12.2 (or LE13 nightlies) Tvheadend 4.2 is no longer supported and only Tvheadend 4.3 exists in the 12.2/13.0 addon repo you are updating to.

  • [RPi5] Slow playback of even 720p from YouTube

    In theory de-featuring the board to a single HDMI connector shouldn't be an issue, but if you fuzzed one thing it's possible other things were damaged too. Historically i'm able to play 4K30 VP9 content from YouTube, although I didn't test since the rather niche regression below was possibly added (and can't test from current location).

    There is one software regression we are triaging, noted when playing 4K H264 on an RPi5; much higher resolution than 720p VP9 but also software decoding so there's a chance your issue could be the same thing. Log in to the RPi5 over SSH, run rpi-eeprom-config -e and add SDRAM_BANKLOW=3 to the end of the file, then reboot. Any better after? NB: If no difference, it's not the same issue and you can revert the change.

  • Trying to understand auto-update...

    LE only auto-updates within the same release series, e.g. 12.0.0 > 12.0.1 > 12.0.2. It never auto-updates between major releases like 12.0.x > 12.2.0 or 12.x > 13.x as major releases often contain breaking hardware changes and/or Kodi major version changes.

    For example. forced update from 12.0.2 > 12.2.0 would be an issue for RPi5 users running Tvheadend 4.2 (doesn't exist in 12.2) or an x86_64 device with older nVidia card would rebot to no Kodi home screen (GPU drivers don't exist in 12.2).

    You can manual update in the settings add-on if you've read the release notes and nothing impacts you.

  • LFTP transfer speeds over WiFi

    The laptop has a proper WiFi antenna allowing 'max' transmission rates and so much single-core CPU capacity that single vs. multi-threading makes no practical difference. The CPU design is general purpose and the fully built system uses a large amount of power and generates a lot of heat even when handling trivial tasks.

    The RPi5 has a rubbish antenna so WiFi will always be at a disadvantage when compared to Ethernet, and the ARM CPU single-core performance is much lower so single vs. multi-threaded has a more noticeable impact. The SoC package is a lot more efficient and a fully built system uses considerably less power and generates less heat for a trivial workload.

    As usual, the moral of the story is .. use Ethernet :)

  • Goes to LibreELEC loading screen when large mkv files

    Code
    [  888.846372] VideoPlayer[1304]: segfault at 48 ip 00007f20f594ce85 sp 00007f20a77fe280 error 4 in r600_drv_video.so[7f20f55b2000+b48000] likely on CPU 1 (core 1, socket 0)
[  888.846392] Code: 45 00 01 f0 83 2e 01 0f 84 b0 01 00 00 0f 1f 84 00 00 00 00 00 48 8b 83 e8 00 00 00 48 89 ab f8 00 00 00 66 0f ef c0 49 89 e4 <48> 8b 68 48 0f b7 45 44 0f b7 55 40 0f 29 04 24 48 89 ee c6 43 3f

    No idea what any of that means .. Just flagging in case someone else does. I'd personally start with testing an LE13 nightly release to see if newer (everything) magically resolves the issue? - because even if we discover what the issue is, there will be no fix for LE12.0.

  • [x86-64] No 2160p on JVC Projector

    Code
    2025-08-13 19:08:23.604 T:976      info <general>: ffmpeg[0x208aae90]:   Stream #0:0: Video: hevc (Main 10), yuv420p10le(tv, bt2020nc/bt2020/smpte2084), 3840x2160 [SAR 1:1 DAR 16:9], 23.98 fps, 23.98 tbr, 1k tbn (default)

    ^ media is detected as 4K23.976 (10-bit, with a colourspace normally associated with HDR)

    Code
    2025-08-13 19:08:23.740 T:979     debug <general>: CRenderManager::Configure - change configuration. 3840x2160. display: 3840x2160. framerate: 23.98.
2025-08-13 19:08:23.745 T:892     debug <general>: DeleteRenderer - deleting renderer
2025-08-13 19:08:23.745 T:892     debug <general>: LinuxRendererGLES: Cleaning up GLES resources
2025-08-13 19:08:23.745 T:892     debug <general>: SetHDR: setting connector colorspace to Default
2025-08-13 19:08:23.745 T:892     debug <general>: LinuxRendererGLES::Configure: fps: 23.976
2025-08-13 19:08:23.745 T:892     debug <general>: SetHDR: setting connector colorspace to BT2020_YCC
2025-08-13 19:08:23.745 T:892     debug <general>: LinuxRendererGLES::Configure: HDR passthrough: on

    ^ then it flags a renderer with [email protected] and appropriate colourspace, but have you enabled "adjust reresh" ? - If yes it will output using the whitelist (not configured) or best guess at the right mode. If not, it will scale the output to the desktop res (1080@60). So make sure adjust-refresh is enabled and configure the whitelist as per the wiki article.

    Once done, if you run kmsprint on the SSH console before playback it will show DRM connector properties as 1080@60, and during playback it should show them to be [email protected]?

  • [x86-64] No 2160p on JVC Projector

    Quote from Ozyman

    Hope this helps!

    Not much. Please repeat after creating a plain SMB mount to the device where you store media, then play something appropriate and 4K from that source using the Kodi 'Videos' view so we can see a playback event containing all the normal and useful ffmpeg/drm/Kodi media debug info that's being masked or suppressed by the Plex plugin you are using. In the log you've captured I can sort of figure out where playback probably occurred, but there's no useful info.