ZergShadow
Member
I had tried run stream in 8000 and it works. What cons?
twitch 8000 bitrate
- Thread starter ZergShadow
- Start date
ZergShadow
Member
How much can i rise for twitch?
ZergShadow
Member
But obs allows 320 for audio and I use this. Seems now i go your settings. Tnx man. But how you found this numbers?
https://help.twitch.tv/s/article/broadcast-guidelines?language=en_US in this article they say 128-320 for audio.
if i go 128 audio so i can go 8282 video?
Last edited:
yes pretty much, twitch max is 8500kbit/s total bitrate and they turn off the stream if you go higher, so you want to stay as close to 8500 kbit/s as possible but still have some wiggle room because the bitrate fluctuates because no encoder does clean CBR
ZergShadow
Member
Seems you was right but now this is 8250 320 and can go further with video bitrate if you go less then 128 audio.
I wouldn't recommend going over Twitch's own recommendations, which would be bitrate 6000 and audio 128 kbps (max 320kbps).
help.twitch.tv
Dunno how and if they enforce it, but higher bitrates are usually only allowed for affiliates and partners.
Worst case you might get a temporary suspension.
Customer Support
help.twitch.tv
Dunno how and if they enforce it, but higher bitrates are usually only allowed for affiliates and partners.
Worst case you might get a temporary suspension.
ZergShadow
Member
Now i think that its only connected with overall bitrate.i can start now good with 7948 128 and higher chances to get good start is lower. For me 7948 128 7949 128 is critical numbers where I start get bad starts.
ZergShadow
Member
This numbers fluctuates all the time.
Thanks for not knowing anything but still posting. There is no differents if you are partner, affliate or a 5 minute old account they all have the same limits. I don't get why this myth always gets brought up.
It does depend on the encoder that is used and by how much it does overshoot with the bitrate, x264 does not fluctuate as much as nvenc, but streaming with nvenc with 8250kbit/s for video and 160kbit/s for audio did always work for me. Going over that gave me from time to time error #1000 and the stream could not be viewed.
ZergShadow
Member
There more bitrate i use, the more chances that i lose source quality at start. I also think it depends on daytime.
Last edited:
Yes if you are peaking over 8500 kbit/s for longer than a few seconds twitch does disable source if you have transcoding or cuts the stream of and shows error #1000 for new viewers if you don't have transcoding. If you got source once running it will keep running, you have to refresh the browser tab to see if it does work.
Keep trying until you find your sweet spot that works. It is worth in a so bitrate limited enviroment to try to squeze every bit you can get for better quality.
Keep trying until you find your sweet spot that works. It is worth in a so bitrate limited enviroment to try to squeze every bit you can get for better quality.
ZergShadow
Member
At start you told that maximum is 8250 +160 is 8410 now you tell that its 8500!
ZergShadow
Member
now i reread that and understand that 8250 150 stable and 8410-8500 can give #1000 error later.tnx.
FerretBomb
Active Member
There is no higher bitrate limit for Partners. I am one.
8000kbps is simply a word-of-mouth, entirely unofficial "known good" value that mostly works.
There is no technologically-enforced upper limit to how much bitrate you can use. (Staff MAY come in and ask you to turn it down.)
I have successfully tested with up to 12mbps, but as you go higher, more people will receive Network Errors and player blackscreens.
Your stream may stop being replicated if the ingest server is unable to process your incoming bitrate. A partial will end up with the Source option being removed, as the ingest/replication/transfer stack failed, but the ingest was able to feed into the transcode stack to the point THAT feed can still be replicated and transferred to the local video delivery CDN servers. It isn't Twitch 'turning off Source'.
Audio bitrate IS factored in.
The difference between 320kbps MP3 and 128kbps MP3 is significant. 320 and 128 AAC (which OBS uses) is mostly un-noticeable unless you're listening side-by-side. I've run down to 96kbps and no one noticed. 160 is as high as I'd bother going on audio.
The drawbacks to high bitrate:
Your viewers WILL receive more player Network Errors and have to reload the stream.
Unless you are a Partner with guaranteed transcodes (quality options), running at a high bitrate will reduce the accessibility of your stream. The higher bitrate you stream at, the fewer people will be able to watch smoothly. Running at a high bitrate without guaranteed transcodes is MASSIVELY shooting yourself in the foot; to grow, you need to make sure that ANYONE coming in will be able to watch your stream, before worrying about wanking over 1080p or 60fps video.
Number-wanking is hands-down the BIGGEST newbie-trap. I fell into it myself at the beginning. A 720p30 stream at 2000kbps with good mic audio and game/mic balance will gain and retain FAR more viewers than cranking the dials to 8000+kbps to satisfy the number wanking "must have 1080p60!!!11!!" that many new streamers do.
8000kbps is simply a word-of-mouth, entirely unofficial "known good" value that mostly works.
There is no technologically-enforced upper limit to how much bitrate you can use. (Staff MAY come in and ask you to turn it down.)
I have successfully tested with up to 12mbps, but as you go higher, more people will receive Network Errors and player blackscreens.
Your stream may stop being replicated if the ingest server is unable to process your incoming bitrate. A partial will end up with the Source option being removed, as the ingest/replication/transfer stack failed, but the ingest was able to feed into the transcode stack to the point THAT feed can still be replicated and transferred to the local video delivery CDN servers. It isn't Twitch 'turning off Source'.
Audio bitrate IS factored in.
The difference between 320kbps MP3 and 128kbps MP3 is significant. 320 and 128 AAC (which OBS uses) is mostly un-noticeable unless you're listening side-by-side. I've run down to 96kbps and no one noticed. 160 is as high as I'd bother going on audio.
The drawbacks to high bitrate:
Your viewers WILL receive more player Network Errors and have to reload the stream.
Unless you are a Partner with guaranteed transcodes (quality options), running at a high bitrate will reduce the accessibility of your stream. The higher bitrate you stream at, the fewer people will be able to watch smoothly. Running at a high bitrate without guaranteed transcodes is MASSIVELY shooting yourself in the foot; to grow, you need to make sure that ANYONE coming in will be able to watch your stream, before worrying about wanking over 1080p or 60fps video.
Number-wanking is hands-down the BIGGEST newbie-trap. I fell into it myself at the beginning. A 720p30 stream at 2000kbps with good mic audio and game/mic balance will gain and retain FAR more viewers than cranking the dials to 8000+kbps to satisfy the number wanking "must have 1080p60!!!11!!" that many new streamers do.
The problem is the fluctuation of bitrate caused by the encoder like i wrote above, example:
static image: https://r-1.ch/analyzer/results/pwxi4dhkgshvzukvbv0w.db3a70
gameplay: https://r-1.ch/analyzer/results/pwxi4dhkgshvzukvbv0w.ff3450
If that happens for multiple segments (so 4 or more seconds) your stream gets detected as to high bitrate and looe source or will display error #1000 for new viewers. But it the error #1000 fix itself after the stream was under that 8500kbit/s for some time, idk if source will come back, I never tested with account that gets transcoding from the start.
Well the 8500 kbit/s limit is nothing unofficial, it is what Yueshi Shen said is the max twitch is willing to deliver for every channel no matter if it is a new or a partner account. Rest of what you wrote is technical wrong, only thing that is true is that viewers that don't have fast enough internet won't be able to view your stream, but depending on the country you focus that share of viewers unable to do that are near zero.
Last edited:
FerretBomb
Active Member
Interesting. Where did he say that? Only bit I've been able to find was about IWS, not Twitch, and as general recommendations.
Again, just a Partner trying to help out with real-world experience as to what works, and why so many never grow. If you want to ignore it and continue number-wanking, that is your prerogative. Enjoy.
- YouTube
Enjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.
youtu.be
Sure you want to help but with your recommendation you would lose me and pretty much any other tech savvy person after some seconds because of the low quality annoyance. If your target are 12 year olds with no money, watchting on their smartphone in a poor country, sure your recommendation could be great. But than you are partner but still will not make any real money. The guys with the deep pockets don't watch trash quality streams.
FerretBomb
Active Member
Hey, handy! Thanks for the link.
If you cater to the up-their-own-ass snobs when you are getting started, you will not grow.
Specifically, for new/small streamers, streaming at high bitrates is shooting yourself in the foot to the point of blowing off your leg. When you have guaranteed transcodes as a Partner, you can go nuts. But frankly, having the mass market share is far more important even then, and most still choose to cater toward the midrange instead of the 'perfect quality only' demanders.
Frankly, you tend to ignore the one whale in favor of a thousand "12 year olds with no money". It's a much safer bet to diversify, and work in monetization through other means. All of which is neither here nor there, as we aren't talking about Partner-level strategy. We're talking about new-users.
So please, stop giving new streamers actively harmful recommendations that will cripple their growth, encouraging them toward your number-wanking preference.
At least 50% of your viewership is not watching the stream at all, just using it for background noise. Video quality is significantly less important than having good audio.
If you cater to the up-their-own-ass snobs when you are getting started, you will not grow.
Specifically, for new/small streamers, streaming at high bitrates is shooting yourself in the foot to the point of blowing off your leg. When you have guaranteed transcodes as a Partner, you can go nuts. But frankly, having the mass market share is far more important even then, and most still choose to cater toward the midrange instead of the 'perfect quality only' demanders.
Frankly, you tend to ignore the one whale in favor of a thousand "12 year olds with no money". It's a much safer bet to diversify, and work in monetization through other means. All of which is neither here nor there, as we aren't talking about Partner-level strategy. We're talking about new-users.
So please, stop giving new streamers actively harmful recommendations that will cripple their growth, encouraging them toward your number-wanking preference.