Posts by VLouis

Quote from denis_k

The "Libreelec configuration" addon doesn't launch on Raspberry Pi3.

On updated system or a new installation.

Because of this, the "Libreelec" button in the system settings doesn't work.

Hi, Just think a bit about this. It's many people using LE with RPi3, me too, and if should be a bug like this in LE, here would be a lot of complains. Another things: what LE version do you use? Where is the log to be able to see what's wrong with your device? Did you tried with a fresh install on a spare SDcard?

For logs read wiki.libreelec.tv/support/log-files.

Quote from ieure

I got tired of the rPI's poor WiFi and tendency to hang and need a reboot.

The "rPI's poor WiFi" it's easy to handle with a USB-Wifi adapter, or better with a wifi-ethernet adapter (if you have no chance to use wired network there). The "tendency to hang and need a reboot" could be related to the wifi issue... So, if you still have the RPi4 and could try with wired network or have a cheap USB-wifi, it worth to try it... I'm using few RPi-LE, and with "normal" use (without too much "fancy" addons), it's very stable. Even the one with wifi connection (not the "standard built in wifi"), it's stable.

Quote from ieure

Every time I reboot the machine, it plays audio through the (terrible) internal speaker, instead of over HDMI into my receiver.

You could try to check the sound options in the BIOS. Maybe it's something to set the default sound output to HDMI. Or disable the built in speaker.

Another thing, even if these developed for continuous use, it could be benefic to be rebooted time to time. For this I'm using a cron job, to reboot the LE every day at early morning (like am 3:00).

Quote from JoeCotty

How can i solve this or can this be solved ?

Hi, try to connect the TV directly, and in SSH terminal run the "getedid create" command. More info here: https://wiki.libreelec.tv/configuration/edid

Quote from daggs

do I need to remove the addon in order to get help?

That should be a statement, not a question.

Did you tried to make a backup, and try with a fresh install (only with the minimal addon installed)?

Quote from jam75

What is this log ?

https://wiki.libreelec.tv/support/log-files

Another thing you didn't mentioned the TV server used. If it's the TVheadend, you should use the web interface with admin user to check or modify the recordings (if other ways don't work).

Quote from parc_de

So, its perhaps the Octopus PVR AddOn or KODI in general ... no idea

Without any useful information (full debug log, video codec)... It's the same for us: "no idea"...

Did you tried this:

Quote from chewitt

The config here is generally recommended https://wiki.libreelec.tv/configuration/4k-hdr

Other useful info would be some detail about the video file, read here: https://kodi.wiki/view/Player_process_info

Quote from S1l3nc0r1976

Am I doing something wrong?

Yes.

Without propper logs it's hard to figure out what's wrong. Read here

Quote from wolf7250

Googling this, I suspect it is because I created the EXT4 filesystem on OpenMediaVault which has support for quota metadata.... am I going down the right track with my understanding? And what are my options?

Hi, it's two ways to resolve this:

You build your own LE version with quota support. But that means any times you will want to update it, you will need to build a new modified LE image. If you have experience in linux could be done without "complications".

Backup the data on your SSD and change the partition to be compatible with the LE images. That you need to do once, and you will be able to update the LE directly from LE server.

Quote from ktiix

How can I put my backup file back into this folder?

It's many way to do that:

With the same "live linux" method you can access the "Backup" folder and to copy back the backup package (.tar file).

Windows - Samba connection (explorer - network -> you should see the "LibreELEC" device)

Windows - FileZilla and SFTP connection ("/storage/backup", use the SSH user/password)

Can't be excluded your backup to contain some "insane" files and to get the issue back after restore... in that case open that ".tar" file (ex. with 7zip) and copy back only the most important files (use the "live linux" method).

Quote from DpiTVai

I also try to install KODI on Raspberry Pi OS and everything works.
Can I test something else?

Did you tried with a fresh LE install on another sd-card?

Quote from ktiix

I copied all the contents of the sd card to my laptop, but I don't see any file or folder clearly labelled as backup

It's a second partition with linux filesystem (ext4) on the SDcard. You could use a live linux on a USB stick to boot your pc with linux (no need to install anything), then you will able to "see" that partition and copy the backup somewhere. Or... Use the LE file manager (setting - file manager) "add source" the "root" and you will be able to find the "storage/backup". After that the backup file can be copied to USB drive connected to RPi.

As it's suspected to have a dying SDcard, and the backup is on that card, you should use the pc - live linux version and copy somewhere the all data from that second "storage" partition.

Quote from ktiix

Oh wow. This system has been running for only about 6 months, on a new Samsung A2 EVO sd card. Is there a way to increase the lifespan of the card? That's a hefty price to shell out on this frequent basis if this is normal for a card to die this fast.

First and the easiest is to check the SD-card. "Make a backup of Kodi data that you care about if/while you still can" and you could verify the card in a card reader and PC. If you able to format it and to copy data to it with a resonable speed, should be OK. Reinstall the LE, try to boot it, and if working, restore the backup.

Quote from surfrock66

I took a backup, did a fresh install with the latest .img, restored the backup, and it's happening again.

Hi, probably in your old setup it's something that not compatible with the new version. I would try to make a fresh install, add the addons and settings, and from backup to use only the other stuffs, like media files.

That Radxa Dragon Q6A hardware looks pretty nice. Qualcomm 8 core CPU, Adreno GPU, onboard M2 NVMe (2230) slot, "normal size" HDMI connector... Would be nice to have LE for it in the future. Could be a good alternative for Raspberry.

Hi, I think this needs enabled in the config.txt:

# uncomment to enable analog audio output
#dtparam=audio=on
#audio_pwm_mode=1

Quote from iiiGerardoiii

CRTs have better motion clarity than any "flat display" because of the way it refreshes the image (electron beam). Certain things just look objectively better on a CRT (mostly retro games but also some TV shows if they were released with an interlaced format).

I know well those CRT displays, I repaired enough decades ago. The phosphorescent layer make the image softer, but the quick movements often looks "washed" because this.

Quote from iiiGerardoiii

Telling a CRT user to switch to a current HD display is like telling someone who plays Doom to upgrade from Win95 to Win11 because Win95 is "outdated" when Windows 11 doesn't even have a DOS mode anymore. Certain things were meant to be used in a certain way.

I have no problem with people who like the CRT displays. And usually isn't a problem to connect a CRT to an old video source (like Doom with Win 95). When you want to connect a CRT to a "new" video source, it's another story. Needs "things" to be able to connect (like that vga666 project - GPIO pins with 6 bit resistive DAC to get some kind of analog RGB), resolution incompatibilities. Usually workaround exists, sometimes good, sometimes barely working...

The EDID "explain" what resolutions are supported by the display. If in the settings would be added some other (possible unsupported) resolutions, for other users could lead to blank screen and a lot of complains. At the other hand, if these resolutions it's added in the settings or coming from a modded EDID, probably wouldn't change anything. Instead of this, you should provide more informations about your "audio issues", maybe can be solved in other way, or check that modified "Player" and "System/Display" settings.