Server Version#: Always upgraded to latest Current: (Version: 1.24.2.4973-2b1b51db9)
Player Version#: Unknown/Not in my control
Hello!
I’ve set the default bitrate to 3mbps for remote streams, but they seem to immediately negotiate down to 2mbps and stay there unless the viewer manually overrides. There’s plenty of bandwidth on both ends (gig/gig here, plenty down on the remote side) so 3mbps is not a challenge. However the first negotiation limits it down and to ugly results.
How can I help the software prefer / take affinity to 3mbps and push for that instead?
You cannot set a default bandwidth for remote streams on the server side.
You can set a remote stream bandwidth limit – so basically if you set that to 3 Mbps, clients can pick their own preferred quality, however if their selection exceeds your remote stream bandwidth limit, their stream will max at that bandwidth.
Keep in mind the client app will apply that limit for the expected maximum bitrate which can be significantly above the average bitrate. So going with an average 2 Mbps isn’t unreasonable if your media has a significantly higher max. bitrate.
Right, I wasn’t finding any way to set a preferred bitrate on the server side.
The problem is just it’s super inconvenient / cumbersome to my friends who share it to dig in and find that setting and decypher what quality means what bitrate, etc. I’m trying to make this as easy as possible (Think: Grandpa-easy)
I guess I was hoping if there was a manual tweak in the bitrate negotiation I could play with outside of the web-UI.
I have the max bitrate at 12mbps I believe, so headroom isn’t the problem. Speedtests across the country to varied ISPs regularly give me 500mbps upload+ so it’s not a question of congestion on my end.
I dunno’. Just kind-of wish I could nudge that 2mbps which people typically always seem to end up at to 3mbps for the better 720p experience.
I am not sure I fully understand the last qualifier about the source bitrate, these are all blu-ray rips I’ve personally MakeMKV’d to a Synology NAS. No transcoding/handbrake or anything just the main title .MKVs, so average is like 23GB per title. Does that make it more likely for users to end up streaming at a lower end-bitrate?
Nice! Ok, well, It’s got my vote. Since I’ve been so diligent in the source quality it feels sad to me to watch the client player unnecessarily kneecap it’s bitrate!
I suppose it’s not as simple as that.
Keep in mind some users might set the remote quality on purpose, e.g. if you want to stream from a mobile network with a limited data plan, if you have a poor internet plan or need capacity for other means (e.g. not to block the rest of the family from watching decent quality Netflix).
Oh of course, I’m purely talking about what the default settles to before they make any choices whatsoever. It just seems to have an affinity to 2mbps, no matter who the client is or where they are located. My friends dont really have the technical desire to go in and set it either, so if i could influence the default, the experience would be better.
I know these cases are to people with good internet (cable at least), whether it’s congested or not is not in my visibility. But it’d be nice to nudge the algorithm a little.
In the mean time, I did find a field in the server settings for max server upload bandwidth, and I just set that up to like 100mbit now instead of i had it mathed out much lower clients X bitrate target. Maybe that will help?
