Emby not respecting mbps limit over cellular data?

[Luke 42078]

4 hours ago, Jcheinaman said:

 

As promised in my post directly above, I ran this a few times and I was able to replicate the issue. I included a few pictures from the app. I also included the log. I used my iPhone for these tests, but the app does the same thing when connected with my iPad. Being that this appears to be linked to the app, I'm not sure if the server logs will necessarily help here or not. Call me crazy, but something is definitely out of sorts here. Please let me know if you find anything. Thanks!

 

Direct play from my local network. Proper playback as expected:

transcoding, but @ max bitrate on cellular data. I have my network stream limit set to 5mbps. This is when the server dashboard simply states "Transcoding" and has no transcode reason or stats displayed below it. If I was previously connected to the app via a local wifi connection and I don't first manually log out and back into the server, this is the result below. It's almost like the server gets confused? It transcodes, but doesn't limit the bitrate over the remote connection. Stats for nerds doesn't even show the transcode progress. It's almost like it's just saying that the file is transcoding for some reason, but not actually transcoding and simply playing directly:

Transcoding on cellular data properly after I log out and back into the server via the iOS app:

 

embyserver.txt 551.78 kB · 0 downloads

There is a lot of playback in this log. What time did you do this?

[Jcheinaman 19]

2 hours ago, Luke said:

There is a lot of playback in this log. What time did you do this?

I did this this morning around 8am Eastern. If you need me to do anything else, please let me know and I’ll be glad to assist. I was intentionally playing back to try and recreate the issue and hoping that you could see that in the log. 

[Luke 42078]

Actually I believe in that 8am example the bitrate was respected in all cases. What gave you the impression that it wasn't? The transcoding stats usually take about 10 seconds to appear when you start playing. When you didn't see them, that may have given you some kind of false impression that something wrong was happening.

But in both cases the server requested a video bitrate of around 4.6 mbps from the transcoder, and then you add the 384k bitrate for the audio, and that puts you right at 5 mbps, which is exactly what you've configured.

Now I do see in your screenshot it says 5.4 mbps, hard to say where that extra .4 is coming from. We'd have to see the ffmpeg transcoding log.