Bitrate problem

[Bagul 182]

Hey,

Well, I've seen several threads that talk about the subject but none of them contains a concrete answer.

When playing video on the local network I have no problem.
But when I play a video on a remote network depending on the client used the bitrate does not match the internet speed.

When I go to see the logs there is a bitrate limit that is set up except that I did not set one.

Depending on the browser used the quality is not the same (eg: Firefox => 720p 1.5mbps | Chrome => 1080p 6mbps).

 

Firefox:

Chrome:

I thought it was due to my reverse proxy but when I play a video without reverse proxy by opening the port 8096|8920 on my box the problem persists.

 

I have of course a FFTH network. During my tests I did not have any user using my server. I didn't try with the beta version because I don't necessarily want the beta to be accessible for my users.

I saw on a thread giving the solution to put 0.0.0.0/0 as local network in the settings of Emby but it does not suit me because the maximum bitrate is used even when the internet speed is not good.

 

My user settings:

 

My network settings:

But for example the ios application does not have this problem. But the AppleTV application has this problem.
The AndroidTV application doesn't have this problem but all browsers have the problem.

And when the internet connection is not good the bitrate in auto is always a little bit above the internet connection.

 

I don't want to put a fixed value for the quality, my users and I don't necessarily watch in front of our TV and for example in public transport the connection is not necessarily the same everywhere.

 

If the problem is solved in the beta I'm sorry I made this thread.

embyserver.txtffmpeg-transcode-c87d3498-bab4-4569-a795-91eefad4f356_1.txtffmpeg-transcode-6334f201-b90e-4a1f-b27c-dda9f0e496ef_1.txt

[ebr 16185]

2 hours ago, Bagul said:

The AndroidTV application doesn't have this problem

You get reasonable values when using this application?

[Bagul 182]

It's more of an observation. My users using the AndroidTV application can play a video in direct playback when they are in 'auto' then I didn't notice any bitrate problem on this one.

[Bagul 182]

Hey @ebr,

I just tried with the beta and the problem persists.

I also found this capture on a thread showing the bitrate value hardcoded. This would explain the problem?

So when I look at it I don't understand why at this place my bitrate is 1500000

Edited April 7, 2022 by Bagul

[Luke 42080]

Hi, if you're finding auto too conservative then try setting it to the value that you need.

[Bagul 182]

Hey,
My problem is not that the auto quality is too conservative.
The problem comes from the fact that when playing video in auto, whether with my browser or other, the quality found by the auto is not good. 1.5mbps of bitrate for a ffth connection is weird.

[Bagul 182]

Ok, So I solved my problem partially by rewriting the 'detectBitrateWithEndpointInfo' function in the 'dashboard-ui/module/emby-apiclient/apiclient.js' file the value I find is much closer to reality.

 

without bandwigth limit:

 

With bandwidth limit:

Edited April 11, 2022 by Bagul

[RanmaCanada 496]

As Luke said, sadly auto is just way too conservative.  What you need to do is figure out what your connection is like with each user and go from there.  It's a PITA but it let's you know who has an ISP that is throttling them, and who doesn't.  I have a thread where a person is trying to watch the same video on 2 different devices in the same house, and the apple tv capped them at 3mpbs, while their ipad pro did a direct play.  Luke gave me the same answer.

[Bagul 182]

4 hours ago, RanmaCanada said:

As Luke said, sadly auto is just way too conservative.  What you need to do is figure out what your connection is like with each user and go from there.  It's a PITA but it let's you know who has an ISP that is throttling them, and who doesn't.  I have a thread where a person is trying to watch the same video on 2 different devices in the same house, and the apple tv capped them at 3mpbs, while their ipad pro did a direct play.  Luke gave me the same answer.

I understand that the value is conservative.
But I always have the same values on the web version whether the connection is very bad or not outside my LAN. For the Apple TV I have also noticed a problem I have also reported in my initial post.
But in my previous post I was talking about the web version. By debugging the code I rewrote the function to give the bitrate in auto and it works so I will leave it like that. But I didn't start this thread for fun. 3mpbs for an Apple TV that can handle 4K... there is a problem. On the other hand on my LAN (I use an Apple TV) or on apps like the iOS or Android TV app on my WAN I have no problem.
 

And like I said I wouldn't put a fixed value. Some of my users are computer neophytes and I won't bother them with numbers they don't understand. I ask them to use the applications as much as possible to avoid any problems.
I just wanted to report the problem so it could be fixed later if there was indeed a problem but I think this thread will be quickly forgotten based on the responses:
"Put a fixed value"
"Auto is conservative"

 

[RanmaCanada 496]

I agree.  Most of my users are completely clueless about tech, and it's frustrating when they complain that the stuff they are watching is pixelated to garbage.  I've moved as many as I can off Apple devices, and off of ISP's that throttle their connections, but not all have wanted to move or replace their device.  I tell them, "it is what it is".