Passthrough of a digital signal requires a digital output (HDMI or S/PDIF). That's an an Analogue output.
Posts by chewitt
-
-
The error to mount is normally caused by the filesystem being marked/detected as "dirty" meaning it has errors. Make sure the card is unmounted cleanly in Windows (or whatever OS the SD card was created from) before removing the SD card, as that can be the cause. The 32MB /storage partition will be automatically deleted and recreated at 100% size during first-boot.
-
LE has a limited number of pre-built add-ons to install things specific to LE or that are useful on a mediacentre HTPC box. If you need anything more we support Docker, which opens up lots of opportunities to run other apps/code in containers.
-
chewitt - sorry to tell you but YouTube have removed the video - you're apparently violating their terms of service.
I think their algorithm detects Kodi and assumes piracy. I've appealed it.
-
I have watched several reviews this morning and every time they visit Youtube it is visibly very bad.
RPiOS has some big plumbing changes to handle with the incoming 'Bookworm' based release and there's new code that's functional but not optimised yet. For sure running a full desktop in the background will incure a penalty over the more minimalist use LE has, but I would expect to see a regular drip-feed of improvements once the dust settles on the board launch. It's not something I'm planning to track mind..
-
I've posted a basic video on YouTube here: https://youtu.be/mYP3Vkysn38. As noted in the opening starwars crawl i'm in the wrong country at the moment so don't have access to demo a broad range of media content. The video covers H264 @ 1080p and 1080i and 4K30/4K60 VP9; the later plays but drops frames whereas the lower refresh-rate 4K30 content plays fine (the 4K30 content is intentionally slo-mo style). Where I bring up codec info you can see the H264 1080p/i media is using around 20-25% CPU.
-
I am sure we will see great device support from the Raspberry Pi team, it's really hard to beat the fact that you can open an issue on Github and they will address it.
We've spotted a few regressions in the kernel and firmware in the last month or so as things have evolved. I'd guesstimate the average time from "first mention of problem" to "fix merged" is around 36h.
Meanwhile an RK3588 fanbois in the Phoronix blog thread is telling me that RK3588 is better because (regarding kernel sources) "the community and Collabora are cleaning them up and exporting them to upstream. It's been a year and things are going well" .. which is roughly how long I've been saying "ask me again in six months" each time someone asks if LE supports RK3588.
QED
-
No hardware decoding for H.264 is pretty weird as well, though probably not such a problem given the CPU performance.
It removes the max-1080p cap that RPi4 has and so far all the H264 4K media I have plays fine; although I'll self-admit that I have very little 4K H264 media since it's not a broadcast standard. Normal 1080p media is no issue at all.
-
Xorg start runs a script to detect the primary GPU and symlink the appropriate libs needed for that GPU flavour to work.
-
Code
cd /storage/.kodi/addons wget https://github.com/glab84/plugin.audio.radio_data/archive/refs/heads/master.zip unzip master.zip mv plugin.audio.radio_data-master plugin.audio.radio_data systemctl restart kodiLibreELEC does not include git but you can download a `zip file from GitHub ^ and unpack it. Then you need to restart Kodi and navigate to the add-on and enable it.
-
Yes, as long as the BT chipset in the dongle is recognised by the kernel and results in BT drivers being loaded. It's never 100% guaranteed but these days most devices use known/generic BT chips and should work.
-
-
Yes, as long as you have no plans to downgrade back to the earlier release (If yes, make a backup first).
-
If you're seeing the Kodi splash things are up/running so you can SSH in to check kodi.log and see what's going on (or not). If there's not much info (as not in debug mode) and you have local DB files then it's possible to stop Kodi, add content to advancedsettings.xml for debug mode, delete the Nexus DB files, then restart kodi to reinitiate the update; but this time you'll see more info in the log to find the issue. If you have an external DB then it's the same process but you'll need to drop the tables in the DB to force the update process to restart.
-
Code
2023-09-24 06:20:36.613 T:1937285696 NOTICE: Using Release Kodi x32 build (version for Raspberry Pi)Changing that URL to HTTP (as ix.io does not use HTTPS) shows ^ which definitely didn't come from an Acer PC
-
I would recommend testing/using LE12 nightlies as those have much newer kernels and mesa code.
-
the new u-boot loader is what is faulty --- and I don't know why it is being used if it is known to be problematic
Wrong. The user hardware is faulty, which creates noise on the UART which is interpreted as keypresses causing boot to be interrupted.
Stats show a reasonably number of AMLGX installs on Hub hardware, though I have no way of knowing whether people are using the upstream u-boot image or the box image
I've been busy tinkering with something else recently so didn't find time for building a tweaked u-boot version. Soon insh'allah.
-
No success despite repeating these steps. I have plenty of free memory and the CPU is idling along with no load. What am I doing wrong?
You're wrongly assuming that LE follows normal Linux distro packaging conventions. It doesn't (intentionally). If you really want to run a Plex server on the same device as a Kodi playback client, install the Docker add-on and investigate running Plex server in a Docker container. I'm not aware of any LE specific howto guides/writeups for this, but Docker is Docker.
