Bug Report High bitrate spike with CBR?

[v6ooo]

Twitch was complaining about the quality was just Acceptable and when I had a look I saw this.

The broadcast is not set to constant bitrate (CBR). [Current average: 1831 kbps, current max: 2784.0 kbps]

The thing I'm worried about is if Twitch detects this and thinks it's only Acceptable quality then people on mobile devices won't be able to watch it.

My bitrate is CBR 2000, resolution 720p & 30fps

I had 3 scenes running during this. "intro", game screen (had to change game capture to correct window), and "outro".


Regards,
v6

 

[dodgepong]

Twitch transcodes your stream to a more mobile-friendly HLS stream, so you don't have to worry about mobile quality.

As for the bit rate spiking, are you using a custom buffer?

 

[FerretBomb]

Actually Dodgepong, the 'new requirements' mean that non-partnered streams will NOT be visible/transcoded to mobile/console if they are only at the 'Acceptable' level; only partnered streams will.

I've had to drop my keyframe interval to 1 (2 results in Twitch saying it's at 2.44 seconds) and occasionally try a few times; even with CBR set, it still pops up the same error that v6000 is receiving. It's on Twitch's end, their detection code is kind of crap at the moment, and up to us to work around it.

http://help.twitch.tv/customer/portal/a ... quirements

 

[dodgepong]

Ah, I was confused as to what he meant...I thought he was referring to picture quality, not "settings" quality...Twitch should really use a different term for that.

 

[Krazy]

Actually Dodgepong, the 'new requirements' mean that non-partnered streams will NOT be visible/transcoded to mobile/console if they are only at the 'Acceptable' level; only partnered streams will.

I've had to drop my keyframe interval to 1 (2 results in Twitch saying it's at 2.44 seconds) and occasionally try a few times; even with CBR set, it still pops up the same error that v6000 is receiving. It's on Twitch's end, their detection code is kind of crap at the moment, and up to us to work around it.

http://help.twitch.tv/customer/portal/a ... quirements

Holy crap...1 second keyframe interval must be seriously doing bad things to your picture quality...

Ugh, I hate that they are trying to force a stupid keyframe interval.

 

[Lain]

Ferretbomb - I'm guessing the only reason twitch was saying it was at 2.44 seconds was because the app was set to VFR (variable framerate) instead of CFR (constant framrate). If you turn on CFR in advanced it should fix that issue.