View Profile
View Forum Posts
Private Message
Is there much difference between these???
My OS hard drive is ATA 133 split into 4 x 10GB.
When I capture 720 x 576 I get flickers.
Lower resolution are flawless.
I just added a 80gb ATA100 hard drive.
I captured to that hard drive and the picture is perfect.
Is this because....
1) I am capturing to a second disk?
2) The second disk is empty?
3) The second disk is newer and even though it is ATA100 it is faster?
I have benchmarked the 2 drives and there is nothing between them strangely. But my ATA 133 is quite full. Although I had this problem when I had just the OS installed.
The reason I ask is because the ATA 133 is supposed to be coming out.
And I was going to install my OS on the ATA 100 drive and partition it. Then capture to it.
Is it likely I will get the same problem if i don't capture to a seperate hard drive??
Cheers
Fozzee
+ Reply to Thread
Results 1 to 11 of 11
-
-
BTW Both are 7200 rpm drives.
Fozzee -
Keep the OS and the capture drives separate. Big cause of less-than-perfect captures is people trying to do this on single drive systems. Use the fastest drive as the capture drive preferrably on it's own channel. Mine is an 80 Gig 7200 rpm Maxtor on it's own channel on an ATA 100 adapter and it works great with little or no frame drops even at higher bit rates (6 MB/s + Mpeg-2 720X480). Also, when capping, turn everything off that you can, right down to the clock. Everything steals cycles, especially on low spec systems (like my PIII 1GHz). Good luck...
-
I agree with everything he said. DV capture users could use the slower drive for capping (as long as it's 7200RPM).
Also, the more full the drive is, the slower it caps, because the end of a drive (inside sectors) are half the read/write speed of the outer ones.
Also, in your case if you captured on the last partition, you're effectively using the slowest part of the disc. AND, any time the CPU accesses windows or swapfile data on partition C, it's seeking back & forth between the inner & outer tracks - NOT a recipe for success.
-
Fozee,
What motherboard chipset have you got? I had flickering in my captures until I got rid of my VIA-based motherboard. I just bought an intel-based board and now the flickering has gone. Just a thought...
cheers,
cliffo -
Hmm, I didn't know there were IDE controllers supporting ATA133 as of yet...
Which MoBo is it, or you are using an Add-on IDE controller? -
Hi
Of course it's a via board. I'm fully aware of the problems. I'm going to stick to capturing at 480 x 576. Then converting to 352 x 576 1/2 DVD. My captures look great at that resolution so I'll leave 720 x 576 alone.
I don't have a DVD writer yet anyway. When I do it'll be time to change mobos.
My mobo is a KT3 ultra.
The ATA133 shows at UDMA mode 6 in Device Manager.
The ATA100 shows as UDMAV Mode 5.
Can't IDE run ATA 133 then?
Fozzee -
ATA133 is pure marketing. 133 is the total speed of the PCI bus, so you'll never take full advantage of the hypothetical top speed. For that matter, no IDE drives today can even USE the bandwidth - they top out under 100 (and for sutained transfer they top out under 66. Numbers above that come from reading the drive's cache, which admittedly can be important with today's 8MB cache drives).Originally Posted by Fozzee
-
So if i change from.....
40GB ATA 133 to 80GB ATA 100 I won't notice a difference in speed.
Cheers
Fozzee -
No you probably won't notice the difference. You also have to take into account the brand and model of the drive. There are some ATA100 HD that are faster than ATA133.
-
Right. It's all about where the bottleneck is. Since no IDE drive can supply data faster than the ATA100 interface can take it, that's not the problem.
Quote