Paste kodi: debugging was not enabled. Do so, restart LibreELEC, and reproduce the problem.
Also, sound output to what? TV speakers, AVR, something else?
Paste kodi: debugging was not enabled. Do so, restart LibreELEC, and reproduce the problem.
Also, sound output to what? TV speakers, AVR, something else?
If it helps anyone else
Not really. We still have no idea what skin(s)/add-on(s)you have installed. But it all seems to work now.
Running on Amlogic with CoreELEC (official): 19.3-Matrix, kernel: Linux ARM 64-bit version 4.9.113
Why are you visiting the LibreELEC forum and not the CoreELEC support forum?
INFO <general>: CAddonMgr::FindAddons: repository.elementum v0.1.83 installed
As per forum rules which apply to Kodi in general, no support will be available when repos/add-ons facilitating video piracy are installed.
I suggest you first fully clean up your Kodi setup before asking your next question(s).
Kodi worked well but shown a little yellow thunder near the clock.
Get yourself a decent power supply, as the current one is struggling to provide the power.
Sure... But "if it looks stupid but it works, then it isn't stupid".
would you tell me how
What you earlier suggested:
using NFS for recording and Samba for replay at the same time
I wondering using NFS for recording and Samba for replay at the same time everything woks fine.
There is only one way to find that out.
What OS is running on the RPi4 server with 4TB?
Handling files is a relatively demanding job on a CPU for a RPi, both USB30 and Gigabit ports really only work at half speeds in my experience. So depending on the overall bitrate of the VDR streams, it's possible that the RPi4 is simply not up to the task, despite having set up NFS correctly.
I don't think the naming scheme is the problem, it's better to have actual names than identifications as X6sK8L3 like motherboards do.
The problem is that certain video/graphic capabilities are not in each release of every video chip generation. The cheaper chips (Atom, Celeron..) don't always get all video goodies that Core 3/5/7 get. And then marketing people "forget" to mention the missing features.
Jasper Lake is from Q1'21, so you'd think Linux already has some support from 5.12 or 13. But apparently you do need 5.15+.
Did you also try the nightly from https://test.libreelec.tv/ ?
Kodi uses a relational database, but paths are used in various fields.
It's not the directory of the library that needs to change. If you want to change source paths in the music database, then there are 4 tables to edit: art. path, source and source_path. Browse these tables with a SQLite tool, and you will see which fields need editing.
Also there is the textures field in the local Textures13.db file. It also contains path references.
Before you start hacking, make backup copies of the MyMusic72.db and the Textures13.db files.
Also, have a look here: https://kodi.wiki/view/HOW-TO:Up…when_files_move
Your TV should be able to display the RPi4's picture 1-on-1 pixel perfect. All TVs have a setting to disable "overscan". With LG this is called "Scanning" on my TV, but LG can have renamed it by now. Only as a last resort should you use Kodi's calibration settings.
What is dmesg?
It's basically a rundown of your system that also includes your hardware components.
The dmesg listing you can provide via a SSH connection into your LibreELEC device, and type on the command line:
It should return a URL which you need to copy/paste into your next post here on the forum. And if wifi doesn't work, you will need to connect via ethernet cable instead. You can find the IP address for connecting in the System details of Kodi.
Seems I have no chance to save my work. Right?
Doing a video/music database export (when things are running okay) always works as a good backup system.
A remote SQL database you can always backup via sqldump or tools like PHPMyAdmin. And don't forget to include commands to recreate the tables.
If you are familiar enough with SQL, then you can edit/change the paths in the various (4?) database tables.