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

    I have the same issue (live TV from SVT Play stops after ~1 s) on a Vero 4k+ and a Vero V, running OSMC (https://osmc.tv/). Both stopped working at the same time, not related to any updates at that time. Not sure if there's any relationship between OSMC and LibreELEC (I guess not?). Since both of my devices stopped working at the same time, I would assume the issue is due to some change on the SVT side.

    That is puzzling, since I can play live TV on 13.0 nightly but not 12.2.1. Maybe the livestream format that SVT is serving is a little unorthodox or "out of spec" somehow, in a way that some players tolerate but stalls others players?

    Quote from nosen

    You understand me correctly, but I don't want to switch my daily driver to the nightly version for two reasons: 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'm using LE nightly builds for years, am my experience, the fixes are includes more quickly in the nighlyes. I don't update the nightly at every new version, just after few weeks maybe, and feel more stable than the "stable" release. For me that's only a label. :)

    Your choice, wait till this will be fixed in the next "stable" build, or use the LE 13 nighly where already it's working well...

    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.

    Whoa, a couple of things:

    First, thanks for letting me know that the nightly version is stable enough to daily-drive. That piece of information puts the situation in a new light. I didn't consider it to be a viable workaround. I don't think I came across as obsessing over the stable label though.

    Second, I'm not the only user. There has been another LE user in this very thread who confirmed the issue.

    Third, I didn't try to pass the buck. I assumed (correctly, it turned out) that you had misunderstood the issue (despite having clear step-by-step instructions for how to reproduce the bug). When I figured out you hadn't understood the issue, I asked for your confirmation. I thought you might direct me to do another test, now that you had a better grasp of the problem.

    I assure you that I act in good faith and want to help improve Kodi and LE for everyone. If that's not an interesting proposition for you, we can stop trying to fix this bug. I want to keep going, but I need your help to continue.

    As for right now, I'll try switching to nightly and piece by piece install and configure until the bug comes back, if it comes back at all. Does that sound like a good plan to you?