Yeah, I was expecting such an error. We are working on our own log server.
Copy & paste kodi.log into PasteBin instead, and post that link.
Posts by Da Flex
-
-
On LE 11.0.4...
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 -
On LE 11.0.4...
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 -
Yeah, RPi5 is the brute force solution of video decoding
. It misses the low-power A55 cores of Rockchip RK3588, and also hardware acceleration for common video codecs. -
To be precise, login by SSH, and use these commands:
- cd .update
- wget https://releases.libreelec.tv/LibreELEC-Generic-legacy.x86_64-11.0.4.img.gz
- reboot
-
- activate passthrough at the audio settings
- add force_eeprom_read=0 to https://wiki.libreelec.tv/configuration/config_txt
-
waclaw66 You are using banned add-ons. That means no support. I suggest to install LE from scratch.
-
waclaw66 Upgrade to 11.0.4. Switch CEC off / on on your TV. Try another HDMI cable, if available.
If it still fails after this...
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 -
Dude, you are looking at a compressed image.
Decompress it, and mount that image to look inside.
-
On Kodi level: no. Your question has been answered earlier:
-
LE doesn't support interlaced mode on RPi, so switching to progressive is expected.
-
wyup Only Dolby can say what's legal - ask them. My take is: If a device can decode DV, it has to have a license. It doesn't matter where the decoding algorithm comes from. So I guess it's a license-per-device thing.
-
Out of interest: would the usage of the Pi Model 3B+ bring a noticeable performance increase compared to the 3B?
You will notice a difference (I got both), but such an upgrade makes no sense since RPi 5 was released.
-
Do you think the Flirc case will be sufficient?
That case is good enough for those values (medium overclocking):
If you go extreme, you will need something like this:
Raspberry Pi 5 4GB Overclocked at 3GHZ CPU/1.1GHZ GPU
I think I won silicon lottery again. Ordered two Pi’s - one hit 3GHz CPU and 950Mhz GPU without additional voltage and 1.1GHz GPU with +0.05V over_voltage_delta=5000.
The other one couldn’t hit 3GHz without additional voltage, so I sent it back.
-
I wonder if any of this could be hacked in the future, to create the necessary drivers. Or hopefully we just move past DV, and get an open implementation that doesn't cause this mess.
It has to be conform to Dolby licensing conditions. If you find a legal hack, let us know.
-
-
josh4trunks Use the CoreELEC forum.
-
Delete the cache now, and reboot.
