Bowser,
Cris clearly knows more than I do concerning this issue, but there's something he forgot to mention. Depending on color depth and resolution of your captured video stream, as well as the video format (and therefore degree of compression) the actual bandwidth needed for playback varies. Your disk or memory subsystem may not be the bottleneck; rather it might be your CPU or video card.
For example, if you are playing a highly compressed video, the CPU has to do a lot of work to decompress each frame before displaying it. A good video card may offload some of that work (depending on compression algorithm.) For example, there are MPEG-1 and MPEG-2 hardware accelerators.
In general, the more frames per second -- the better. However, at around 30 fps any further increase becomes unnoticeable even to experts. That's why TV, for example, does 30 fps. So if with increased frame rate you get decreased performance, blame the hardware and not the frame rate.
I've got a simple (though very crude) test to see whether it's your CPU or your disk that's a limiting factor. Create a very large video file (multi-GB if you can) with a known number of video frames in it. Then open up the time window to see the seconds as they pass, and copy the large file to another location on the same disk, timing the operation to the nearest second. Take that time and divide it by 2. Then divide the result by the number of frames in the video file. This should give you a rather rough fraction of a second your computer needs to simply read one frame of video from its hard disk. If you want a more reliable figure, repeat the test several times and average the results across the trials. You can further compute standard deviation, or even the error margin, if you want. Naturally, to playback at 30 fps, the computer must be able to read 1 frame in 1/30th of a second. If there's extensive processing involved with each frame, then it would be nice if your computer can read 1 frame in as little as 1/60th of a second or less. Anyway, if the time you get is very small, then your disk is not to blame; rather you need a CPU upgrade (or a memory upgrade, or both -- depending on your CPU brand and model).
My 2 kopecks
------------------
I am; therefore I think.
[This message has been edited by Boris (edited January 16, 2001).]