EPTI don't recommend using this any more since it will cause Chrome to crash.
+ Show Spoiler +
So there's been a lot of complaints about twitch's poor performance recently. While they are to blame for some of it (lack of European data centers and other POPs), I suspect a lot of the problems stem from Flash player and poor TCP/IP tuning. I wrote a program to analyze how fast Flash player is able to receive the data and it did appear to stall from time to time, which may affect how TCP RWIN tuning over higher BDP connections (ie, Europe to US) works, potentially causing too small of a window size.
This program will intercept RTMP connections and handle the networking separately from Flash player using an event based system for maximum performance. If Flash player is unable to read the data fast enough, it will be buffered (up to 4MB). Additionally, a larger initial receive window is attempted.
Fortunately / unfortunately my own connection rarely lags, so I have limited data to see if this has any effect, but from my sample size of kollin, it appears to improve things a little so why not give it a try!
Requirements:
Visual Studio 2010 Runtimes
Google Chrome
Pepper Flash (Chrome's internal flash player, unless you change it this is the default)
Windows 7
Download:
http://www.teamliquid.net/staff/R1CH/TwitchProxy.zip
Put both files in a folder somewhere and run Chrome, then run TwitchProxy. You can tell if it works by watching the console, when a stream is open you should see it spamming away about buffers. If it breaks and you can't browse anything, just restart Chrome - all changes are applied in-memory only. If you restart Chrome completely, you will also need to restart the proxy for it to apply to the new Chrome process.
Note that this program is pretty much an experiment so treat it as such.
This program will intercept RTMP connections and handle the networking separately from Flash player using an event based system for maximum performance. If Flash player is unable to read the data fast enough, it will be buffered (up to 4MB). Additionally, a larger initial receive window is attempted.
Fortunately / unfortunately my own connection rarely lags, so I have limited data to see if this has any effect, but from my sample size of kollin, it appears to improve things a little so why not give it a try!
Requirements:
Visual Studio 2010 Runtimes
Google Chrome
Pepper Flash (Chrome's internal flash player, unless you change it this is the default)
Windows 7
Download:
http://www.teamliquid.net/staff/R1CH/TwitchProxy.zip
Put both files in a folder somewhere and run Chrome, then run TwitchProxy. You can tell if it works by watching the console, when a stream is open you should see it spamming away about buffers. If it breaks and you can't browse anything, just restart Chrome - all changes are applied in-memory only. If you restart Chrome completely, you will also need to restart the proxy for it to apply to the new Chrome process.
Note that this program is pretty much an experiment so treat it as such.
.
