Posts by chewitt

  • [RPi4] No Audio on LE 11 and LE 12

    Quote from osflake

    As You Can see HDMI0 and HDMI1 is available.

    The image shows "EDID=none" and whatever causes no EDID to be read is the source of your problem as Kodi determines HDMI audio capabilities using EDID data from the HDMI connection at startup. No EDID = No audio.

    The config.txt and distroconfig.txt files are full of changes from known-working defaults; although most are #commented out and are legacy items which are no longer supported, there are also other items present which will change behaviour.

    In short, this is not the clean install that you were asked to make (it looks like an upgrade from an older LE9 install) and there is so much config mess from you guessing at things that it's not clear what change(s) might be involved. Please go make a true clean install. Unless there is a self-inflicted problem with bad cables or HDMI adaptors (or an Argon case) it should then "just work" like a normal RPi4 install.

  • Can't rip CD with cddb infos anymore

    https://github.com/xbmc/xbmc/pull/25700 <= seems to be this issue, which is fixed for K22, but wasn't backported to K21.

    The quick fix is to update to a current LE13 nightly image which uses K22. The longer fix is waiting for someone to see if the patch backports onto K21 and then either submit a backport upstream (and then bumping the Kodi version in our LE12 branch) or we can backport the patch direct. I'm not sure there's any plan for another K21 maintenance release. I've been using K22 images for the last year and despite technically being pre-alpha code they've been stable, so I'd probably pick the quick option.

  • Can't rip CD with cddb infos anymore

    Please provide a full debug log.

    How to post a log (wiki)

    1. Enable debugging in Settings>System Settings>Logging
    2. Restart Kodi
    3. Replicate the problem
    4. 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

  • [RPi3B+] RTSP Stream Not Playable

    Quote from LoneWolf

    the 3B+ only offers 640x480, 800x600 and the selected 1024x768. I couldn't get it to set higher one, or any in the correct format.

    The display pipeline on RPi0/1/2/3 is 1920x1080 maximum and supports a specific set of configurations. The much newer RPi4/5 can handle 4096x2160 max and a wider variety of configurations.

    If you can capture/share some examples of the stream we can look deeper.

  • [RPi5] WiFi Speed Drops to Zero by GUI Activity

    Quote from fliz

    Does the Flirc case impede the wifi signal?

    The issue is not the flirc case impeding the signal, it's the generally rubbish WiFi on the board in the first place. It's a compromise for basic functional connectivity not high throughput performance.

    Two suggestions:

    a) Use an external USB device, the Realtek and Mediatek chipsets used in most of them are now mostly supported in upstream kernels which reduces the lottery of things working or not (still never guaranteed, but things improved a lot).

    b) Use a WiFi > Ethernet bridge. I'm often testing devices in locations that aren't near Ethernet so I use some old Apple Airport Express units in bridge mode to get things connected. No drivers needed and they have a decent antenna. Amazon has options for mini/portable bridge units for a similar price as a better external USB WiFi dongle.

  • [RPi3B+] RTSP Stream Not Playable

    I'm fuzzy on the precise details in some areas ( popcornmix can probably describe things more accurately) but I think this is broadly what's happening:

    The H264 hardware decoder supports a maximum 1920x1080 resolution on both boards (RPi4 inherited the same IP block as RPi3) and you are trying to play 2560x1440 resolution media on a 1024x768 monitor. As hardware decoding cannot be used because the resolution is too large the boards fall back to software decoding + resizing to match the output resolution + adjusting from 15fps to 60fps refresh rate (the only easy bit). RPi4 has the CPU grunt for the task so you see output. I'm unsure why RPi3 shows a blank screen where RPi4 shows output, but this is probably due to a capability difference between RPi3 (1080p max) and RPi4 (4K capable) so display pipelines are not equial. Disabling DRMPRIME in Kodi disables hardware decode and changes rendering in the kernel DRM layer; hence you now see something on RPi3 instead of nothing, but I'd guess it's still beyond the capabilities elsewhere in the pipeline so it's not usable output.

  • Inputstream FFMpeg Direct Problem

    Quote from acamas125

    I'm using this sports add-on to watch live NBA games. There are links called Home and Away. Most of the time when I click on that, it's either LE will crashed or playback failed will appear. While Kodi on Windows 11, the video plays almost instantly.

    In the absence of any technical information (crash logs or such) I consulted my son's magic 8-ball, and it said "it is certain" .. so there's your answer /shrug

  • [HELP] running LE on a MXQ PRO

    The board pic posted in the Armbian forum doesn't show the WiFi chip on the board. Yours is a Silicon Village "SV6256P" but no guarantee what the other user had (might be the same, might be Realtek, etc).

    Searching on GitHub finds a few "ssv6x5x" drivers, but some of them are tagged as being usable with Linux 4.4 (as used in older downstream Allwinner kernels) and there are substantial crypto changes since then which mean drivers will not forward-port onto the modern upstream kernels that LE uses. You might find newer ones, or you might not /shrug

    NB: Even if you do find a newer one, LE will not add support for downstream drivers that have no visible hope of being upstreamed to the kernel; we've only just managed to exorcise the last downstream Realtek drivers from our codebase. You're welcome to self-build custom images with your own driver changes though.

  • Stuck on Kodi screen after reboot

    Please provide a full debug log.

    How to post a log (wiki)

    1. Enable debugging in Settings>System Settings>Logging
    2. Restart Kodi
    3. Replicate the problem
    4. 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