Server Version#: 1.16.1.1246 (Nvidia Shield)
Player Version#: 3.98.2
There seems to be separate time cursors for the FF/REW button and the skip forward/back buttons (left and right on the TV remote).
If I seek using FF and then play, all is OK. If I then follow up by trying to skip forward using the right button on the remote (which should skip by 30s), it instead skips to 30s after the position before I used FF!
This means it’s almost impossible to use skip forward/back after having used FF/REW in any one viewing session.
It’s definitely happening on every show I’ve recorded using Plex DVR from UK FreeviewHD broadcasts - h.264 and AAC_LATM codecs, DirectPlayed. Not tried other sources yet.
I’ve also noticed that even skip forward (30s) and back (10s) from the left/right direction buttons on the remote are unreliable.
Forward can be anything from 30s to 45s. Back can be anything from 3s to 10s. Gets worse the more you skip in a recorded programme. For example, on an hour long programme with 5 minute ad breaks every 15 minutes, when I get to the 45 minute break the skip forward and back is all over the place and almost unusable.
Again, all on UK HD programmes recorded using Plex DVR (h.264 and AAC_LATM).
Latest Samsung Tizen 3.0 app (3.105.0), latest PMS for Android TV 1.16.3.1402 on Nvidia Shield.
I’ll need to remove the file from my Google Drive shortly as it’s taking up so much space. If you could download it and let me know when you have it that would be much appreciated.
Hi @sLumpy. The recent update has fixed the incorrect timings being shown after skipping, but I’m still getting yuge random skips forward after using the 30s forward skip to skip ads in an hour long programme, usually after around the 50 minute mark.
Have you managed to reproduce this? If not, I have another sample file if it helps.