Throttling isn't throttling.

[zer0ish 12]

Hi,

I've been using Emby for a few years and noticed this for a while, but now that I'm getting back into gaming, it's starting to affect bandwidth since it's pulling more data then it should be, or needs to be pulled.
As you can see from the screenshot, there is 37 minutes of buffering when the user isn't even close to that point.
I have "Enable throttling" set to avoid using more resources then needed but for some reason there isn't any throttling going on with this.
If the transcode is being done as seen in the screenshot the throttle doesn't apply. 
The second screenshot is 7ish minutes later and the buffer hasn't been throttled.

I'm looking at a live feed of my pfSense traffic graph and it keeps spiking even beyond what I've allocated to the user.
I've set it so all users that aren't on the Local network are limited to 4Mbps, and this isn't the case for people who have the bellow transcoding.
This user is somehow pulling 15-30 Mbps when they should only be getting a max of 4Mbps and it should be throttling after 2 minutes of buffering.
I know the screenshot shows 1.9Mbps, but this isn't the case when I look at the data going out of my network with everything else turned off(for troubleshooting).

At the very least, it should still be getting throttled at 2 minutes of buffer to avoid using my upload when the user isn't at the point yet.

Please let me know what log file I should attach and I will. 

Any info on a solution would be great.

Thanks,
 

[Happy2Play 9783]

Devs may need to see the ffmpeg log, but I know Emby hasn't throttled for Chromecast in quite awhile as I believe the log reports "Latest request position unknown" so throttling can not happen as it does not know where it is.

Edited October 1, 2021 by Happy2Play

[Luke 42083]

HI there, yes let's look at an example. Thanks.

[Happy2Play 9783]

18 minutes ago, Luke said:

HI there, yes let's look at an example. Thanks.

Does this not circle back to this topic?

https://emby.media/community/index.php?/topic/91295-transcode-throttle-appears-to-be-broken/&do=findComment&comment=951429

But yes we would need to see the ffmpeg log.

[zer0ish 12]

Hello,

Attached is the 2 most recent ffmpeg log files.
Hope this helps. But if as mentioned this isn't something that can be fixed we can close this.

ffmpeg-transcode-Sept 30 0914PM.txt ffmpeg-transcode-Sept 30 0851PM.txt

[Luke 42083]

Hi, we're looking into this. Thanks for reporting.

[Happy2Play 9783]

While the devs look into this, can you test changing the throttle method to see if it makes a difference.

path will be C:\Users\zer0ish.apextriangle\AppData\Roaming\Emby-Server\programdata\config\encoding.xml

Edited November 1, 2021 by Happy2Play
added path

[softworkz 5072]

This time throttling was in fact broken due to the latest ffmpeg reporting the time in log output in a different way.

It's already fixed for the upcoming beta.

Thanks for reporting!

[zer0ish 12]

9 hours ago, softworkz said:

This time throttling was in fact broken due to the latest ffmpeg reporting the time in log output in a different way.

It's already fixed for the upcoming beta.

Thanks for reporting!

Ok great, good to know. 
So there isn't anything I have to do, just wait for the next release?

[Carlo 4561]

Yes, just wait for the new release to fix this for you.