The only thing that can dynamically change is an add-on. Look at the add-on update history.
Posts by chewitt
-
-
chewitt I guess this patch should better be dropped and intel devs need to fix the issue properly
I don't think this would cause problems. The patch caps the DRM connector at 10-bit output to prevent it ending up in 12-bit which results in bandwidth issues when HBR audio is present. For DV output we are tunnelling in 8-bit RGB and avoid the problem. I don't see DV issues with a Generic build based on current development running on an N150 box.
That patch is a hack though, so a candidate for improvement as userspace vs. kernel colour support evolves.
-
The only committed changes in our 12.2 branch since 12.2.1 (last November) have been add-ons and (ironically) timezone and root cert updates, but without any significant changes to warrant pushing another formal release out, there hasn't been one, and for the same reason we stopped LE12.2 nightlies a while ago too, so development has focussed on LE13.
We should/could maybe look at publishing root certs and timezone changes as add-ons to prolong the lifespan of the base images for longer without the need for a full image update. That's probably a rainy day project though..
-
Add-ons might/would be my blind guess.
-
isn’t it the case with the Raspberry Pi 4 that the jack socket has to be enabled in the “config.txt” file first!?
Correct
-
or it was introduced by patches and addons from Zabrimus
This, as there haven't been any issues with input.
-
Looking forward to an upstream merge
It will happen. The current driver I'm using is an ugly port of even uglier vendor driver code and replacing it with something clean that can go upstream has always been the objective.
-
starting to re-use it, navigate around doesn't get it out of that dim mode to normal...
FWIW, I don't see this with any of the nightly images that I run on x86-64/Amlogic/RPi/Rockchip hardware; albeit using the black screensaver instead of dim, but I don't think that would matter since both function in essentially the same way.
-
PR11904 is likely related.
It hasn't been merged (still fighting 10-bit output on RK3328) so that's not the cause.
-
Note: If you are running these rather experimental images we have no great interest in the ticket. Switch to a Generic nightly to reproduce the problem first.
-
It's not possible to update the zone files without self-compiling an image. It's easier to update to a current LE13 nightly:
https://test.libreelec.tv/13.0/RPi/RPi4/
I've been running (own built) nightlies for the last 18-months and there's nothing unstable about them. The only reason we didn't already ship a K22 beta is me fighting unrelated Rockchip kernel patches.
-
Depends on what kind of bug report you are submitting. If you have triaged the issue and have a strong idea on the problem open a ticket on GitHub with all the information. Otherwise (and esp. if the issue was diagnosed with AI tools, start a thread in here first to avoid the noise.
-
That will happen, but it might not be for a bit as I am submerged in other things.
-
It still looks like it's playing something with a messed up mp4 container or H264 internal structure. If you copy the same file to local storage or play from an SMB share, does it play?
-
I don't speak English. If I create a ticket, I don't know how I'll be understood there, especially since people here don't understand me and misquote me.
Our advice for this forum is always to post in your native language, then copy/paste the Google translation underneath. The same works with support tickets. The flirc team is fairly small, but all nice people, don't be shy.
-
Code
channel-map = front-left,front-center,front-right,rear-left,rear-right,lfeHave you tried something like that ^ in the config? (rearrange the text until things come out right)
Try default-channel-map as an alternative
-
I know little about pulse audio, but channel placement comes from ELD data which alsa derives from the EDID data on the HDMI connection. It might be worth ensuring (with Kodi stopped else it hogs the audio device) that alsa speaker-test can output 6ch audio correctly.
-
No idea as I don't run nightlies. I'm still working through PR11904 on RK3328 to solve some issues, then I might look.
