Thought I’d check in after a few months. Not at all surprised that this still isn’t fixed. Pretty sad tbh
4 Likes
Per @ChuckPa, the ticket number for this issue is logged internally as #13564. Until a fix that mentions this bug shows up in the release notes, I am not going to consider this fixed.
Folks,
Finally getting attention on this.
May I please have:
- Sample of a file which recreates this.
- PMS server DEBUG logs (MUST have debug enabled while recreating)
- Player logs (important as well)
- If playing in browser – which browser & version.
Seriously? I’ve already provided all of the above to you in my PMs.
I provided a sample video file, as well as server and player logs on March 18, over 3 months ago at this point. That should have been enough for the engineering team to reproduce the issue on 1.25 or later. Echoing sentiment by the 100s of other users in this thread to say that it’s ridiculous bordering on absurd that all this time has passed and it’s still not being taken seriously.
1 Like
The reason I asked to test again is:
-
The logs provided are from PMS 1.26.1
-
Engineering could not reproduce using 1.27.2
-
I retested this with 1.27.2.5929-7000 on DS418 and cannot reproduce it anymore with Plex/web in Chrome.
-
They reached out to me to ask if indeed the problem still existed
-and- -
Assuming it did, see how it manifests in 1.27.2 (there have been transcoder changes since 1.26.1)
1 Like
For those who snipe –
- Off-topic posts will be removed.
- If there is nothing to say, please refrain.
1 Like
Making a video of my desktop was not viable.
Please observe these screenshots and their timestamps.
This video played without incident.
I can no longer recreate the problem.
From the engineering team:
In this case I couldn’t repro on the current shipping version of PMS (1.27.2), however I was able to repro on the version suggested in the issue (1.26.1).
It seems to me, this issue (Issue #13564) has been resolved by other independent activities.
I was definitely experiencing the issue on previous Plex Servers (1.25ish) + Web player. But it does seem like 1.27.1.5916-6b0e31a64 is free of this issue (at least in the Ubuntu installation I just tested)! I tested with Firefox and Chrome so far, but I assume the issue is solved! Thanks for the update!
1 Like
Is this also resolved for you?
Upgraded from 1.24.5.5173 to 1.27.1.5916 on Ubuntu Server 18.04.5; transcoding audio and no longer seeing the issue. Will stress test this later, but this release might have finally resolved the issue.
@ChuckPa , are you able to elaborate on what the fix was for this?
From what I can see in the change log, there was an update (bug fix) to the DASH protocol . Plex/web uses the DASH protocol to stream from PMS to the web player.
1 Like
Has anyone been able to reproduce the issue with Version 1.27.1.5916? I have tried both Windows and Linux PMS test servers with this version and can’t reproduce. I’m thinking about upgrading my live server to the latest version but wanted to see if anyone else is having any issues first.
Thanks!
Holy cow i thought i was crazy having this issue for a while now.
Same symptoms, some random videos (TV shows or movies) will run out of buffer.
Updating to latest version and will stress test tonight. This is a pretty frequent issue. Wife tried to watch hunger games and it was freezing every 2ish minutes.
Will try again.
Update: Finished the last 30 minutes of the movie without a freeze, when it was freezing constantly via the web player. Now watching the office (a TV show that it seems to freeze on almost constantly). I’ll report back if I get this issue again. Initial testing seems to have fixed it.
Issue is gone for me as well on the latest, the freezing and having to totally restart the stream to resume one.
But I still do get a lot of random buffering, like my client isn’t requesting enough of a buffer then suddenly it will if I pause or restart it a few times.
Has anybody had anything like that? I can’t account for it, server and client aren’t congested and it happens with Direct Play on LAN as well.
2 Likes
That one I haven’t seen. You’re seeing it with direct play?
I had no streaming issues all night.
I upgraded the Plex Media Server to v1.27.2.5929 and after a couple of tests, the error was not reproduced.
I will test some more during this week and report back.
To all the users who reported and helped troubleshoot this, thank you for your persistence. To the Plex Team, thank you for fixing it. Now, for some constructive criticism.
The communication on this issue has been, at times, counter productive. The community raised an issue with Plex and was swatted down with “Why are you peasants using the WEB?!?” We were belittled with passive-aggressive behavior while asked again and again to prove an issue even existed.
After Plex could finally reproduce the issue and it now appears to be fixed, we’re asked to provide proof (@ChuckPa your “Finally getting attention on this.” from June 30th at 12:28am). Again, the communication here is the problem. If you had started off with “We believe this is fixed because we can no longer reproduce it internally, can you all verify with xxxx version and provide logs if you still have the issue”, then we wouldn’t feel like we’re just being strung along like we have felt for the last 7 months. While I agree that we need to stay on-topic and not devolve into sniping, it is important to realize why this behavior may be occurring.
There’s a technical lesson to be learned here, which the engineering team has done by fixing the issue. There is also a social lesson to be learned, in how to communicate effectively with people. This lesson is relevant and on-topic, because humans are social beings and ineffective communication wastes time and causes emotional responses that derail progress.
We’re all happy and thankful the issue is fixed. But we should not forget to learn from this and remember than not all issues are purely technical.
Thank you @ChuckPa and Plex!
Sorry, my reference to “peasants” was how I interpreted this:
I know that may not have been the intent, but I have been exclusively using the web interface to play my content for years and I can’t remember ever having an issue until this one. The attitude of disbelief and sarcasm over the course of 7 months (I get it, pandemic and life happens) made it seem like Plex was trying to kill off the web side of playback, not get it working again.
I’m not intending to pick on anyone, I know I’m far from perfect myself, I just want to articulate the technical and social lessons I think we can all learn from this thread. We’re all in this boat together! 
Problem seems fixed. Wait and see. thanks @ChuckPa and Plex dev team.
