Jump to content

Wrong Bitrate on Live TV streamed by TBS encoder


vaiuba
 Share

Recommended Posts

vaiuba

Hello,

I've a TBS encoder with 2 Streams:

1) 1080p H265 7.000 kb/s bitrate

2) 720p H265 2.000 kb/s bitrate

If I connect to TBS using VLC I can see all the time the current bitrate corresponds to what set in TBS Encoder.

 

When I open Live TV connected to this live stream with any device using Emby app, I can see different bitrate:

1) 15Mbits

2) 6Mbits

This causes troubles when watching in a limit bandwith situation, where I set up a max 5MB/s in the Emby app option. In these cases Emby force transcoding on stream 2), which is bad.

Is there any chance to force Emby to read correct bitrate?

Thank you

 

Example2 from iPad.jpg

VLC.png

TBS Config.png

Link to comment
Share on other sites

It could be the client you're using can't play back the container or video codec so it needs to transcode.  In that case it will need transcode the video to h.264 which will require more bits.

May I suggest a quick test.  For the first test remove the sub stream encoding and just use the main stream.

Try that and see if it makes a difference with only 1 stream being generated.

The second test you can try is to switch the profile being used from H.265 to H.264.

Let us know what you get after trying both of these.

 

Link to comment
Share on other sites

vaiuba

Thank you for your reply.

I already tried to change encode profile, but it is the same.

If I put the maximum bandwith to a value > 6Mbps (10Mbit for example) no transcode is done. This happen just when I set a value that is lower than read bitrate (which is unfortunately wrong).

How Emby calculate this value? If I ffprobe the source stream, i can see on bit_rate field the value N/A (there is now way to explicit set a value in the stream property).

thank you

Link to comment
Share on other sites

Did you try the first thing I mentioned removing the sub stream?

What does the client show when playing back with the H.264 profile?

Link to comment
Share on other sites

vaiuba

Switched to h264 and disabled substream.

Same thing. Main stream is read by Emby with a 15Mbps bitrate.

attached TBS configuration and stats for nerds

B1B15DEF-7B0B-454A-A18C-4F758B0350FB.jpeg

EF7101E7-D748-4ABE-B77C-81F6C2C891EC.jpeg

Link to comment
Share on other sites

Thanks for trying that.  Your results are interesting.

Do you get different results with different Emby Clients?

If you do a small 5 minute recording and then play that back, what bitrate does it show?

Link to comment
Share on other sites

vaiuba

Sorry for delay, I had some troubles adding fake EPG in order to enable recording.

This is current bitrate for stream 2)

 

Any Ideas?

Capture.PNG

Link to comment
Share on other sites

OK so that is in agreement with Emby.  Have you tried this with the primary stream?

Link to comment
Share on other sites

pünktchen

Try to change the encoder setting from variable to constant bitrate. I guess ffmpeg cannot read the overall variable bitrate as long as the file/stream has not finished and so Emby will just use some default values depending on the resolution.

Edited by pünktchen
Link to comment
Share on other sites

vaiuba

I already tried to change all parameters on TBS Encoder, restarted Emby everytime, but nothing changes.

Link to comment
Share on other sites

pünktchen

But my other assumption still stands:

3 hours ago, pünktchen said:

I guess ffmpeg cannot read the overall variable bitrate as long as the file/stream has not finished and so Emby will just use some default values depending on the resolution.

I have exerienced similar recently with Handbrake and the Quicksync encoder. Even MediaInfo did not show any bitrate until the encoding has finished.

Link to comment
Share on other sites

Maybe, using constant bit rate for the encode would help.

Link to comment
Share on other sites

vaiuba

I set CBR on TBS Encoder, restarted Emby, but bitrate is always read as 15 Mbits for 1) and 6Mbits for 2)

ffprobe still reads bit_rate = N/A

Edited by vaiuba
Link to comment
Share on other sites

It sounds like the encoder is fully writing header information so Emby doesn't have a way to accurately determine the bitrate and has to guess.  If it does that it will opt on the side of safety and assume a higher bitrate.

Which specific encoder are you using?

Link to comment
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
 Share

×
×
  • Create New...