[bishoptf]

Needed to build a new frontend and just used the latest version of Kodi, didn't realize that they had released v19 but that is what I am using.  Everything is working normally except for one issue that my wife came across.  When you are watching livetv and wish to rewind, the screen comes up and it indicates that its skipping/rewinding back but it does not work, it always returns you to the current watching position.  If I pause livetv and after a period of time try to skip/fast forward that works fine, actually better than it used too but trying to rewind/skip backwards will not work.  If I bring up a recording however rewind/skip back works normally so it is only when doing when watching liveTV.

Here are myspecs:
mythtv v.30+fixes backend
lubuntu +kodi19+mythtv pvr plugin

Not clear where I should pull logs from Kodi frontend or myth backend, let me know which or both and I can pull the logs.

[bishoptf]

Looks like this is what I am seeing in the Kodi log when I try to skip backwards:

2021-02-20 08:59:50.377 T:1062 WARNING <general>: OutputPicture - timeout waiting for buffer
2021-02-20 08:59:55.909 T:781 WARNING <general>: Skipped 3 duplicate messages..
2021-02-20 08:59:55.909 T:781 WARNING <general>: CGLContextEGL::SwapBuffers: last msc time greater than interval
2021-02-20 08:59:55.926 T:781 WARNING <general>: CGLContextEGL::SwapBuffers: last msc time greater than interval (1)
2021-02-20 09:00:05.909 T:781 WARNING <general>: Skipped 2 duplicate messages..
2021-02-20 09:00:05.909 T:781 WARNING <general>: CGLContextEGL::SwapBuffers: last msc time greater than interval
2021-02-20 09:00:05.925 T:781 WARNING <general>: CGLContextEGL::SwapBuffers: last msc time greater than interval (1)
2021-02-20 09:00:10.526 T:1062 WARNING <general>: Skipped 3 duplicate messages..
2021-02-20 09:00:10.526 T:1062 WARNING <general>: OutputPicture - timeout waiting for buffer
2021-02-20 09:00:25.908 T:781 WARNING <general>: Skipped 6 duplicate messages..
2021-02-20 09:00:25.908 T:781 WARNING <general>: CGLContextEGL::SwapBuffers: last msc time greater than interval
2021-02-20 09:00:30.925 T:781 WARNING <general>: Skipped 1 duplicate messages..
2021-02-20 09:00:30.925 T:781 WARNING <general>: CGLContextEGL::SwapBuffers: last msc time greater than interval (1)
2021-02-20 09:00:36.425 T:1062 WARNING <general>: Skipped 9 duplicate messages..
2021-02-20 09:00:36.425 T:1062 WARNING <general>: OutputPicture - timeout waiting for buffer

2021-02-20 09:00:36.425 T:1062 WARNING <general>: OutputPicture - timeout waiting for buffer appears to be the issue, not sure what is causing the timeout, if anyone needs any additional information let me know.

Thanks

[thedarkspark]

Hi,
I can confirm the exact same issue when I updated from Kodi 18.9 to 19.0 on my Bravia Android TV (with the Mythtv Addon)

I don't have the issue with the other 3x Kodi PC's running 18.9 on Xubuntu 20.04 (which don't auto update like Android TV), and it's also working correctly on a Xubuntu 20.04 VM.

I am running MythTV .31+fixes backend.

[janbar]

Hi,
I can confirm the exact same issue when I updated from Kodi 18.9 to 19.0 on my Bravia Android TV (with the Mythtv Addon)

I don't have the issue with the other 3x Kodi PC's running 18.9 on Xubuntu 20.04 (which don't auto update like Android TV), and it's also working correctly on a Xubuntu 20.04 VM.

I am running MythTV .31+fixes backend.

HI, the issue should be fixed with the release 7.3.1 of the addon. I missed to implement a change coming with Kodi-19.0. Now it works here. You could confirm it is fixed for you.

[bishoptf]

Hi,
I can confirm the exact same issue when I updated from Kodi 18.9 to 19.0 on my Bravia Android TV (with the Mythtv Addon)

I don't have the issue with the other 3x Kodi PC's running 18.9 on Xubuntu 20.04 (which don't auto update like Android TV), and it's also working correctly on a Xubuntu 20.04 VM.

I am running MythTV .31+fixes backend.

HI, the issue should be fixed with the release 7.3.1 of the addon. I missed to implement a change coming with Kodi-19.0. Now it works here. You could confirm it is fixed for you.

Tested and appears to work like before, thanks for the quick fix!