Re: Traffic Management in general
"160p HD works with roughly 250kb/s :-) so what are some people on about! Your eyes cant see much difference anyway! 1080p requires more 750 - 850kb/s."
160p "HD"? Whut? You sure that wasn't a typo of "720p"?
Anyway, let's assume 0.25 bits per pixel compressed video in 1080p.
1920*1080 = 2,073,600 pixels.
2,073,600 * 0.25 = 518,400, divided by 8 = 64,800 bytes per frame.
At 25 frames per second, that's 1,620,000 bytes per second. Quite a bit more than 850 kilobits. In fact several times as much. At 30fps it goes to 1,944,000 bytes per second, which doesn't really leave much of a budget out of that 2mbit/sec. None at all with a very large amount owing, actually. In fact you wouldn't get much change out of two megaBYTES per second.
Now remember that video streams are not regular, and tend to have keyframes every few seconds followed by a bunch of delta information showing how stuff has changed since the last keyframe. Suddenly, that 2mbit/sec limit seems a little... small.
Of course, not many people will play 1080p over a mobile phone... but some people have tablets, and some of us do like to tether, or plug our HDMI-port-enabled phones into TVs.
(edited because of a few schoolboy errors.. the real figures are even worse!)