Same problem here on Samsung TV. Rolled server back to 1.16.3.1402 and problem went away.
2 Likes
I have the same setup and same problem.
I reinstalled version 1.16.3 and everything’s working fine again.
What is the easiest way to downgrade on Unraid?
Is there an official program for beta testing for Samsung (or other smart) TV’s? I’m sure some of us would gladly volunteer to help out.
1 Like
Im interested to know what the bitrates/resolution for each of those files are. sounds like the higher the bitrates the worse the skipping is from my readings.
I was gonna ask someone to try this first before me or roll a chance cube to see who goes first (shoutout to The Phantom Mennace) thanks Bernd!
1 Like
I’ve seen it with bitrates as low as 900 kbps
That very much depends on the repo used to install Plex. If you use the official Plexinc app your mostly screwed without backups as Plex still does not allow previous builds #general:plex-features when are you going to allow this?
If you use the Linux repo then you can uninstall the app and reinstall specifying the version i.e. 1.16.3.1402-22929c8a2 as the version which will pull only that build. Really just should not update as UnRAID does not take much of feature benefits and only adds risk as developers still don’t allow rollback its a lost cause with Plexinc version.
I had no issues downgrading using the plexinc docker in unraid, I just changed the repository to “plexinc/pms-docker:1.16.3.1402-22929c8a2”
Same issue with Samsung and Plex since latest version release. This is simply par for the course.
It’s been a gamble every time I’ve launched Plex on a Tizen Samsung since I bought it. Shameful development effort for that platform.
How I’ve missed Orca these past few years.
Same problem with a Qnap NAS and a Samsung TV. Fixed installing version 1.15.4.993.
Same problem here. I rolled back the plex server to 1.16.3.1402 and now it’s back working.
I have 3 samsung TV’s (same issue on all of them).One other thing that may help PLEX people.
My son is my neighbour,Using his WIFI connection rather then mine also solve the issue.So is it because my PLEX server & my smart tv’s were on the same WIFI???(I tried 2.4 & 5.0Ghz)anyway since i could not stay on his WIFI,rolling back was my best choice.I do not intend to make any update for a while until PLEX people can figure out what cause the problem on the samsung TV’s
Using a different WIFI connection on my samsung TV’s did work for me(same provider,different connection).As soon that i came back to my own WIFI on all the TV,s problem reappear…So if your PLEX server is on the same wifi then your TV’s,it will not work unless you downgrade you server to 1.16.3.1402…(Same issue on a Fire TV stick)
same here with PMS on ubuntu and Samsung Tizen TV. Both downgrading or disabling directplay seem to work
Its not just with Samsung app…which is a problem on there as well. Also an issue with Firestick…Seeing this issue even after downgrading to 1.16.2
You need to post this issue here: https://forums.plex.tv/c/plex-players/streaming-devices and tag it with fire-tv.
Include in your post:
- PMS version
- FireTV app version
Information Update:
I was just informed that the problem is clear now and they’re working on fixing it.
The problem, and now to reproduce it, are in hand now.
12 Likes
I just updated to 1.16.5.1488 and my KS8000 still suffers from the skip forward issue after re-enabling Direct Play. Playback is okay with Direct Play turned off.
Plex version 3.103.1
Tizen 2.4.0
How did you roll back your plex version on your Smart TV?
