[gromgsxr1]

Thanks. Can you confirm that you have programmes on your list that do not have episodes, like a film, or some special programme?

there are a few one off documentary's (single episode) no films

[kereltje]

Thanks. It is most likely some change in the data BBC returns. I'll try to replicate when I get home.
Can you open an issue on github?

[gromgsxr1]

Thanks. It is most likely some change in the data BBC returns. I'll try to replicate when I get home.
Can you open an issue on github?

I did create a new BBC account added 2 multiple episode series and the list loaded. I then added a single one off documentary and got the error removed that item and it opened again. Il open a git issue tomorrow

[TheJezstarr]

For the last week, I've noit been able to watch live TV on iplayer. I use it to get the correct regional version of the news (our antennae gives us West Midlands, but we're in the East) This also occurs on Firefox, but not Chromiumn.

I've had Kodi running for about 36 hours today, so I have snipped the error log from all of yesterday's detail, but this shows setup and crash:
bazizikuke.kodi (paste)

There's some odd 404 errors in there. Sometimes I get audio and no video, sometimes it just stops. This time it crashed Kodi altogether, but that's not usual.

[izprtxqkft]

This time it crashed Kodi altogether, but that's not usual.

actually, kodi crashed kodi, or rather it just quit

this is a known behavior when 2 addons try to create busy dialogs at the same time
- https://github.com/xbmc/xbmc/issues/24526

in your case it looks like netflix and iplayer collided

so this part can be excluded from any diagnosis of the iplayer 404 errors and the other issues you are experiencing (those issues i am not commenting on)

[kereltje]

There's some odd 404 errors in there. Sometimes I get audio and no video, sometimes it just stops.

The only time I've seen a HTTP 404 status on manifests and streams from iplayer is when you've only managed to circumvent geo blocks up to the moment you actually play the stream.
Are you sure you don't use any kind of VPN, proxy, smart DNS, etc, that may inadvertently route (some off) your network traffic through some other part of the world?
If that doesn't help, try to seek back 30 seconds in the live stream while it still playes. If you can't get it to play at all, try to watch from the start.
If that doesn't help either, enable libcURL in component-specific-logging and create a new log.

[TheJezstarr]

The only time I've seen a HTTP 404 status on manifests and streams from iplayer is when you've only managed to circumvent geo blocks up to the moment you actually play the stream.
Are you sure you don't use any kind of VPN, proxy, smart DNS, etc, that may inadvertently route (some off) your network traffic through some other part of the world?
If that doesn't help, try to seek back 30 seconds in the live stream while it still playes. If you can't get it to play at all, try to watch from the start.
If that doesn't help either, enable libcURL in component-specific-logging and create a new log.

I am absolutely sure that I'm not using a VPN/proxy, and it works as normal in Chromium (but not Firefox)
However, the 'skip back 30s' suggestion did work. Takes about a minute for audio to start, but once it does, skipping back seems to re-buffer and video works fine.
I did enable libcURL logging, though, so here's a log in case this isn't just a 'me' problem:
https://paste.kodi.tv/sefuluyego.kodi

[kereltje]

However, the 'skip back 30s' suggestion did work.

That suggests Kodi is requesting segments too close to (or over) the live edge and are simply not available yet. A live broadcast happens 'now', but it takes a little time to encode en distribute the streams. A DASH steam is in fact a series of packets (segments) of a particular lenght. If a boadcaster is distributing segments of, let's say, 10 seconds, it takes at least 10 sec of 'live' show before a segment is ready to be sent.
This is all handled by Inputstream Adaptive and AFAIK has never been a problem with iplayer streams.
The only I thing can think of right now, is that your system's clock is slightly ahead - what your sytem thinks is 'now' is yet to happen at the BBC. It would only be a few seconds, otherwise live wouldn't play at all.

[TheJezstarr]

However, the 'skip back 30s' suggestion did work.

That suggests Kodi is requesting segments too close to (or over) the live edge and are simply not available yet. A live broadcast happens 'now', but it takes a little time to encode en distribute the streams. A DASH steam is in fact a series of packets (segments) of a particular lenght. If a boadcaster is distributing segments of, let's say, 10 seconds, it takes at least 10 sec of 'live' show before a segment is ready to be sent.
This is all handled by Inputstream Adaptive and AFAIK has never been a problem with iplayer streams.
The only I thing can think of right now, is that your system's clock is slightly ahead - what your sytem thinks is 'now' is yet to happen at the BBC. It would only be a few seconds, otherwise live wouldn't play at all.

Thank you! That's the problem. Rolling back the system clock 30s has fixed it!!

[kereltje]

Thank you! That's the problem. Rolling back the system clock 30s has fixed it!!

Glad it works now.
I wouldn't advice to set the system time manually though. I think it's better to sync to a time server, so it's exactly on time and stays that way.