So it did not work. Here is the latest log.
https://gist.github.com/ad433164ab8235842a5b
the twitch test, do you see the quality to the right? that is bad. you have plenty of bandwidth, but its not steady, this is why it gave you a 27% quality.
for example, I used to have 3Mbps upload, and when I ran that test, I would get somewhere between 60-80% line quality. being as all your ingests are giving the same quality, this is some load issues at your ISP. maybe even as local as your node. usually ISPs don't consider twitch high priority, but with as many people streaming now-a-days, it can really clog weak network components.
Anyway, things that you can control is ensuring drivers are good for your NIC (best are from the motherboard manufacturer's website) and chipset drivers. a good quality cat5 cable, and not connecting through an old hub, but directly to the router, asking them to replace your router/modem. ask ISP to run a line quality test for a 24 hrs or more period, etc. I dont take no for an answer with my ISP, I make sure all of my equipment is in order and make sure they do what they can to diagnose the issue. some ISPs are harder than others.
Luckily I was one of the lucky few that have google fiber and can run the twitch test with really low RTT, 100 quality and 10,000kbps. I'm not braging, I'm just glad to be done with TWC.
ok, back to troublshooting,
@R1CH, can you recommend any change of his latency tuning factor that might help? maybbe 25? maybe disabling "tcp send window optimizations"?
@TheNerdShow , you can play with these settings but just note where the defaults are. some changes will be worse than others and its definitely not advised for this to be a typical practice of other viewers.
