And what if doesn’t? What if this just causes more problems on server-end? Then it doesn’t matter if it helps the client-end if I’m telling them they ain’t allowed to use it because it ruin the server? What are you going to do then. Wait another 6 years to come up with the conclusion we already have come up with?
Well, this is why we have different ideas and prototype things internally. If we weren’t confident in it, I wouldn’t be talking about it. Again, I’d ask you to withhold at least some judgement until you’ve had a chance to properly experience what it is we’re working on.
And I should do that I agree with you but it’s just not easy when you straight out turning our ideas down. And asks us not to do the same with yours. Like don’t misunderstand me I’m looking forward to see what this is you have come up with. But I’m just making it clear if this ain’t working we are going to be alot of serveradmins that’s going to be pretty annoyed by you guys
The title and the request kind of diverged 
I’m not just trying to rain on people’s parade, but trying openly and clearly communicate on what things will or won’t happen. I’m not one to lead people on, and then have them be shocked when XYZ is or isn’t there.
Well I get that. But still it just seems like you are trying to avoid server admins have any decisions in how their servers are supposed to be used? You say we can control it by terminating transcodes and so on if we don’t like the approach. But then you have to do something about you subtitles. Or the fact that the web client always transcodes audio to acc. And so on and so on. So really turning it off transcode isn’t an option. But I don’t have a problem with audio transcoding. Video transcoding is the real sinner. And I can live with that in minor occasions. Which your new thing should be able to do according to you. But just the words “it will be up to the end user” that catch my concerns me. And that it won’t be a server sided decision if we doesn’t turn something off that can’t be turned off. I know it can but then 70% of my users can’t use my server
Give the server control of what is and isnt allowed to stream. If we want X user to be able to transcode we have that option. If other users we know have strong internet and we want to disable transcoding for them then we should be able to. There’s absolutely no reason as server admins why we can’t force specific things on our users. We and WE ALONE know how our servers operate and what they can and can not handle. I persoanlly have ONE single family memer who I wish to allow transcoding. The rest of them not at all. Reason is they have stronger internet and this one person does not. But when other people change their configurations to something we initially do not allow it slams the server AND RUINS IT FOR EVERYONE. That’s what we are saying. Stop allowing users to DDoS our servers unknowingly.
If we could control everything, then sure there would be less transcoding, but for some clients, like Roku, or web browsers, or gaming consoles, we don’t really get much of a say in what they do or don’t support from a codec point of view. Where we can, we maximise the codec support for the clients where we do have control. What we’re working towards though is minimising transcoding wherever possible, and try to have folks Direct Play where possible.
This may be fine but as it stands clients on all platforms will transcode with the default settings. Like many people have said in other posts there will be less headache maxing everything out than having every single client transcode right off the bat.
Yeah and what I’m trying to say I’m fine with direct streaming which they won’t even be allowed to if I turned of transcoding. So what you suggested earlier isn’t something we can do thats my point. So the whole client side and end user thing doesn’t stick right with me. Seems like Plex wanna take over all our hardware and use them for your gain
What on earth thinks we want to take over your hardware? 
We’re offering more control to end users to improve their playback experience, give them higher quality and reduce transcoding cases.
If we want to disallow certain things from specific users we should have this option. If we don’t want X user to transcode we should be able to set that. These users who know ABSOLUTELY NOT A THING should not be allowed to unknowingly slam our servers to the dismay of everyone else.
It was supposed to be a funny exaggeration. But still you wanna give them higher quality equal maximum quality. Great but then you want them to be able to decide how much bandwidth they using well fair enough but that means transcode. You want to make them able to have a better playback which means on unstable connection it will transcode. Then not transcode then transcode. Go up and down in setting constantly sounds really unhealthy for my machinery. What could go wrong? In Plex we trust. It’s only my hardware. (That’s where my little funny exaggeration come in)
I just kill streams and send text messages when people change their settings or they get reset by an update because it’s better to make one user mad than everyone.
WIth the way the new way works, you’d only be seeing a transcode if it was otherwise unable to play, and the user has then selected a lower quality in order to continue playback. If the option to Direct Play became available again, they’d be prompted to do that.
535 messages in we get a glimpse of the solution!
That actually sounds pretty decent. I knew we could squeeze some details out of you! Haha!
We just had to be annoying and President enough
As I said earlier, I didn’t want to give away too many details when things are still in flux, but we’re further through the prototyping phase now, so I have a bit of a better idea of where things are getting nailed down, and can say confidently on how (some parts) will work. 
Now you say someparts? So there is more to it? A bitcoin miner aswell?
