How long does it take you to copy a dvd with DVD Shrink?

[ferrarifreak93]

My old system took about 25 min to burn a dvd movie (8x burner) and so does my new system with the same burner. I thought conroe was suppose to be much quicker...

 

[jpeyton]

A new processor doesn't speed up your DVD burner. Why don't you compare encoding times?

 

[ferrarifreak93]

I wasn't expecting the new cpu to speed up my burner...but I did expect the entire process within DVD Shrink to be quicker

 

[jpeyton]

We need numbers to draw a conclusion.

My C2D is a lot faster than my P4 at encoding, even at 2.4GHz stock speed.

 

[ferrarifreak93]

yeah, my first post was unclear. Basically, I know the conroe is much faster when encoding. But this didn't translate to a significant decrease in DVD Shrink times in my experience.

 

[GeezerMan]

I thought I had a problem with DVD shrink time when going to a Opteron 165 overclocked to 2.6GHz. It seemed like it should go faster. Turns out it was a bottleneck on the hard drive. When shrinking and encoding to the same drive, it won't be very fast. Encode to a second internal drive, and BAM. My encoding speeds TRIPLED.

 

[3chordcharlie]

A decent P4 or better can easily outdo the simultaneous read/write capability of any hard drive that you likely have in your system. A second internal drive is the best way to speed up encoding in your case.

 

[Rottie]

Encoding to second hard drive like Western Digital Raptor 150 will cause C2D a speeding ticket.

 

[Duvie]

however if you look at my old benches i did several months back i saw huge performance increases even when using 1 hdd....problem is most ppl dont know what they are doing....

there are more serious bottlenecks then the hdd alone when it comes to dvdshrink.....Some DVD-rom drives have fixed limits of rip speed....you need to look at what cpu usage is throughout the process...

Also are you using same version on both systems? Deep ananlysis and sharp adaptive corrections may add time but will give a much more superior product them before....plus they are better on latest version and that also added some time....

1) have to use same version
2) have to use same DVD movie when testing...they are not all the same....
3) have to use same dvd-rom drive....they do not all rip at the same speed...
4) have to use same HDD....defragged, drivers, configurations, size of drive, SATA vs PATA (though minimal), etc can all be factors in differences

so post all you r specs...the movie used....times on both system...

If you cant do this then you dont know what you are doing and you are not in the right position to make any conclusions.....

 

[mithrandir2001]

I'm confused about these hard drive issues. I use DVD Shrink to read from my DVD-ROM and encode an ISO to HDD and then I use ImgBurn separately to burn. I guess others are ripping with another tool (to HDD) and then using DVD Shrink/DVD Decrypter for batch encoding/burning?

I always use deep analysis and adaptive corrections (CPU intensive) and even with encoding from DVD-ROM directly, DVD Shrink needs about 25-30 minutes per disc. I have a stock E6300 and while I have nothing to compare against I am generally pleased with the performance. Burning with ImgBurn takes up about another 20 minutes with full verify, but this is dependent on DVD burner drive speed.

 

[GeezerMan]

In my experience, rip speed is dependent on DVD rom speed. I just ripped a home movie of mine, and CPU usage for me was very low. Analysis, shrinkage, and encoding is very CPU intensive. If you encode a DVD, not shrinking it, just encode, from one internal drive to another, what KB/s speed does DVD shrink show? If I encode from one internal SATA drive to another, I can hit 60,000 KB/s, whicjh I think is pretty good. Now, throw in an analysys, or shrink it, and it slows way down.