Question / Help New Twitch.TV "Stream Configuration Quality: Incompatible" ?

[Emiya Shirou]

Re: New Twitch.TV "Stream Configuration Quality: Incompatibl

No, you set your KEYINT to double your frame rate. If you're streaming at 30fps, set your keyint to 60. You don't need to change your frame rate.

So what is this KEYINT and why it has to be different now?
Also I got very very important question HOW MUCH will this impact my streaming on my internet and PC? because if it is gonna start lagin my game or stream I will be angry as hell...

Hardware:
CPU Type: DualCore Intel Pentium E2160, 3200 MHz
Motherboard: Gigabyte GA-P31-DS3L
System Memory: 2048 MB (DDR2-1066MHz)
Video Adapter: NVIDIA GeForce GTS 450 (1024 MB GDDR5)
Audio Adapter: Realtek ALC888 @ Intel 82801GB ICH7 - High Definition Audio Controller [A-1]
Network Adapter: Realtek PCIe GBE Family Controller

Internet Upload speed: 1.07 Mbps

If your stream is entertaining and you have good content, it will be fine. If a stream is entertaining but low quality, I usually won't turn it off (unless it is egregiously low), but I often turn off high-quality streams that are boring.

Well people are entertained by what I provide to them but I only stream at 360p... I already notice that some people come, see 360p and just run away without saying anything... So yeah, Good Job twitch, if the video quality will be indeed lower then there is not freaking chance I am changing that KEYINT unless forced to, anyway I am still waiting for that explanation to my questions that is in this post you are reading right now.

 

[Krazy]

Re: New Twitch.TV "Stream Configuration Quality: Incompatibl

Setting keyint of 2 seconds should have very very very little impact on your stream. It should only affect extremely low bitrate streams. You might notice a tad more pixelation than before, but it's not going to suddenly prevent you from streaming anymore.

People really need to calm down about this change, there's almost nothing that is going to be changing for 99.9% of streamers except for the keyint setting.

I think some people have it in their heads now that you have to set your audio bitrate to 160kbps or something, but that's just the MAX you are allowed now. If you want to stream at 128, 96, or even lower audio bitrate, you are still going to be able to. You just won't be able to go over 160kbps anymore. That's all.

 

[dodgepong]

Re: New Twitch.TV "Stream Configuration Quality: Incompatibl

Keyint is short for keyframe interval. A keyframe is a full-frame image, and video compression works by sending only the changes from frame to frame, rather than each frame in full. So x264 only inserts keyframes every so often to make sure the compression doesn't make it look too far off from the original image. You might have tuned into some streams and it looked all distorted and green for a few seconds, and then it corrected itself...that's because you missed the first keyframe, and got another one to correct it.

By default, x264 sends keyframes every 250 frames or so (or sooner if it decides it needs to). For a 30fps stream, that works out to ~8.3 seconds between each keyframe, assuming the maximum amount of time is used each time. Twitch needs that changed to 2 seconds, or 60 frames between keyframes for a 30fps stream (keyint=60).

The consequence of sending more keyframes is that more bandwidth will be spent on full-frame images that would otherwise have been spent improving the quality of other frames. So quality will slightly decrease as a result of setting keyint to 2 seconds. I don't think it's anything to worry about, though.

 

[Emiya Shirou]

Re: New Twitch.TV "Stream Configuration Quality: Incompatibl

Keyint is short for keyframe interval. A keyframe is a full-frame image, and video compression works by sending only the changes from frame to frame, rather than each frame in full. So x264 only inserts keyframes every so often to make sure the compression doesn't make it look too far off from the original image. You might have tuned into some streams and it looked all distorted and green for a few seconds, and then it corrected itself...that's because you missed the first keyframe, and got another one to correct it.

By default, x264 sends keyframes every 250 frames or so (or sooner if it decides it needs to). For a 30fps stream, that works out to ~8.3 seconds between each keyframe, assuming the maximum amount of time is used each time. Twitch needs that changed to 2 seconds, or 60 frames between keyframes for a 30fps stream (keyint=60).

The consequence of sending more keyframes is that more bandwidth will be spent on full-frame images that would otherwise have been spent improving the quality of other frames. So quality will slightly decrease as a result of setting keyint to 2 seconds. I don't think it's anything to worry about, though.

Thanks for your explanation, now I understand and I do worry... I want to have good image quality in that 360p so I assume when they will force this setting I will be bitching and being angry all the time at my stream quality... this kind of things discourage me a lot... I only probably will stop being angry when I see that people watching me don't give a shit about image being pixelated as hell instead of smooth as it is right now. (but probably then, it will still be bugging me as hell).

 

[Krazy]

Re: New Twitch.TV "Stream Configuration Quality: Incompatibl

It's really very doubtful it will noticeably impact your stream quality.

 

[Emiya Shirou]

Re: New Twitch.TV "Stream Configuration Quality: Incompatibl

It's really very doubtful it will noticeably impact your stream quality.

Let's hope that it will not... but looking at my max 800 bitrate with VBS... I doubt that it won't. We will see.

 

[Kharay]

Re: New Twitch.TV "Stream Configuration Quality: Incompatibl

I think some people have it in their heads now that you have to set your audio bitrate to 160kbps or something

For a while today that really was the only way I could get an Excellent rating. Now, obviously this is part of Twitch's development process of this requirement/profiling system of theirs but still, confusion is to be expected if the expected or intended result is nowhere near the actual result.