The Plex Pass holder isn't going to have to pay for the app, but any other accounts that aren't Pass will. This is for Android, iOS and Roku, for sure. I'm guessing your friend is probably NOT running Plex Media Server himself?
+1 been waiting a long time for this. is it out yet or will it be?
The Plex Pass holder isn't going to have to pay for the app, but any other accounts that aren't Pass will. This is for Android, iOS and Roku, for sure. I'm guessing your friend is probably NOT running Plex Media Server himself?
No he is not. Thanks for letting me know. i told everyone till now android is free. Now i know not to tell them that anymore.
Yes, to be able to set a cap that applies to all subscribers is sorely needed.
I too would love to see this feature. It is actually one of the most needed features in my opinion. I really hope it is brought to Plex soon.
+1 not sure how this hasn't been implemented yet.
+1
I'd settle to just know who the person is sucking the bandwidth from my server without going through router/network logs. I can tell via resource monitor what IP address is sucking up the bandwidth, but making the link between username and ip address can be a bit more difficult when most of your friends live in the same state.
Just add another line to this picture below Audio.
Remote Quality - 20 mbps
(Or IP Address!)
"Oh hey, that's my idiot friend Billy again, time to revoke his access until he learns."
Obviously, being able to set a upper limit on outgoing internet bandwidth per client would be preferred.
"Oh hey, that's my idiot friend Billy again, time to revoke his access until he learns."
It could also be "Oh hey, that's my bad for not providing an audio format that my buddy Billy needs for his client." Or, this "I need to call Billy and walk him through the process to set up his client to best support the media I have on my server." Most of the time the users haven't got any idea what the settings are, nor how they impact the server, bandwidth or other users. This is on US as Admins to make sure they set things up to fit our environments. This isn't on them...
There aren't easy ways to see this kind of information historically. The bottom line is, tools like these need to be a part of Plex, so we, as server admins, have the tools we need to do the job. PlexWatch and PlexWatchWeb give us the basic tools to do this, but these should be a part of the Web App that gets installed when we install Plex itself. Not an addon that not everyone can run.
+1
This needs to happen.
+1
I'd settle to just know who the person is sucking the bandwidth from my server without going through router/network logs. I can tell via resource monitor what IP address is sucking up the bandwidth, but making the link between username and ip address can be a bit more difficult when most of your friends live in the same state.
Just add another line to this picture below Audio.
Remote Quality - 20 mbps
(Or IP Address!)
"Oh hey, that's my idiot friend Billy again, time to revoke his access until he learns."
Obviously, being able to set a upper limit on outgoing internet bandwidth per client would be preferred.
Then in the meanwhile you definitely want to setup PlexWatch and PlexWatchWeb. PWW will let you view the playback history of all users and whether the streams were transcoded, IP address, client used, bitrate etc etc. Great solution until server-side restrictions are introduced.
For example I have one user who uses Chrome on an underpowered laptop for playback and I can see that every item of HD media they playback is transcoded to a lower bitrate that the laptop can handle. They mentioned recently that Plex started buffering for them and when I checked PWW I could see there was no transcoding anymore of high bitrate video so I advised them to reduce the bitrate again and all was well.
Same goes for anyone over-using Plex (relative to others) - I can see with PWW who has been consuming the most media and if it is impacting on others, particularly at peak times, I ask them to reduce quality to 480p for a week or so. I can make sure they're doing this with PWW.
I built a server with a pretty good CPU so transcoding 2 or 3 streams at a time is no issue, but my upload is restricted to 20Mb/sec so it's important that not everyone is streaming full bitrate 720p or 1080p media at the same time.
+1
this is a much needed feature.
+1 Please....
+1 This seems very essential when you use shared libraries
I know that the number of votes or the rating a request has does not ensure it can or will be implemented, but it seems odd that this request is marked as "Popular", and other requests with less votes are marked as "Very Popular."
- Server-Side Speed Limits/Caps for Shared/Subscribed Users (~550 votes - Popular)
- Multiple Cuts Of Movie (~360 votes - Very Popular)
- Restart Plex Server From MyPlex (~360 votes - Very Poplar)
- PMS: Support of x86 Intel Evansport architecture (~400 votes - Very Popular)
How about bumping the status of this request up to "Very Popular?"
+1
Or, this "I need to call Billy and walk him through the process to set up his client to best support the media I have on my server." Most of the time the users haven't got any idea what the settings are, nor how they impact the server, bandwidth or other users. This is on US as Admins to make sure they set things up to fit our environments. This isn't on them...
Nope, it has to implemented on server side. I have access to 4 plex servers. Do I really have to remember the max bandwidth for each server and then change manually the quality on my client each time I watch a movie on a different server ? No way.
Nope, it has to implemented on server side. I have access to 4 plex servers. Do I really have to remember the max bandwidth for each server and then change manually the quality on my client each time I watch a movie on a different server ? No way.
I KNOW this needs to be moved to Server Side, which is my whole point... What might work on your server for bandwidth and CPU resources might bring my server to it's knees. The current design REQUIRES the server admin to be the one to set up the media to fit his environment. What fits yours might not fit mine. So I need SERVER SIDE controls to make how I stream to my users fit the hardware and bandwidth. I also need to set up the media to maximize my server's resources for all of my users to make use of my media.
With some hardware, regardless of the controls in place, if the bandwidth requirements are too high for the wire to the world, the stream will still be transcoded. If the audio in that stream is the wrong format, it gets transcoded. If the container is wrong for the client, more transcoding. If you put in unsupported subtitles, again, transcoded.
If you don't have your media set up in the right type of container, with the right codecs for video and audio, regardless of Billy's settings, he is going to force your server to transcode. That was my whole point... All the controls in the world aren't going to make up for having an under-powered server and the content not set up correctly for the clients you intend to stream to.
Yep, having the content in the best possible format is surely half the battle!
It doesnt need anything special, just tell PMS to set the client preferences speed to what you want. The server doesnt even have to manage bandwidth, it just locks the client at 1.5mbps whatever, locking the user out of the setting, piece of piss.
Seriously, 2 f@dging years!!??
+1 i think there needs to be more control here.
Even better might be some smart control that I tell the server my bandwidth and how much I want reserved for me. Its not often i have any trouble with this, but i would like to reduce the bandwidth for certain users who seem to be hogging.
