OTW: if I understand correctly, the principle involved here is only in the capture process. In order to avoid dropped frames, choppiness etc., the incoming video needs to be streamed as smoothly and consistently as possible to the hard drive. This has two implications. The first is that, as the application runs and e.g. virtual memory is occasionally invoked, some disk access is required. Thus if your application and virtual memory space are on the same drive as you are capturing your video to, capture will occasionally be interrupted by other processes while the heads move to a different part of the disk and then back again - giving rise to the possibility of less-than-smooth capture. The second implication is that, ideally, you will be laying your incoming video down to a single, continuous space on your hard drive. If the incoming video needs to halt temporarily while the heads move to a new part of the disk, again, there wil be an interruption to the flow. That's why the strong recommendation is a) to decicate a drive to video capture, and b) to defrag your video capture drive regularly - to maximise the amount of contiguous space on it. How do you 'dedicate' a drive to video? Simply, you just designate that as the drive to which you will do all your capturing. In my set up, all the applications are on 40GB physical drive C: and all video is captured to a separate 80GB physical drive D:. It works for me. Hope that helps. (By the way, I'm deeply jealous of your 2 x 200GB drives - every couple of projects, I have to delete pretty much all the contents of the D drive before I can start another..)
__________________
Premiere Pro, Encore, Photoshop, Ulead VS6, WXP Pro, Core 2 Duo, 2GB, 2 x 250GB SATA3 drives, 2 x 250GB USB 2 external drive, DVD writer, GeForce 7300 GS 256MB
The biggest fool can ask questions that the wisest man cannot answer... | 
Linear Mode
