Ah ok I’m with you, I’ve not seen that prompt, I just figured it came hand in hand with the bandwidth detection!
not sure how to pull shield logs but i’ll figure it out and send them over. i know what the issue is. my shield is on a different subnet so i had to tell my server that that subnet is local streaming. it connects locally but my plex use to think it was remote and would force a relay until i changed some settings that @ChuckPa helped me with.
Hey @DaveBinM, firstly thanks for being so helpful in this thread, secondly, is there any news on any more users / clients having this rolled out to them?
We’ll be rolling this out to more users in the coming week or two for Android TV. Other platforms will come in time, but I don’t have any more information on this at this time.
Ok, thanks for the update Dave!
Sorry to drag up such an old post, but is it possible to apply this for all devices, but also set a bitrate of say 10Mbps?
I’m sure it is and my regex is just off but i’m tearing my hair out now!
Yea. What that script does is drop the paramater from the URL so it doesn’t even get passed to the server.
It’s already set for all devices with this:
if ($http_user_agent ~ (^|.*)) { set $tempargs ${args}-TEMP; }
Change the two similar lines to something like this:
if ($tempargs ~ (^|.*)&maxVideoBitrate=(\d+)(.*)-TEMP) { set $tempargs $1&maxVideoBitrate=10000000$3-TEMP; }
if ($tempargs ~ (^|.*)&videoBitrate=(\d+)(.*)-TEMP) { set $tempargs $1&videoBitrate=10000000$3-TEMP; }
Perfect, thanks!
I’m so grateful for the light at the end of the tunnel you’ve given us, though I am curious if you’re able to share whether the rollout is going as expected or otherwise? This Netflix password sharing policy update has my server slammed with 4Mbps 720p transcodes. ![]()
Everything that we’ve seen so far shows that this is increasing quality, and decreasing buffering time, which is exactly what we were hoping to get. Users should be direct playing as much as possible.
Got linked here from another thread, replying so I know what’s going on as I to have this exact problem and hope to be able to push quality settings to all clients of my server as well. Even with a well powered server having a bunch of remote clients at 720p/2MB means a LOT of unnecessary transcoding and a lot of unnecessary buffering and low quality.
Hey man thx for this, but I have an error with this:
nginx: [emerg] invalid condition “$http_x_plex_device_name” in /etc/nginx/templates/plex_force_bitrate.include:2
Any idea?
Need to see the whole configuration for nginx otherwise I have no clue. It needs to be in a specific place.
@sixones @DaveBinM This is huge; thank you for your work on this (and anyone else who was involved)!
So grateful that this was ultimately seen as an actual solution. It’s a really big deal for both the introductory and ongoing experiences on both the client and operator ends. Thanks again!
Please move this conversation to another thread, as its not directly relevant to the feature request and ongoing work related to it.
Seems pretty relevant to me considering this thread is 4 years old and one single client with an extremely small subset of users can even use this “ongoing work”.
Sad we have to hack around one of the biggest threads on this forum.
Now I feel like Linus.
Don’t anybody go asking me questions related to the work-around now. I won’t help you.
Ok fine @DaveBinM, let’s come back to the original topic: can you give us a status of where you are to make stream quality to the highest possible value so servers can stop transcoding and overheating for nothing? Thx
We already have work out on Android TV, as discussed further up. It will come to other platforms in future, though I won’t be giving specific dates or timeframes.
Is this new feature officially out for all Android clients? And is it something that can be seen in the Plex app settings?
It’s available for all Android TV clients, and is enabled by default. You can see it by looking at the Quality Suggestions option in the app settings.