4 years later this is still a major problem.
And now it seems like Plex has eliminated this workaround. So something is happening there - but why did they not eliminate that bug instead?
Tirelessly the Plex developers are working against the users. You see?
I only have problems seeking if Iām viewing the last 3 to 5 minutes of a show - If you miss something important in the show climax and try to back up, it will just spin forever.
This occurs on my Amazon FireTv v2, and FireTv Stick 4K. Looking at the Plex Dash app on my phone, it only appears to happen when the client has buffered transcoded video right to the end of show. Until the buffer includes the end of the show, I can rewind without issue. The Plex Dash app shows there is no data being sent to the client when this happens.
I first noticed this bug several years back, but then it was working properly for a long time, across many updates (running Plex on Synology NAS). It has only reared itās ugly head again in the last 3 or 4 updates. It is extremely annoying.
@chaz-leopolds That is exactly what happens to me on Shield TV Pro⦠if I miss anything near the end of content⦠I canāt rewind. Gotta restart the content and ffw to the end again. Annoting af.
Iām also affected, especially when using āSkip Adsā. Nine times out of ten it will freeze spinning. I have to hope it remembers where it was up to, stop the playback and resume (if it managed to store where it was up to).
I see this on Android TV and Iāve just checked and the web client does the same.
Honestly bizarre that a media streaming product cannot skip through media without freezing.
Thank you so much! Disabling subtitles while I fast forward fixed it
Will this be fixed in an update?
This has started happening to me on my Hisense TV recently. No skipping possible. Even finishing one episode and automatically skipping to the next causes it to fail. I must stop the play and restart it to get it going again. Turning off subtitles doesnāt change the behaviour.
Pausing before rewind and fast forward seems to help.
I have the same issue on my WebOs Tv.
Same thing on my Hisense TV! It works fine with all of my other devices, and it started with tv just recently. Worked perfectly fine before.
Server Version 1.23.3.4707
Plex for VIDAA 3.13.14
After last update, Heisense TV fastforwarding works fine. Thank you!
Why wonāt Plex address this? I canāt take it anymore!
Why wonāt Plex address so many other bugs?
Stupid company communications policy
Itās subtitles
Turn them off and then play from beginning
Fast forward to where you want
Then put your subtitles on
Itās not.
It always is for me
If they can find the subtitles bug this would fix my issues that have been present for over two years
Iām not saying there isnāt another bug with rewinding and fastforwarding though 
Same. Issue. The āUse alternate streaming protocol for video playbackā helps, but still rough.
PLEX SUPPORT! What can we provide to help resolve this issue?
Running a Synology DS1019+, and Iām having the same problem that just about everyone in this thread is having.
When is Plex going to fix this issue? I mean, itās obviously a problem, and I donāt feel like trying a ton of different configurations that may or may not fix the problem.
Come on guys, this is A BIG ISSUE. Can someone PLEASE fix this for your paid, supporting customers? LOL Incredible that this bug is around for over 4 years now.
Real simple, take a 4K movie, and try to fast scan forward or backward with itā¦it wonāt work. It will just time out, and in some cases crashes the Plex client.
Come on Plex developersā¦DO YOUR JOB!
Thanks all for this much needed thread! How frustrating.
Iāve managed to fix it on my Samsung TV by pausing the show, choosing a lower resolution, fast forward, and play again. My original is 2.4mb and I could play it at 2mb or lower.
I tried Chrissiās method above (plex settings > debug > tick āuse alternative streaming protocolā) and this may have helped a bit but I still couldnāt fast forward or rewind on the TV.
Hope this helps someone else.
Hi Plex.
Please, please, please address this issue. Itās been around for literally years and seems to get no attention. Near every week we see client and server upgrades with loads of fixes ( I read the notes ) and features. But this incredibly frustrating issue persists