There will always be places with bad infrastucture, that dosen’t make it the norm. I really don’t think theese limits should be made by looking at the places in the world with the worst infrastucture and going of that.
And IMO (Capped) cell connections places the bandwith limit concern more with the user and are not comparable to a real static connection.
We are not talking limits but default settings.
But the discussions is a moot point since Plex implements another solution that may or may not get released someday, maybe, no one knows. Plex is not communicating anymore.
As a server admin, I want the ability to prevent someone from transcoding. Period end of story. I don’t want to turn it off server-wide. I don’t care if their data would be eaten up. The resources being expended are at my expense. I am not Netflix.
Their inability to stream the full content is not my concern.
Not an infrastructure issue. Capped internet connections exist everywhere and are believe it or not fairly normal. Hell my provider Comcast limits their home internet. And the Denver metro certainly does not have infrastructure issues causing them to do that. As a matter of fact there was a big article the other day of ISPs trying to sway the FCC into allowing them all to impose data limits. (The FCC has blocked some providers from imposing caps, like Charter Communications)
If you read my posts, I know that and am on bored with that. I don’t know how I can make it anymore clear that I 100% agree with making the default max. It annoys me also that I have to constantly talk people through how to fix that. My response was directed at someone who was essentially arguing that data limits don’t exist and that is absolutely not true.
First, this is not what the discussion is about and completely off the rails now. Second, if you are that desperate to prevent specific users from transcoding but leave it operable on your server (don’t understand why you would do that) there are scripts that exist to do that. 2 seconds on Google would have shown you that there is a Tautulli script that can kill streams for all kinds of very specific reasons.
We’re here griping because no one wants to manage scripts, or add-ons, or any other 3rd party solution that should be doing a task the Plex software should be very capable of doing on its own.
Turning off transcoding for specific users is 1: not at all related to the conversation taking place in this thread, and 2: an incredibly niche feature that I would rather the Plex team spend that time working on something else that has a wider impact, like changing the default on clients to max (the theme of this thread), or enabling subtitle selection on a per series basis, or multiple cuts of films, or better subtitle support, etc. If you don’t want specific people transcoding on your server, then either A: turn off transcoding, B: talk to them about it like most admins do with their users, C: remove them from your server, or D: use that script to do it.
We’re all here to solve the problem of unwanted transcoding, whatever title you want to give it. Plex doesn’t do a good enough job allowing server admins to manage unwanted transcodes which leads to this threads title, defaulting clients to max. The reason this thread is so long and old is because all of us here want PLEX to handle this issue of unwanted transcodes, not a 3rd party, or scripts, or whatever else.
I think you’re missing the point, which is not that we want transcoding off for specific users across the board, but that we don’t want users to transcode when it’s actually not necessary.
I think your missing the context of my posts. I think you should go back and read the posts I made and what they were in response to. If you can’t understand them after that then I don’t know what to tell you. You are all trying to start an argument that doesn’t exist. This started as a response to someone who implied that data limits were a thing of the 2000’s and that is not the case. The rest of this has turned into people coming into this thread with pitchforks while not understanding that they don’t have a fight to show up to.
Ok great. I’ll use the script once they change the default. At least then I won’t be removing people who decided to update their client or don’t know what they’re doing it.
The vast majority of users have no clue what I’m asking them to do when I tell them to change the settings. There are pdfs with screenshots and long write ups to describe this to people who barely know how to use their device in the first place.
Now I won’t really have to worry about those users if the default was my choosing or maximum. Because then the people I’d be choosing found their way to the settings rather than just being clueless when they’re first invited.
Ok I re-read and while you’re correct, it’s confusing, because you’re replying to someone who replied to a comment from 2 years ago.
In the intervening 2 years, Plex let us know about the solution, and how it will work, which should alleviate your concern.
If you were just waxing poetic about how some people want to lower their bandwidth usage then that’s fine, but this might not be the forum for that (considering how many emails this sub conversation has generated, and the fact that the original comment you responded to won’t have any affect on how Plex solves this).
Hence why the comment was directed at the commenter and not any of the people that wanted to ride in on their rage ponies.
I didn’t have any concerns. I pay to have unlimited internet at my place and host a fairly large server with quite a few users myself. My concern was someone chastising someone else when they were actually the one in the wrong.
You can take the passive-aggressive noise elsewhere friend. This wouldn’t have turned into what it did if all of you could have just allowed the correction of one person who was wrong. Instead of that, the rage ponies were mounted and people came storming in without even making an attempt to understand the context of my original comment. I have no interest in bickering with any of you anymore. Take it to someone else.
Use Tautulli to ENFORCE rules on YOUR server. Problem solved.
This thread isn’t even relevant anymore with the workarounds that 3rd party apps provide.
I can use Tautulli to not have my clients default to using a low bitrate that will cause them to transcode and experience poor quality video?
Truly not passive aggressive. I agree with you. But this isn’t the best forum for that considering how many people get notified to replies in this thread.
Yep, by setting a stream kill under certain circumstances with a custom kill message instructing them what to do otherwise no play.
Tautulli knows if the transcode is only happening because of the client’s settings? I want my users to transcode if they want to, but not by default because they don’t know that they need to change the setting.
Unfortunately that does not solve the problem, otherwise we would not be here.
If you think this thread isn’t relevant anymore, you simply don’t understand what we’re asking for.
A kill script is not the same as having clients default to maximum. There are MANY users who would get kicked with a script and are simply not savvy enough to understand.
If you find this thread irrelevant I urge you to stop following replies.
Of course this thread is relevant.
I still want people to be able to transcode, I just don’t want it to be on by default (why watch at a worse quality, and use server CPU reesources when their internet connection is sufficient to direct stream?).
Kicking streams with a message telling them how to change it is NOT a solution to a bad UX, just a (pretty bad) workaround.
