Posts by gibbon

    Code
    2023-01-28 02:22:08.697 T:1434     INFO <general>: Starting Kodi (19.5 (19.5.0) Git:19.5-Matrix). Platform: Linux ARM 32-bit
    2023-01-28 02:22:08.697 T:1434     INFO <general>: Using Release Kodi x32
    2023-01-28 02:22:08.697 T:1434     INFO <general>: Kodi compiled 2023-01-07 by GCC 10.2.0 for Linux ARM 32-bit version 5.10.110 (330350)
    2023-01-28 02:22:08.697 T:1434     INFO <general>: Running on BCM2835 with LibreELEC (official): 10.0.4, kernel: Linux ARM 64-bit version 5.10.110


    Why is Kodi is compiled for 32-bit ARM in RPi4 build? It might have been the case before in earlier releases but it's the first time I noticed this.

    Yes but the effect is that the audio is then downmixed to a stereo signal.

    What kind of audio interface you're using? You should be able to send multichannel PCM over HDMI as long as the receiver supports it:

    Quote

    For digital audio, if an HDMI device has audio, it is required to implement the baseline format: stereo (uncompressed) PCM. Other formats are optional, with HDMI allowing up to 8 channels of uncompressed audio at sample sizes of 16 bits, 20 bits, or 24 bits, with sample rates of 32 kHz, 44.1 kHz, 48 kHz, 88.2 kHz, 96 kHz, 176.4 kHz, or 192 kHz

    HDMI - Wikipedia
    en.wikipedia.org

    AFAIK current latest LE & Kodi releases does NOT have a special support for DVB-T2 USB sticks. So you have to check whether the DVB-T USB stick you wish to use is supported by Linux kernel (release that current LE is running on) or not.

    I'd have to investigate this since I'm not sure whether they need any device-specific driver in kernel. They are USB devices after all so also part of some standard USB "class"?

    This thingy effectively prevents you from having a heatsink? I don't see the point then unless you're okay with not fully utilizing your RPi 3/4 CPU and GPU. And Pi Zeros lack Ethernet so they won't make very good job of distributing channels to LAN. Personally I was thinking about getting DVB-T2 USB stick. But I don't know how good is their support under LE and Kodi.

    I tried to replace the path VIDEOS FOTOS (old) by the new one VIDEOS FOTOS SERIES in MyVideosXX.db

    Ok I think you misunderstood how text REPLACE function works. You did

    REPLACE(strPath,'/current/VIDEOS FOTOS/','/updated/VIDEOS FOTOS SERIES/');

    while what you describe is more like

    REPLACE(strPath,'/VIDEOS FOTOS/','/VIDEOS FOTOS SERIES/');

    Quote

    What I don't know is if it's also necessary to repace the HDD label (PELIS 04 instead of VIDEOS FOTOS and if so, where it is.

    Of course. It's in various places. You can copy files to your PC and use graphical tool DB Browser for SQLite to browse database tables (Browse Data tab) and execute SQL (Execute SQL tab).

    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.

    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 LibreELEC
    RetroArch KODI add-on for LibreELEC. Contribute to ToKe79/retroarch-kodi-addon-LibreELEC development by creating an account on GitHub.
    github.com

    I 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.