[Spirou]

I am running on Kodi-18.0-ALPHA1 Git:20180216-0fcc225-dirty.
It seems at least rewind is broken in live-tv with timeshift activated (I tested both FILE and RAM setting). Also fast forward produces some strange artefacts/flashing. Playing recordings or videos it all seems to work just fine.

[FernetMenta]

Please elaborate on "broken"

[Spirou]

What I am experiencing is:

• When I press "rewind" on my remote the live stream is starting to rewind but not for much more than a second. Then it resumes instantly into normal playback again. This happens at any position during playback, so timeshift buffer usually is filled with more than a second of video.
  
• When I pause live-tv and then press "fast-forward" on my remote, it start fast-forwarding from current position but the screen is "flickering" or rather "flashing" in short intervals.
  

I am experiencing none of the above when watching a recording or video file.

I have ubuntu 16.04.03 LTS (desktop) with updated kernel  4.13.0-32-generic x86_64 running only kodi 18 ALPHA1 and vdr 2.3.8 on my system. For my dvb card (cine-s2 v6.5) I am using the udated mediabuild drivers from herrnst. Apart from that everything is standard and regularly updated.

[Spirou]

Anyone else who is running kodi 18 on Ubuntu 16.04.03 LTS and has the same issue or can confirm it is running as expected?
If this is an individual info waht else can I do to troubleshoot? Just provide the debug log? Change settings?

[FernetMenta]

I'll look at this soon.

[FernetMenta]

seems to be caused by this change in pvr code: https://github.com/xbmc/xbmc/commit/2e82...ee45816292
this makes every seek fail.

I pinged the author

[Spirou]

Glad you could find the (likely) root cause. Hope the author can fix it. Pause/Resume still works fine but I really miss the ability to rewind.

[ksooo]

Will be fixed with https://github.com/xbmc/xbmc/pull/13589

[Spirou]

Thank you!

Update: Just checked out latest code from git which contains the fix. Rewind works like a charm. When fast forwarding I still get the flashing screen (looks like display is quickly flapping between stream and a green background), but besides that, it is working So many thanks again to @FernetMenta and @ksooo for your support and fixing.

[FernetMenta]

What platform are you using for Kodi?

[Spirou]

Platform is an Intel SkyLake i3-6100T CPU on an ASUS B250M-C board, using Sky Lake Integrated Graphics:
GPU: Mesa DRI Intel® HD Graphics 530 (Skylake GT 2)
OpenGLVersion: 4.5 (Core Profile) Mesa 17.2.8

TV Tuner card: Cine-S2 v6.5
OS: Ubuntu 16.04.4 LTS (kernel: Linux 4.13.0-36 -generic)

[FernetMenta]

At what ff speed do you observe the issues?

[Spirou]

I need to observe this more closely.

For a quick test I just started an FTA HD channel, pressed pause and then started fast forwarding. Strangely, there was no flickering at all.
An hour ago I started watching a recording of a Pay TV channel which was still ongoing. When fast forwarding - at least at 2x and 4x speeds - I am pretty sure the display was flickering at either speed.
After the recording had finished I started watching the same recording from the beginning and when fast forwarding, to my surprise, there was no flickering.

I will test FTA, FTA HD, Pay TV and Pay TV HD at various FF speeds to see if it makes any difference.

Update: I am not quite seeing the systematics behind it. On FTA HD channels it seems to occur less frequently. On the Pay TV channel I have it - no matter if SD or HD. And at lower FF speeds (2x, 4x) it happens more frequently than at higher FF speeds. This is from a few tests I did. But maybe the effect is at pure random.

Interestingly while testing, the below lines are filling up kodi.log:

xml:


23:41:00.011 T:139857870415616 WARNING: CRenderManager::WaitForBuffer - timeout waiting for buffer

23:41:26.931 T:139861320571264 WARNING: Previous line repeats 49 times.

23:41:26.931 T:139861320571264 ERROR: CVaapiTexture::Map - Error: invalid VASurfaceID(6)

23:41:30.519 T:139857870415616 ERROR: Previous line repeats 26 times.

23:41:30.519 T:139857870415616 WARNING: CRenderManager::WaitForBuffer - timeout waiting for buffer

23:41:30.552 T:139861320571264 ERROR: CVaapiTexture::Map - Error: invalid VASurfaceID(6)

23:41:30.574 T:139857870415616 WARNING: VAAPI::FFGetBuffer - no surface available - dec: 0, render: 3

23:41:30.610 T:139857870415616 WARNING: CRenderManager::WaitForBuffer - timeout waiting for buffer

23:41:30.998 T:139857878972160 ERROR: VAAPI::CheckSuccess - Error: surface is in use(16)

23:41:31.151 T:139861320571264 ERROR: CVaapiTexture::Map - Error: invalid VASurfaceID(6)

23:41:31.153 T:139857870415616 WARNING: CRenderManager::WaitForBuffer - timeout waiting for buffer

23:41:31.195 T:139857878972160 ERROR: VAAPI::CheckSuccess - Error: surface is in use(16)

23:41:31.312 T:139861320571264 ERROR: Previous line repeats 1 times.

23:41:31.312 T:139861320571264 ERROR: CVaapiTexture::Map - Error: invalid VASurfaceID(6)

23:41:31.893 T:139857870415616 ERROR: Previous line repeats 3 times.

23:41:31.893 T:139857870415616 WARNING: CRenderManager::WaitForBuffer - timeout waiting for buffer

23:41:31.893 T:139861320571264 ERROR: CVaapiTexture::Map - Error: invalid VASurfaceID(6)

23:41:32.375 T:139857878972160 ERROR: Previous line repeats 2 times.

[Spirou]

Does the above give any hint? I am observing this only in Live TV but the problem may lie somewhere else.

[FernetMenta]

I spotted the problem. It's a vaapi issue. I hope I get some time coming weekend to fix.it.