Checked with latest update 1.25.9.5721. Not fixed so far.
@ChuckPa Anything on this?
Hi @BigWheel,
Can you look into the bug report that @ChuckPa submitted on 3/18/22?
We would like to know if Plex has had any progress in getting this fixed. We are all stuck on PMS 1.24 and would like to upgrade to 1.25 once this is fixed.
@ChuckPa , any news?
No news⦠bad news⦠![]()
Iām working with Engineering on this.
Itās not at all forgotten.
If we could clone the Transcoder team 3-4-5 times, weād be set. ![]()
Thereās a lot of work being done right now.
Speaking personally, Iām holding my production PMS at 1.24.5
For my needs, I see no reason to advance past 1.24.5 at this time.
Thank you for the update, @ChuckPa, we appreciate the candid responses.
I have an issue with playback stopping at last 5% of movie. It still sends data through the network but nothing is happening on the device. This issue has been going on for a year. It happens on my chrome browser and PS5. It does not happen on my Samsung Plex app.
Itās always direct stream. I can restart the movie/stream at the time it died out and it just dies out again eventually like it only gets 1 buffer window and never refreshes to end of movie/stream.
Itās very annoying to do as Plex will mark the movie as watched/remove from queue because <5% of the stream was remaining.
I do see in the Server log many times before it dies:
[0x7fa0d8195b38] WARN - [Transcode/1n8gy3z4mcffclt64jt919fw] Transcode runner appears to have died.
Just another report that Iām experiencing this as well⦠finally today found this thread https://www.reddit.com/r/PleX/comments/ralets/plex_stops_buffering_randomly_when_using_plex_web/ and this post. I thought it was just me, glad Iām not crazy.
Yeah, Iāve had the same issue for at least a year or more, if you pause a stream for less than 2 minutes, you can resume no issue, but if you pause it for longer, itāll resume playing until the buffer runs out and just sit there until you reload the page.
i solved the issue using plex client for windows, this is not really a solution as it should work also via web browser, but the client is not bad, I had to say that using client also the transcoding is far less fr my library.
So please try plex for windows https://downloads.plex.tv/plex-desktop/1.43.4.2971-aa2133cc/windows/Plex-1.43.4.2971-aa2133cc-x86_64.exe
As you noted no, it is not a solution to the problem noted in OPās post. This issue is specific to Plex in the web browser. I do fall back to this myself when it becomes too annoying. Iāve found the āUse alternate streaming protocol for video playbackā which forces audio to transcode to mp3 as a decent work around for web browser use but it is not a solution either. Typically when Iām at my PC Iām not aiming for a blow it out of the park experience so mp3 is fineā¦but Iād prefer no transcoding, even if itās light.
Any news on this ?
Of course not, but Iām sure they are planning lots of unnecessary new features instead
Hi @ChuckPa,
Can you see where this ticket is in the system? Has it been assigned to anyone?
Iām not really sure why Plex wouldnāt give this bug highest priority. They seem to be fixing a lot of low priority bugs and ignoring this one.
Thanks.
I looked back at the tickets. The one we had for this was included with another fix.
From what you and others are saying here, itās not been fully resolved.
I would like to update both the server and player logs which capture this happening so I can read them then open a new or reopen the old ticket.
To do this, I would like:
-
Server logs set to DEBUG enabled with VERBOSE disabled.
-
In the Plex/web settings - enable DEBUG logging (itās off by default)
-
Now recreate the fault.
-
Stop the playback
-
Download the Logs ZIP file from PMS
-
Go to Settings - Plex Web - Debug and click the
herebutton (near the top) -
Copy and paste that text into a text editor file and attach it with the serverās ZIP logs.
Sigh. Sent logs again. Still failing with latest version of PMS.
To all following here:
There is a new regression.
1.24.3.5033-757abe6b4 - works for the āCamerpersonā test file
1.26.1 and above ā fail.
Yes, as mentioned in the very first post in this thread from over 6 months ago.
Back I go again. UGH.
Folks,
Working with @swlody , we went through it a few times.
He slapped me around with a wet
and kept me on target ![]()
We got it.
The trouble report has been submitted to Engineering with the test file.
I can confirm, 1.24.5 is the highest version which works with this particular file in this case.
This means that there is some obscure regression in the transcoder.
Why this file wonāt transcode while others will is a mystery to me but Iām sure Engineering can figure it out.