What number to use for bitrate limit with fiber internet?

[gene0915 42]

I recently upgraded to AT&T 1 gig symmetrical internet and in the 'Internet streaming bitrate limit (Mbps):' box, should I enter 900Mbps or '0' for unlimited?

 

[Luke 42079]

HI, I would suggest leaving it at the default unless you have a specific reason to change it. Please let us know if this helps. Thanks.

[gene0915 42]

1 hour ago, Luke said:

HI, I would suggest leaving it at the default unless you have a specific reason to change it. Please let us know if this helps. Thanks.

What sorta kinda sparked this thread was that after getting up and running with AT&T, I noticed that live TV streaming wasn't working and I was poking around to try and figure out why. Turns out, it DOES work but only for some channels. (I was just happening to pick the bad ones apparently

Example..... if I use Emby (browser on the Emby server) to try and live stream a local NBC HD channel (4.1), I get this error:

No compatible streams are currently available. Please try again later or contact your system administrator for details.

If I launch my Channels DVR software on this same PC (browser based) and tune into 4.1, it works fine so I know the problem isn't the HDHR box.

Some TV channels are working fine in Emby and others fail with that 'no compatible streams' error.

Uploading a few log files for your review.

Thanks Luke!

embyserver.txtffmpeg-transcode-46b3ea7a-9dfc-4117-9465-6afd1845cae8_1.txtffmpeg-transcode-9274da39-a01a-471a-b379-a11ff64cb307_1.txtffmpeg-transcode-9274da39-a01a-471a-b379-a11ff64cb307_1(1).txtffmpeg-transcode-76363be5-c4e5-4383-8f5f-06409b38b432_1.txtffmpeg-transcode-76363be5-c4e5-4383-8f5f-06409b38b432_1(1).txtffmpeg-transcode-b1f2fc9a-7a70-4612-bf75-fe8e801c51da_1.txtffmpeg-transcode-b1f2fc9a-7a70-4612-bf75-fe8e801c51da_1(1).txtffmpeg-transcode-c2f17947-f61c-41cb-a89c-f43d03b33557_1.txtffmpeg-transcode-c660d08c-943b-488e-be3c-7d2b39e4e9f6_1.txt

[Carlo 4561]

The transcoder does not like your streams.

14:05:59.382 [mpegts @ 0x1849840] PES packet size mismatch
14:05:59.383 [mpegts @ 0x1849840] probed stream 1 failed
14:05:59.386 [mp3float @ 0x18502c0] Header missing
    Last message repeated 6 times
14:05:59.386 [mpegts @ 0x1849840] decoding for stream 0 failed
14:05:59.386 [mpegts @ 0x1849840] Could not find codec parameters for stream 0 (Audio: mp3 (mp3float), 0 channels, fltp): unspecified frame size
Consider increasing the value for the 'analyzeduration' and 'probesize' options
14:05:59.386 [mpegts @ 0x1849840] Could not find codec parameters for stream 1 (Unknown: none): unknown codec
Consider increasing the value for the 'analyzeduration' and 'probesize' options
14:05:59.386 Input #0, mpegts, from 'http://127.0.0.1:8096/LiveTv/LiveStreamFiles/06396420ffa2425b96f75f221e26fd3e/stream.ts':
14:05:59.386   Duration: N/A, start: 90573.099033, bitrate: N/A
14:05:59.386     Stream #0:0[0x31]: Audio: mp3, 0 channels, fltp, Start-Time 90573.593s
14:05:59.386     Stream #0:1[0x35]: Unknown: none, Start-Time 90573.099s
14:05:59.386 Stream specifier 'v:0' in filtergraph description [v:0]deinterlace_vaapi@f1[f1_out0] matches no streams.

That format is pretty strange.  You don't see audio as the first stream often at all.
But it's choking on the deinterlace_vaapi filter.

As a quick experiment could you try something for me? Go to the transcode menu and switch the first drop down to Advanced.
Now switch the order so QuickSync is about the Vaapi entry.
Do that for every decoder and encoder.
Try playing your TV channels again.
You can switch the order back after the test.

@softworkz

[gene0915 42]

1 hour ago, cayars said:

