Jump to content
maxxoverclocker

Bitrate reported on server dashboard can't possible be accurate?

Recommended Posts

maxxoverclocker

Hi!

 

After the update from 4.3.0.30 to 4.3.1, I've noticed that in the server dashboard the bitrates for transcoded media are wildly inaccurate, sometimes 5-10x higher than the actual source media:

 

5e1e0ad3b27ee_Capture2.png

 

The source media for this was 7,867 kbps as reported on the media detail page:

  • Title1080p H264
  • CodecH264
  • AVCYes
  • ProfileHigh
  • Level41
  • Bitrate7,867 kbps
  • Color spacebt709
  • Bit depth8 bit
  • Pixel formatyuv420p
  • Ref frames1
  • NAL4

I've attached the logs for the above.

 

I've also seen it report absurdly low bitrates, like 45 Kbps when they're actually streaming at 3Mbps.

embyserver-1.txt

Edited by maxxoverclocker

Share this post


Link to post
Share on other sites
Luke

Please attach the ffmpeg log. Thanks.

Share this post


Link to post
Share on other sites
Luke

No that's actually not the same at all. In this case the app requested 2 mbps but the actual result is being reported as something very different.

Share this post


Link to post
Share on other sites
maxxoverclocker

No that's actually not the same at all. In this case the app requested 2 mbps but the actual result is being reported as something very different.

Thanks Luke! Very strange.

Share this post


Link to post
Share on other sites
Happy2Play

No that's actually not the same at all. In this case the app requested 2 mbps but the actual result is being reported as something very different.

I guess I am confused as a 2Mb limit and 2Mb transcode, exact same logging as other topic.  UI showing VTT rate about 76Mbps.

Playbackinfo
&VideoBitrate=1616000&AudioBitrate=384000

File Bitrate
"Bitrate":7867582

Transcode
-maxrate 1616000 -bufsize 3232000

22:10:21.235 SegmentComplete=video:1 Index=711 Start=1488.069917 End=1490.071917 Duration=2.002000 offset_pts=0 start_pts=1488069917 Frames=47 filename=0fbcd8816bbe289656fea5a78ddb14aa_s15711.vtt
22:10:21.235 frame=20248 fps= 24 q=-1.0 Lq=-1.0 q=-1.0 q=-1.0 q=-1.0 q=-1.0 q=-1.0 q=-1.0 q=-1.0 q=-1.0 q=-1.0 q=-1.0 q=-1.0 q=-1.0 q=-1.0 size=13932613kB time=00:24:50.11 bitrate=76595.4kbits/s throttle=off speed= 1.8x

Share this post


Link to post
Share on other sites
seanbuff

No that's actually not the same at all. In this case the app requested 2 mbps but the actual result is being reported as something very different.

 

So isn't that exactly the same as in my case? My clients had a limit of 6Mbps, and the logs indicate that they were indeed pulling 6Mbps - yet the dashboard was reporting something completely different.

 

@@softworkz summed up the issue perfectly. Obviously caused by a recent update, as the OP originally indicated.

Share this post


Link to post
Share on other sites
softworkz

We're working on it! Thanks for reporting.

  • Like 1

Share this post


Link to post
Share on other sites
Luke

The output bandwidth has been corrected for the upcoming 4.4 release. Thanks.

Share this post


Link to post
Share on other sites
maxxoverclocker

The output bandwidth has been corrected for the upcoming 4.4 release. Thanks.

Thanks again Luke! This is good to hear because I've noticed that even though I have a per-stream bandwidth limit of 8Mbit/s, some clients are pulling 25Mbit/s (source bitrate) even though the clients are external. Completely depends on the source content though. I'll wait for the 4.4 stable release and see if that does the trick!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...