Question / Help So I've been dropping frames recently

[roguecival]

I've been streaming for almost a year, and as of recent, I've noticed im dropping a lot of frames and its really starting to get annoying, I have tried the two closest servers near myself; New York and Ashburn, and both of which I am dropping frames on constantly. Could this issue be related at all to my CPU-Intel Core i7-3820 CPU @ 3.60GHz
Of course, here is the log:https://gist.github.com/dda1e07659b4d458bff5
Also, I have over 10up, and 100down.

 

[dping]

I've been streaming for almost a year, and as of recent, I've noticed im dropping a lot of frames and its really starting to get annoying, I have tried the two closest servers near myself; New York and Ashburn, and both of which I am dropping frames on constantly. Could this issue be related at all to my CPU-Intel Core i7-3820 CPU @ 3.60GHz
Of course, here is the log:https://gist.github.com/dda1e07659b4d458bff5
Also, I have over 10up, and 100down.

enable aero in the video tab lower your bitrate to 2200-2500.
Best bed, if you are having issues, run this test for your region without OBS or anything happening on your PC
http://www.teamliquid.net/forum/tech-support/478845-twitchtest-twitch-bandwidth-tester

Post a screen shot of the results.

ping to server doesn't matter, quality to the ingest is the most important.

 

[roguecival]

http://x-v.it/9a4o63
Also, I talked to my internet provider, they said its nothing wrong on my side, but more likely there is a bottleneck of data going to the servers which are incapable of working?

 

[FerretBomb]

The ingests have been having problems since Thursday/Friday; I've been seeing the same thing, as have several other sizable streamers. I've been using Dallas and Ashburn, switching to try and fix it, but the only thing really to be done is keep going until it smooths out again. Verified that my local connection wasn't the issue, and my connection to the ingest region was solid. Meaning it's either a weird/bad route problem, or (MUCH more likely) the ingests being on fire while Twitch was off at PAX.

Seconded though. Turn Aero on; it improves performance in OBS significantly. And unless you're a Partnered caster, you should stick at or below 2000kbps to minimize viewer buffering. 3500 will just lead to buffering-hell and people leaving for a more smoothly watchable stream.

Also, if you run Twitchtest as Admin, you should get quality ranks for each server instead of all zeroes.

 

[roguecival]

Alright, thanks FerretBomb, I'll make some changes to the output so it is more watchable. Also, i've been seeing this issue for around two weeks which sucks.Also, I have Aero unchecked now so that could help, hopefully.
Also here is some data from my latest stream: https://gist.github.com/2077469bd97ce012e21d

 

[dping]

The ingests have been having problems since Thursday/Friday; I've been seeing the same thing, as have several other sizable streamers. I've been using Dallas and Ashburn, switching to try and fix it, but the only thing really to be done is keep going until it smooths out again. Verified that my local connection wasn't the issue, and my connection to the ingest region was solid. Meaning it's either a weird/bad route problem, or (MUCH more likely) the ingests being on fire while Twitch was off at PAX.

Seconded though. Turn Aero on; it improves performance in OBS significantly. And unless you're a Partnered caster, you should stick at or below 2000kbps to minimize viewer buffering. 3500 will just lead to buffering-hell and people leaving for a more smoothly watchable stream.

Also, if you run Twitchtest as Admin, you should get quality ranks for each server instead of all zeroes.

for the majoriy of streamers, we can recommend 3000 and have them dial back if 1 or two are buffering. Maybe a year ago when twitch was still getting their shit together 2000 or less. not more so 2500-3000 is what I've been recommending max.

This is, of course has nothing to do with OP just wanted to let you know