Question / Help how do the viewers get no lag?
- Thread starter thaysen13
- Start date
FerretBomb
Active Member
You can't. Livestreaming isn't a Skype call; the video has to be encoded, ingested, replicated, served, decoded. There's a massive amount of work on the back end, and with the additional limits of HLS, 12 seconds is about the bare minimum.
For non-partnered streamers, 720p@30fps, 2000kbps is the recommended 'golden point'. With NO custom buffer size.
Too much bitrate and your viewers will stutter and lag worse.
For non-partnered streamers, 720p@30fps, 2000kbps is the recommended 'golden point'. With NO custom buffer size.
Too much bitrate and your viewers will stutter and lag worse.
Dont know i can stream and watch anything without problems, at the usual recommended bitrate of 3500. 2000 is a bit low and looks shitty, we have 2015 with 4K videos rolling out and 100mbit/s and higher avaiable almost everywhere. The only time when i get lags, is when Twitch is almost dead (400k people watching LCS whatever).
FerretBomb
Active Member
@Cryonic 3500 is far too high for the majority of Twitch viewers; it isn't the 'recommended'. It's the maximum bitrate that the Twitch servers are guaranteed to handle on the ingest side, without running into technical issues. Exceeding 3500 puts you into 'here there be dragons' territory, and is done purely at your own risk.
Twitch recommends that non-partnered casters (who don't have transcodes/quality options available full-time) not exceed 2000kbps, as that is the breakpoint where a majority of Twitch viewers will be able to watch without buffering. It's why the 720p@30fps, 2000kbps 'golden point' exists, as the best tradeoff between resolution, smoothness of motion, and image fidelity, while working within that technical constraint.
2000kbps isn't going to look the very best.
But no one will come to your stream for crystal-clear video to begin with.
And if they get stuck in buffering hell because you're running at too high a bitrate (eg: 3500 being WAY too high for most people), they sure as heck will leave.
Twitch recommends that non-partnered casters (who don't have transcodes/quality options available full-time) not exceed 2000kbps, as that is the breakpoint where a majority of Twitch viewers will be able to watch without buffering. It's why the 720p@30fps, 2000kbps 'golden point' exists, as the best tradeoff between resolution, smoothness of motion, and image fidelity, while working within that technical constraint.
2000kbps isn't going to look the very best.
But no one will come to your stream for crystal-clear video to begin with.
And if they get stuck in buffering hell because you're running at too high a bitrate (eg: 3500 being WAY too high for most people), they sure as heck will leave.
Well i got the i7 5820K @ 4,6GHz extra to have the horsepower for pumping out 1920x1080 @ 60FPS. And this resolution with 60 fps will look like poop even at 3500. We need more and other plattforms can support more. I dont go below 3500 just because anything else will look like crap.
We are not in the 90s anymore, higher bandwith is the future to improve the video quality and this is the first thing to crank up overall.
I could stream at 720p 60 fps 2000kbps and use the CPU to the full power, going with fast or even a slower preset to improve the quality, but even the best cpu cant replace an extra 1500kbps of bandwith in terms of quality.
We are not in the 90s anymore, higher bandwith is the future to improve the video quality and this is the first thing to crank up overall.
I could stream at 720p 60 fps 2000kbps and use the CPU to the full power, going with fast or even a slower preset to improve the quality, but even the best cpu cant replace an extra 1500kbps of bandwith in terms of quality.
Harold
Active Member
And all of that power that YOU have means jack when the route between twitch and your viewers doesn't allow them to use 3500kbit streams and you're putting one out at that without transcoding.
You're subjecting a route that only supports about 2200kbit total bandwidth to over 3800kbit total and expecting it to work right.
It won't.
You don't want your viewers to buffer? Downscale, lower your bitrate, and lower your broadcast framerate.
You don't want to do all that? Get partnership or use youtube for broadcasting.
You're subjecting a route that only supports about 2200kbit total bandwidth to over 3800kbit total and expecting it to work right.
It won't.
You don't want your viewers to buffer? Downscale, lower your bitrate, and lower your broadcast framerate.
You don't want to do all that? Get partnership or use youtube for broadcasting.
Well why the heck is there a problem with a bitrate around 2--4 mbit/s?
Youtube works fine for most people even while loading 4k Videos, same with netflix etc and also other streaming platforms like cybergame, goodgame, gaminglive whatever.
Only twitch shows some problems, but not for anyone. I can watch any stream, even over 4500bitrate (we have a few crazy people streaming at this bitrate to twitch, but they are partnered). Never had a buffering problem if the twitch server is stable...
Youtube works fine for most people even while loading 4k Videos, same with netflix etc and also other streaming platforms like cybergame, goodgame, gaminglive whatever.
Only twitch shows some problems, but not for anyone. I can watch any stream, even over 4500bitrate (we have a few crazy people streaming at this bitrate to twitch, but they are partnered). Never had a buffering problem if the twitch server is stable...
Harold
Active Member
Because non-partnered and/or low-viewer streams get routed exclusively out of the San Fransisco servers of twitch. A lot of people don't have good routes to those servers, so they're shafted on any stream that uses a combined audio/video bandwidth of about 2200kbit.
Your own experience isn't typical.
Your own experience isn't typical.