Goes down from 50 to 30
http://pastebin.com/tXTGjLeQ
http://pastebin.com/tXTGjLeQ
Assuming this is what you're talking about, it generally will mean that your encoder settings are too aggressive for your hardware. And to be fair, 720p@60fps is right on the edge of what an i5 can really handle, on a good day. You may want to consider scaling back to 45fps to leave yourself a bit more margin for error/load-spiking.03:32:41: Number of frames skipped due to encoder lag: 1619 (8.72%)
03:32:41: Total frames rendered: 16759, number of late frames: 397 (2.37%) (it's okay for some frames to be late)
IN-Game and in stream i get dropped frames. especially in stream.Jim said:I don't see dropped frames. Dropped frames typically means network data, so in this case you're probably just confusing the terminology.
As for video, I don't see any particular problem with the log file, nor does it seem you're using monitor capture, which is typically not recommended. Could you be more specific about what you mean?
i have everything in lowFerretBomb said:Assuming this is what you're talking about, it generally will mean that your encoder settings are too aggressive for your hardware. And to be fair, 720p@60fps is right on the edge of what an i5 can really handle, on a good day. You may want to consider scaling back to 45fps to leave yourself a bit more margin for error/load-spiking.03:32:41: Number of frames skipped due to encoder lag: 1619 (8.72%)
03:32:41: Total frames rendered: 16759, number of late frames: 397 (2.37%) (it's okay for some frames to be late)
This would also be supported by the 'goes down from 50 to 30'... if your CPU is choking, the encoding rate displayed at bottom-right will drop. It can also happen if your GPU is overtaxed; the logfile suggests that you're using an integrated graphics solution. Monitor the IGP load; if it's maxing out, you may need to drop your in-game graphics options to give it more 'breathing room' or swap to a dedicated graphics card.
If you mean that your viewers are complaining about stuttery playback, the recommended maximum bitrate for a non-partnered streamer on Twitch is 2000; enough for a good quality 720p@30 stream, or possibly a 720@45 stream with some blocking under high motion. You can also drop all the way to 1500kbps to accommodate even more viewers, but 720@30 is about as good as you're going to get, with that.
Also note that audio bitrate is NOT included in the bitrate setting; that's video alone. 160kbps AAC is excessive. Drop to 96kbps, or 128 at most.
ohnasti said:i have everything in low
i think my bit rate is at 3000
i have 5mb upload.
http://www.speedtest.net/my-result/3077182941
I Did this and i am still lagging.. i guess my pc is not enough.FerretBomb said:ohnasti said:i have everything in low
i think my bit rate is at 3000
i have 5mb upload.
http://www.speedtest.net/my-result/3077182941
Speedtest.net is worthless for livestreamers. Run a 6MB test at http://www.testmy.net/upload instead to see what you have for actual constant throughput.
That said, the problem is NOT your bandwidth. You are not dropping frames. You are LAGGING frames, which means that your local settings are set too high. Your i5 is too slow to run 720p@60fps. It cannot encode fast enough to send in real-time, so is skipping frames. You need to drop to 45fps and see if you are still dropping frames at that rate.
The recommendation to drop to 2000kbps (and 96kbps AAC audio) is for your viewers. Most Twitch viewers will start to get stutter if a stream is running at a rate higher than 2000. Partnered streamers have transcoders available (low/medium/high quality settings) so if people stutter on Source they can drop to a lower-bitrate stream. Non-partnered streamers can't. Many viewers will just leave if they stutter too much. So keeping your bitrate around 2000 is in your best interests, to retain viewership and have people come back.