The transcoder does not like your streams.

14:05:59.382 [mpegts @ 0x1849840] PES packet size mismatch
14:05:59.383 [mpegts @ 0x1849840] probed stream 1 failed
14:05:59.386 [mp3float @ 0x18502c0] Header missing
    Last message repeated 6 times
14:05:59.386 [mpegts @ 0x1849840] decoding for stream 0 failed
14:05:59.386 [mpegts @ 0x1849840] Could not find codec parameters for stream 0 (Audio: mp3 (mp3float), 0 channels, fltp): unspecified frame size
Consider increasing the value for the 'analyzeduration' and 'probesize' options
14:05:59.386 [mpegts @ 0x1849840] Could not find codec parameters for stream 1 (Unknown: none): unknown codec
Consider increasing the value for the 'analyzeduration' and 'probesize' options
14:05:59.386 Input #0, mpegts, from 'http://127.0.0.1:8096/LiveTv/LiveStreamFiles/06396420ffa2425b96f75f221e26fd3e/stream.ts':
14:05:59.386   Duration: N/A, start: 90573.099033, bitrate: N/A
14:05:59.386     Stream #0:0[0x31]: Audio: mp3, 0 channels, fltp, Start-Time 90573.593s
14:05:59.386     Stream #0:1[0x35]: Unknown: none, Start-Time 90573.099s
14:05:59.386 Stream specifier 'v:0' in filtergraph description [v:0]deinterlace_vaapi@f1[f1_out0] matches no streams.

That format is pretty strange.  You don't see audio as the first stream often at all.
But it's choking on the deinterlace_vaapi filter.

As a quick experiment could you try something for me? Go to the transcode menu and switch the first drop down to Advanced.
Now switch the order so QuickSync is about the Vaapi entry.
Do that for every decoder and encoder.
Try playing your TV channels again.
You can switch the order back after the test.

@softworkz

That fixed it, thanks!

Pros/cons for leaving things like that? (QuickSync above VAAPI)

Attaching logs just in case you wanted to see the difference.

embyserver.txtffmpeg-transcode-5b610f28-cc8f-42f2-9ccf-c375a75d639a_1.txt

[Carlo 4561]

Pretty much which ever one works best for you or fastest.
I think the choice is easy for you.

What I've found on both my i7 and Synology that have both choices is the QuickSync being faster.
However Softworkz choose VAAPI as the default and it escapes me now why (but he mentioned it before).

We can get @softworkz to take a look at it but for now you have a solution.

[softworkz 5067]

On Linux, it had always been required to install Intel Media SDK components manually to get QuickSync working. In turn we hadn't got much feedback on this.
Since a few months only, we are including the Media SDK components as part of the Emby Server installation, and now everybody can get QuickSync easily.

Once we are confident enough about it to work fine, I'm inclined to change the default to QSV in fact as it provides better performance and quality.

[gene0915 42]

2 hours ago, cayars said:

Pretty much which ever one works best for you or fastest.
I think the choice is easy for you.

What I've found on both my i7 and Synology that have both choices is the QuickSync being faster.
However Softworkz choose VAAPI as the default and it escapes me now why (but he mentioned it before).

We can get @softworkz to take a look at it but for now you have a solution.

 

1 hour ago, softworkz said:

On Linux, it had always been required to install Intel Media SDK components manually to get QuickSync working. In turn we hadn't got much feedback on this.
Since a few months only, we are including the Media SDK components as part of the Emby Server installation, and now everybody can get QuickSync easily.

Once we are confident enough about it to work fine, I'm inclined to change the default to QSV in fact as it provides better performance and quality.

Yes, since it's working now, I'll leave it "as is". Thank you both (and Luke) for the help!

[Carlo 4561]

6 hours ago, softworkz said:

On Linux, it had always been required to install Intel Media SDK components manually to get QuickSync working. In turn we hadn't got much feedback on this.
Since a few months only, we are including the Media SDK components as part of the Emby Server installation, and now everybody can get QuickSync easily.

Once we are confident enough about it to work fine, I'm inclined to change the default to QSV in fact as it provides better performance and quality.

Thanks, I knew you mentioned it or told me before but I couldn't remember. That's good news.