PDA

View Full Version : Dropping Frames & CPU usage drops to 0%... stumped


fasttimes
5th December 2002, 23:32
I'm dropping groups of 18 frames each during capture. A three hour capture will have about 4K-5K dropped frames! The Preview window also shows "frozen" video and CPU usage *drops to 0%*, during the frame drop periods. CPU usage is about 30% during capture without preview, and about 60% with.
The only things recently added is a A04 DVD-R/RW burner, and two 120GB Maxtor hard drives. I reinstalled Windows, and left out these components, and I get good capture on the 60 GB drive alone (as before), but the new drives drop frames as stated above, with or without the A04 installed.

I'm stumped to what to try next. The drives just seem to drop for no reasonable reason I can discover. The capture files are not fragmented, and they are more than fast enough to keep up with the sub-10MB/s demand. I also can't explain why the CPU usage dropped during these episodes. I'm baffled! Is this possibly a power supply related issue? Might the CPU be damaged? Could "write-verify" be turned on in the new drives? Anyone have a clue what the problem might be?!

Config:
AMD 1900+, K7S5A motherboard, 1GB PC133 RAM, Silicon Image chipset RAID controller, Sound Blaster 5.1, Hauppauge Win-TV, BTWinCap drivers, VirtualVCR, HuffYUV codec, 720x480 YUY2 stream under 9MB/s, 60GB 5400RPM Maxtor (system drive now, used to be cap drive), two new 120GB 5400RPM Maxtor drives (new cap drives.) Indexing, Restore, swap file, ect. all disabled. Minimal Windows XP Pro install, with only basic apps needed to capture installed.

Same results when used as a RAID-0 pair on the RAID controller, and when used independently on the RAID controller, and when used independently on the motherboard controller with the RAID controller removed from the system, and when only one or the other is installed on the motherboard controller.

Mike456
30th December 2002, 10:23
Have you enabled "Disable Windows Write Buffering"? What are your Buffer settings?

PowerMacG4
3rd January 2003, 22:56
If all else fails try getting a new mobo. SiS chipset problem? Maybe check SiS's site for updated IDE drivers.