>wait a second... >Where are you sending your waves as they record?? You *need* to send them >in an no OS HD, and it *should* be 7200 rpm's. But the real key is that >there can NOT be any programs or op system on the disk you are recording to, >not even a partitioned drive. If you do, you run a huge risk of failure, >unless you have a P4 or over clocked water cooled AMD 1.5 GHz and a gig of >ram and a 10,000 rpm drive... > >even then, chances are there for record failure... > >darw_n
"not even a partitioned drive" How are you saving data to a disk without partition? "there can NOT be any programs" Prioly saved data on a disk will not interfere with the recording in any way unless the disk is totally fragmented. A program started from the recording disk, that does not write/read the disk, will not interfere (unless its using too much cputime). I have recorded wav's ( 44k / 16b /stereo ) to my system disk (7.2krpm IDE!) many timed times without problems, using soundforge on a pIII [EMAIL PROTECTED] Note that the amount of data written to the recording disk only is ((44100 * 2)/1048576)= 0.084 megabytes per second and channel I dont see this as an amount that would need 1,5 GHz cpus or 10krpm disks. If you are reading/writing one of your disks while recording to another chances are that you will choke the IDE interface and/or use too much cputime. These problems are less frequent when using SCSI. Thus, beware of running programs that does a lot of reading/writing when you're recording and there won't be any problems. I have never had any. //[EMAIL PROTECTED]
