Server Version#: 1.41.7.9799
Player Version#: 1.109.0.329-ea562b95
This can’t be right, can it? Watching a movie provides expected bandwidth graph output but when watching live TV, whether local or remote, shows bandwidth in the low Kbps according to the graph. This happens whether the client is using the old iOS app, the Plex for Windows app or Chrome browser.
Is anyone able to confirm whether they experience this too?
Still happening after updating to 1.41.7.9823
I can’t say that this applies to your ‘situation’ but it has been reported several (many?) times that the graphs displayed from Windows servers is inaccurate - particularly with CPU utilization.
I mean, it should be resolved or refined, but if you’re able to direct stream, I didn’t see that this is effecting anything.
Thanks for taking the time to respond. This is a recent development; A couple of updates ago the bandwidth graph more or less corresponded correctly with the summary at the top of the dash. Now it doesn’t. 
CPU utilisation graph is as expected.
Thanks again.
I tried doing a quick search about the graphs on Windows and couldn’t find the posts that referenced this, but I think I read they are looking into changing how they gather the data from Windows and so this might change in the future…?
I think it’s our (users) responsibility to report these issues as they occur, but at the same time, if it’s not impacting the functionally for either the server or clients, I don’t think it will be a high enough priority to fix/update it
That said, as to many users dismay, Ones is investing a lot of time, resources and money to revamp not only the Plex client UI, but they are also working on the server side as well with a more modern ffmpeg media engine that will (drastically!?) improve streaming performance with more video cards as well as make it easier to update the engine to newer ffmpeg builds as they are released or implement features that will benefit streaming in the future.
They are also removing old code for features no longer supported (boo!) and relieving them with new open API solutions for 3rd party agents (yeah!).
These changes are huge for it’s users, but also higher for the future of Plex and should keep it competitive (IMHO the best of the bunch) with other similar platforms.
I would expect that if people like yourself (but not me who knows the issue exists, but rests/relies on old posts exposing the same or similar issue) continue to show where fixes and improvements can be made, they will address them…
… But then again, I tend to wear rose colored glasses even when the skys are dark.
I’ll keep an eye out for this issue on my Windows Plex Server and add to the thread as needed.
I usually have multiple simultaneous streams, so it will be harder to see, but I’ll put some effort into it in the next few days.
John
Updating to 1.41.8.9834 seems to have resolved it.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
