SQL statements are meant to be run inside sqlite3 session. You open it with sqlite3 ~/.kodi/userdata/Database/MyVideosXX.db (replace XX with database version number). Then type the statements at sqlite> prompt. After you're done type .quit. Be careful with UPDATE statement because you might destroy your data with it if you (or the author of instructions) make a mistake.
Posts by gibbon
-
-
Hi, just regular LibreElec 10.3 generic in a multiboot setup (grub) using:
menuentry "LibreElec" {
set root=(hd0,6)
linux /KERNEL KERNEL boot=/dev/sda6 disk=/dev/sda5 quiet nosplash tty systemd.debug_shell
}
This debug shell can also be enabled from within the system:
systemctl enable debug-shell.service
Works on every device. But in order to use it kodi.service needs to be stopped first. Because when it's running it "hijacks" GPU and makes virtual consoles inaccessible. That is changing VTs with Ctrl+Alt+F<n> or chvt produces no visual effect. At least that's what happens on RPi4
99.999% of LE users have no idea that a local console exists (in debug mode) and thus have no need to access it, so we haven't wasted space in the image adding font-size-changing binaries that 0.001% of users or less will use.
It can be useful at times for those of us with keyboard attached to their box (and good eyesight). There is also possibility of having no device at hand to SSH from.
-
My biggest gripe with RPi4 is a lack of hardware VC-1 decoding which no release of LE is able to fix. I've seen people claim it's a niche format which it is except it's standard for Blu-ray movies and is actually quite common especially among early releases. I wonder if software playback without framedrops is feasible with CPU overclock.
Software optimisation for HEVC is unlikely to be reimplemented as it was. Most of the tricks required will be hard to upstream and this time around (after 9+ years of learning the hard-way what it means to maintain downstream forks) the goal for the Pi Foundation is to upstream everything. I'll never say it will be never be done, but I think it's unlikely and best case, it's going to take a large effort over a long period of time to happen .. by which time a large percentage of users will have upgraded to new hardware.
Out of curiosity what kind of optimization are we talking about? Decoding stuff in kernel?
My way was a very long way with the RPI4 and libreelec. But now it works. I have 2 55" TVs from Sony with a RPI 4. All working flawlessly with 4K content with HDR.
Hey that's a nice setup you have there. Considering that typical 4K HDR content is encoded with 10 bit color depth and that current LE release supports only 8 bits and trims the extra bits, have you experienced any trouble with that?
-
You need a wrapper to launch retroarch so it's not a native plugin that works within the Kodi application. Personally I wouldn't waste your time trying to make the native support work even though it's tempting.
I see an effort existed for LE 8 that built RetroArch plugin based on Lakka sources (itself forked from LE?):
GitHub - ToKe79/retroarch-kodi-addon-LibreELEC: RetroArch KODI add-on for LibreELECRetroArch KODI add-on for LibreELEC. Contribute to ToKe79/retroarch-kodi-addon-LibreELEC development by creating an account on GitHub.github.comI can't tell how much of a hack it was and why it hasn't been updated. Maybe the developer who is a member of Lakka simply lost interest in LE.
-
Can RetroArch be used as Kodi add-on in regular LE? Is forking the system absolutely necessary?
