https://github.com/xbmc/xbmc/pull/24786 is the first step to a solution, but it's in a complex area of code where changes are slow and deliberate not rushed. This is for Kodi 'P' too (assuming its merged that fast).
Posts by chewitt
-
-
So, to confirm, the issue is resolved for you with the LE12 nightly? - the Android issue needs to be posted in the Kodi forum.
-
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
Hard to comment .. and you've not shared the entire log.
-
-
Just put the .tar in /storage/.update and reboot. Or if you want to start over with a clean install, use https://chewitt.libreelec.tv/testing/LibreE…-12.80.0.img.gz in the same folder.
-
Nope. The hotspot is intentionally simple and doesn't support much more than ON/OFF. If you need router features, you need to get a router
-
The folks at https://tvheadend.org might be more clued up on that kind of thing?
EDIT: https://tvheadend.org/d/8679-tvheadend-ffmpeg-to-dvb-t2
-
I'd ask ilmich to bump the kernel to something newer than Linux 6.1.y as there are improvements/fixes to the rtl8xxxu driver that might benefit things for an RTL8723BU chip. That might not be a simple exercise though, and his time is limited. In the longer term support should be added to the rtw88 driver, but that effort is still in early stages.
Plan B .. (or C) .. use an external USB wifi device or something that's powered from USB but presents an Ethernet interface (so there are no drivers involved).
-
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
-
i have black screen in some channel and signal HLG not work in other channel
Hard to guess what the issue is (debug logs might help) but I'd make an educated guess and point fingers at Intel drivers.
-
-
nasawyer7 not sure what hardware you are using, but if RPi5, this image contains the patch mglae suggested:
https://chewitt.libreelec.tv/testing/LibreELEC-RPi5.aarch64-12.80.0.tar
If not RPi5, tell us and I'll create something to test.
-
Are there some requirements to the SD card im not aware oft?
Nope. Does the problem persist with other cards? Can you imge/boot RaspiOS from the problem card?
-
popcornmix has a draft fix for this issue, see: https://github.com/raspberrypi/linux/pull/6218
This update uses 16K pages and includes the patch: https://chewitt.libreelec.tv/testing/LibreE…h64-12.80.0.tar
Please test and report back.
-
HDR/HDR10/HLG is already supported in LE and Kodi subject to the hardware supporting them; which is complicated on NUC type devices with LSPCON chips as those can modify the capabilities of the "HDMI" output path and prevent a universal/simple answer to what's supported. There are also bugs in Intel drivers that muddy the waters.
DV is already supported in Kodi (on Android with appropriately licensed hardware). However on Linux you will also need licensed hardware (so handling exists in silicon) and FFMpeg support. The latter appears to be progressing, but it will be a while before all pieces are version aligned. Kodi 'P' is about to bump from FFMpeg 6.0 to 7.0 and those patches are merged to FFMpeg master so should be in FFMpeg 8.x (or something post v7.0 at least) and there's likely to be more patching needed.
And for purists: There will never be an open-source implementation of DV to Dolby standards because the tooling and technical info needed for that require sign-up to their license regime (which is the polar opposite of open-source). So open-source DV support will always be limited to making something that looks nice on screen.