2022-07-31, 20:03
Hello:
Having a long-standing WAF issue: sometimes, setting a programme to record in the guide (select the programme, press OK, choose Record) actually sets up a timer for the programme before it.
It seems to more affect programmes which are some way into the future* - for example, if I select a programme at 22:00 this evening ('Our Miss Fred' on Talking Pictures TV), it sets a timer for it as expected.
If I select a programme a few days hence (Wednesday 07:45 - 'Tales of Beatrix Potter' on Talking Pictures TV), it actually sets a time for the programme before it (06:00 - 'The Story of Shirley Yorke').
I've uploaded a debug log of this example here: https://paste.kodi.tv/uwapukeqim.kodi
There was a brief discussion of this back in 2017 - https://forum.kodi.tv/showthread.php?tid...pid2570801 - but it's still happening for me!
I'm running Kodi Leia 18.9 on macOS 10.12.6; my Myth backend (v29.1) is running on the same machine; schedule data is EIT.
* I don't know if this is significant, but at the time of testing/writing it seems to be affecting programmes 23h into the future and beyond.
Having a long-standing WAF issue: sometimes, setting a programme to record in the guide (select the programme, press OK, choose Record) actually sets up a timer for the programme before it.
It seems to more affect programmes which are some way into the future* - for example, if I select a programme at 22:00 this evening ('Our Miss Fred' on Talking Pictures TV), it sets a timer for it as expected.
If I select a programme a few days hence (Wednesday 07:45 - 'Tales of Beatrix Potter' on Talking Pictures TV), it actually sets a time for the programme before it (06:00 - 'The Story of Shirley Yorke').
I've uploaded a debug log of this example here: https://paste.kodi.tv/uwapukeqim.kodi
There was a brief discussion of this back in 2017 - https://forum.kodi.tv/showthread.php?tid...pid2570801 - but it's still happening for me!
I'm running Kodi Leia 18.9 on macOS 10.12.6; my Myth backend (v29.1) is running on the same machine; schedule data is EIT.
* I don't know if this is significant, but at the time of testing/writing it seems to be affecting programmes 23h into the future and beyond.
