@Maxou44 Well, that’s your opinion. I think the old way is much better, what good can 100% cpu usage over 5min do? Starting multiple streams is a nightmare, and I got a pretty ok-ish cpu with 10k+ passmark.
… And it makes the transcoder settings within PMS pretty much useless.
if you launch multiple stream your system share the ressources between transcoders, and because files are chunked you don’t have any stream problems 
@Maxou44 said:
if you launch multiple stream your system share the ressources between transcoders, and because files are chunked you don’t have any stream problems
I still agree with @DuffHQ that this is not a good implementation right now, transcoding the entire thing is really not something you would want, I prefer that plex takes it easy on my cpu instead of maxing it out for 5 minutes.
not to mention, if the session dies or the user pauses or restarts watching, he does the entire thing all over again, for a 2 hour movie, that is a lot of CPU/watt being used for nothing
edit: plus, not to mention that the PS4 or the IOS client of Plex doesn’t do this, so I would say it is a bug regardless and plex should transcode on the fly and maximum like 10% ahead of what the user is watching
Yes, I can confirm this is happening.
Thans for your analysis and explanation @Maxou44
However, I must agree with the others… this is just one of many new bugs on PLEX. In my experience, PLEX its becoming unstable.
Whats the point of having settings for the transcoder, if the plex web app bypasses them?
Some said it only happens when the Audio only was being transcoded? That hasn’t been my experience. Here is one of a few that has happened to me this evening and is currently running. This really needs to be fixed! Between this and the scanner just randomly wanting to scan either my Movie or TV directory cont’, this is killing my server.
So, is there any update on news on this, is it an actual bug, will it be fixed in a future version?
I just heard my server go nuts again over a single transcode because of the 100 % cpu load, on a freaking Xeon, please fix this, it is not healthy for my hardware…
This has been forwarded to Engineering. There is no other information at this point.
As for the Roku, others have needed make 3-4 requests but ALL have been honored by asking ssmith@roku.com.
The tech support people do not know and do not honor this…
@“Michael.De.Vijlder” I wouldn’t get my hopes up. It has worked like this in Firefox for ages. I can see some of the benefits mentioned in this thread and you could argue this isn’t an issue, but I for one would consider this a huge issue. In theory shared resources and no issues sounds good, but in real life I’ve had direct playing clients getting timeouts trying to start a stream because 3 other transcoded streams has a race going… not to mention slow respons from other services running on the same server.
@DuffHQ said:
@“Michael.De.Vijlder” I wouldn’t get my hopes up. It has worked like this in Firefox for ages. I can see some of the benefits mentioned in this thread and you could argue this isn’t an issue, but I for one would consider this a huge issue. In theory shared resources and no issues sounds good, but in real life I’ve had direct playing clients getting timeouts trying to start a stream because 3 other transcoded streams has a race going… not to mention slow respons from other services running on the same server.
I know, but regardless, this really is a big bug, otherwise you wouldn’t be able to select a throttle time in the settings, it is meant to work like that…
I notice that this ‘bug’ doesnt affected all browsers. While my screencap above shows a Chrome browser having the issue, my own Chrome browser does not. So it my be a version thing ( at least with Chrome).
This is what I am currently running and it does not seem to cause the issue for me.
Version 60.0.3112.101 (Official Build) (64-bit)
@foebik said:
I notice that this ‘bug’ doesnt affected all browsers. While my screencap above shows a Chrome browser having the issue, my own Chrome browser does not. So it my be a version thing ( at least with Chrome).This is what I am currently running and it does not seem to cause the issue for me.
Version 60.0.3112.101 (Official Build) (64-bit)
Sure you’re not streaming from the bundled PlexWeb version? I’ve just double checked with the same Chrome build and no difference. It’s the PlexWeb version that makes a difference.
@DuffHQ said:
@foebik said:
I notice that this ‘bug’ doesnt affected all browsers. While my screencap above shows a Chrome browser having the issue, my own Chrome browser does not. So it my be a version thing ( at least with Chrome).This is what I am currently running and it does not seem to cause the issue for me.
Version 60.0.3112.101 (Official Build) (64-bit)
Sure you’re not streaming from the bundled PlexWeb version? I’ve just double checked with the same Chrome build and no difference. It’s the PlexWeb version that makes a difference.
Good point, will have to check tonight. I just have it set up in my Muximux and dont remember where I had it linking too. But I’m betting you are right.
This bug is only in the new Web app player on app.plex.tv. If I use the older player bundled in the server through my reverse proxy, it still follows the normal transcoding server side setting. With the new web app it will continue to transcode until the file is completed. I didn’t see this post here and posted over here.
Gang,
I’m trying to work through this and help bring some focus.
I have chatted with the Web team and they’ve seen the problem as well.
It is a server-side issue and not the hosted vs bundled but does appear to manifest that way.
This said, May I ask who is seeing the issue and on which specific version(s) ?
Gave all of my users my *.plex.direct url and have had no issues with the bundled player from version 1.5.5 all the way up to the current plexpass release.
For absolute clarity please (I"m going to get some devs in on this now).
For additional information,
Last, and most important, IF possible, Two sets of logs please, using the same file and the same PMS version, (clean logs - no verbose - delete pre-existing logs before starting PMS and the recreation)
@ChuckPA said:
For absolute clarity please (I"m going to get some devs in on this now).
- Line 1: “PlexWeb 3.17.2” Refers to the Hosted (plex.tv) app ?
- Bundled is 100% ok in all regards?
- FireFox is a standing issue even before 3.17.2 ?
For additional information,
- Platform / OS please ?
- Seen with ANY other players?
- Anything else I missed ?
Last, and most important, IF possible, Two sets of logs please, using the same file and the same PMS version, (clean logs - no verbose - delete pre-existing logs before starting PMS and the recreation)
Yes
Yes
Yes
Windows 8.1 Pro
No. (Got Samsung, LG, TvOS, iOS, PS4, Android Mobile, Android TV, PMP and OpenPHT clients besides PlexWeb)
Don’t think so, others may correct me.
I’ll try to provide logs, but anyone feel free to beat me in the race cause I’m crazy busy
Ok, here’s what we need to do. VERBOSE logs as a demonstration of what’s happening. Machine not playing ANY other files for ANYONE.
Now repeat steps 3 -> 9 for hosted Plex/web on **SAME FILE **
The Team is waiting for this.
FYI I see it on one of my User smart TV that uses Opera.
@foebik said:
FYI I see it on one of my User smart TV that uses Opera.
If you can recreate as done above, it’s that much more help. I’ve not heard back from the transcoder team but in looking at logs… 2 - 2.5 minutes of playback is also good
