Posts by chewitt

  • Zidoo V-12 Remote

    See if that content works?

  • [RK3576] LE for H96 Max M9 TV Box

    1. Not unless someone upstreams support for the box to the upstream kernel and u-boot

    2. There are nightlies for some RK3576 devices and equivalent test images with marginally newer kernel etc. in my test share

    3. LE supports whatever level of 'properly' the current upstream kernel supports

    4. If you want things to work 'properly' it will probably need device-specific dts/u-boot. Nothing exists for that device.

    In short; there is code and prior-art in our buildsystem and we publish that under GPLv2 so anyone can go nuts and experiment and do whatever they like with it. There are no nicely typed up technical notes or HOWTO guides. You are welcome to ask questsions, but you should have low expectations for anyone spoon-feeding you with instructions on how to author support for your box.

  • Libreelec wants to create new drive

    The Creator app has no code to assign drive letters. That function is solely done by Windows itself when it auto-detects a filesystem on the inserted USB stick. So please direct your pithy ire towards Microsoft who have been authoring that kind of problem for their consumers for about the same lenght of time you've been using computers.

    I've no idea what specificially happend or what the underlying Windows problem is, or even what version of Windows you have (seems you are too busy telling stories to give useful facts) but every version since Windows 95 has a 'Computer Management' control panel and this has a filesystems section that allows your to reformat devices and add/change/deletion the current drive letter assignments.

    NB: Once you create LibreELEC install media you need to boot from the USB stick and the installer will guide you through the process of installing to an internal drive. Once you select an install target the installer will ask you multiple times to confirm that you want to overwrite and destroy existing content on the drive, but if you keep hitting yes, it will do that. I'm mentioning because you sound like the kind of Windows user whose next post in this forum will be complaining that our installer hosed your entire Windows install.

    I'm also going to point out that Kodi has a perfectly good native Windows app, which might be your easiest option.

  • [RPi4] Stuck on LibreELEC Screen when Booted through AVR

    The config.txt file has 4K60 modes enabled so I'll guess that the HDMI port the TV connects to the AVR on only supports 4K60 4:2:0 input so the AVR advertises this to the downstream RPi4 which does not support 4K60 4:2:0 output; so the RPi4 cannot negotiate a valid 4K HDMI mode and Kodi is forced to start 'offscreen' and you see a blank screen instead of the Kodi home screen.

    Switching the HDMI input on the TV to a port that supports 4:2:2 input or changing port properties to allow 4:2:2 input will be the best fix. You can also add video=HDMI-A-1:1920x1080M@60D to kernel boot params in cmdline.txt to force the initial DRM connector state to 1080@60 instead of 4K to get the Kodi home screen showing; but this will not fix the underlying 4K handshaking issue if/when you try to play 4K media.

    NB: This wiki article has some general notes on setup: https://wiki.libreelec.tv/configuration/4k-hdr

  • SVT Play livestream spontaneously quits after 1 second if played on LibreElec

    Quote from nosen

    One, I want to use the stable branch so that I don't have to deal with stability problems, and two, I think it's useful to keep debugging this so we may identify the bug, and stop it from popping up again later.

    I've been running self-built LE13 nightlies for the last ~2 years and the only time they have been unstable is when I've been doing intentional experimenting of my own, but even that's been low drama. The nature of the LE 12.2 release means it's prob. received considerably less staff runtime testing than LE13 nightlies; but hey, users do obsess over the 'stable' label.

    As you're the single LE user reporting the problem and there appears to be a valid workaround I have low interest in chasing the problem on LE12.2 .. esp. when you're already trying to pass the buck and avoid doing the test I've already suggested that might narrow the scope of the problem. The differences between LE12.0 and LE12.2 are too large to do anything but guess, and even if something was obvious the solution is unlikely to go into an LE12.2 image (as there isn't expected to be another release) so the fix would be in LE13 (which doesn't appear to need one).

    Quote

    I want to be crystal clear: the bug only manifests on a small subsection of content, namely live tv i.e. the same thing you'd see on the regular terrestial broadcast

    That ^ wasn't fully obvious in the original report (and perhaps not to the GitHub thread either). Kodi is essentially a big fancy wrapper around ffmpeg's capabilites for playback, and since the kernel and ffmpeg versions/patches in LE12.2 and LE13 are the same, I'd still be thinking about config and behaviour of the add-on more than the OS.

  • SVT Play livestream spontaneously quits after 1 second if played on LibreElec

    LE12.2 is a fork of the LE13 codebase from a couple of months back retrofitted with K21 not K22, and notably with the same ffmpeg version used in both. So if you want to play 'spot the difference' there's more in-common between the LE12.2 and LE13 than there is between LE12.0 and LE12.2 (and that difference is too large to spot anything). Combine that with the add-on working for multiple users with non geoblocked content on both releases and my suspicions are towards add-on config or something environmental not an issue with the base OS; and hence the suggestion to test that theory.

  • Syncing profiles with server

    Nothing changed. Kodi allows you to create different profiles and to use a remote DB to store library and some (but not all) config data. However there is no concept of roaming profiles or a Kodi-internal way to keep data synchronised over multiple devices. You always need some form of external-to-Kodi sync, and being 'external' this inherently runs into data consistency issues.

  • SVT Play livestream spontaneously quits after 1 second if played on LibreElec

    I'm not an expert in reading streaming service logs (and different services will behave differently) but it looks like audio and video are separate streams, and everything goes through a normal looking process of obtaining stream manifestsa and then selecting audio and video streams. The audio stream looks to be selected, but then the video stream switches from SD (448x252@50) to HD (1080p@50) and then the stream stalls.

    There are quite a lot of streaming add-ons installed so I would be interested to see logs from a current LE13 nightly that has only the SVT play and inputstream.adaptive add-ons installed. I'm not expecting anything to be different, but it will remove some noise from the log. I don't see any 'errors' that would e.g. indicate Python issues or something that traces back to the underlying OS. IMHO if there's a difference between the add-on under LE and the add-on the author tested on Ubuntu it's more likely to be add-on or i.a configuration and not the OS environment.

    NB: The stream is H264 and RPi5 does not have H264 hardware decode or hardware deinterlacing so the v4l2_m2m errors in the log that Da Flex has seized upon are nothing more than ffmpeg correctly failing to find hardware decode and deinterlace /dev/video nodes that don't exist and failing back to use software capabilities. All normal and expected on an RPi5 device.

  • Changed behaviour of screensaver black between -11 and 12

    I'm using 'black' as the screensaver with a variety of ARM SoC boards since forever and nothing has changed. I'm admittedly using LE13 images for a long time now but when I was using LE12 in the past (and LE12.2 is based on the same Kodi codebase/version) it worked fine. The description of "First couple of seconds it's dark grey, then pitch black" sounds more like the TV having an issue.

  • DHCP with Manual DNS

    I'd argue the bug is not strictly adhering to the logic of using DHCP .. OR .. manual configuration, i.e. If you switch from DHCP to manual I would expect that the correct action is forcing the user to (re)define everything from scratch. That's probably an issue with our implementation of a ConnMan agent, and something to fix.