Should I worry about 2 bad blocks?

[Vosper]

I've just used SmartRipper on R4 PAL Shrek, and it's hit 2 bad blocks. I had it key check every cell-id as a previous rip had made 44 bad blocks. My question, as indicated by the topic, is do I worry about just 2 bad blocks? What effect might they have on the encode (DivX 5 Pro)?

[LIGHTNING UK!]

Ive no idea how Smartripper works out its 'broken blocks'. Why dont you get on the new 'faster and more stable' bus and use DVD Decrypter :-)

[Vosper]

Because I have never had any problems with SmartRipper in the past, and the interface is the simplest and quickest I've seen :)

The encode of the movie worked fine, except for a pause and skip during the Dreamworks SKG logo at the start. I havn't watched the whole thing, but skipping around it seems fine.

But for the sake of argument I downloaded DVDDecryptor and tried it too.. I had it set to demux AC3 (as I usually do that with SmartRipper) and to deal only with Angle 1. Here is a log of what happened, presuming that Sector (DVDDecryptor) == Blocks (SmartRipper) then it looks like DVDDecryptor actually gave me more errors then SmartRipper (which only gave 2 blocks):

I 10:02:51 Operation Started!
I 10:02:51 Source Device: [0:1:0] PIONEER DVD-ROM DVD-115 1.33 (D:)
I 10:02:51 Destination Folder: F:\SHREK\VIDEO_TS\
I 10:02:51 File Splitting: 1 GB
I 10:02:51 Fast Error Skip: No
I 10:02:51 Detect Mastering Errors: No
I 10:02:51 Stream Processing: Yes
I 10:02:51 Remove Macrovision Protection: Yes
I 10:02:53 Extracting Sectors...
W 10:11:01 Failed to read Sector 2408976 - Tracking Servo Failure
W 10:12:12 Failed to read Sector 2408977 - L-EC Uncorrectable Error
W 10:13:16 Failed to read Sector 2408978 - Tracking Servo Failure
W 10:13:19 Failed to read Sector 2408979 - L-EC Uncorrectable Error
W 10:13:23 Failed to read Sector 2408980 - Tracking Servo Failure
W 10:13:31 Failed to read Sector 2408981 - L-EC Uncorrectable Error
W 10:13:35 Failed to read Sector 2408982 - Tracking Servo Failure
W 10:13:37 Failed to read Sector 2408983 - Tracking Servo Failure
W 10:13:38 Failed to read Sector 2408984 - Tracking Servo Failure
W 10:13:39 Failed to read Sector 2408985 - L-EC Uncorrectable Error
W 10:13:40 Failed to read Sector 2408986 - Tracking Servo Failure
W 10:13:41 Failed to read Sector 2408987 - Tracking Servo Failure
W 10:13:41 Failed to read Sector 2408988 - Tracking Servo Failure
W 10:13:41 Failed to read Sector 2408989 - Tracking Servo Failure
W 10:13:42 Failed to read Sector 2408990 - Tracking Servo Failure
W 10:13:42 Failed to read Sector 2408991 - Tracking Servo Failure
W 10:13:43 Failed to read Sector 2408992 - Tracking Servo Failure
W 10:13:43 Failed to read Sector 2408993 - Tracking Servo Failure
W 10:13:43 Failed to read Sector 2408994 - Tracking Servo Failure
W 10:13:43 Failed to read Sector 2408995 - Tracking Servo Failure
W 10:13:44 Failed to read Sector 2408996 - Tracking Servo Failure
W 10:13:44 Failed to read Sector 2408997 - Tracking Servo Failure
W 10:13:45 Failed to read Sector 2408998 - Tracking Servo Failure
W 10:13:45 Failed to read Sector 2408999 - L-EC Uncorrectable Error
W 10:13:45 Failed to read Sector 2409000 - Tracking Servo Failure
W 10:13:45 Failed to read Sector 2409001 - L-EC Uncorrectable Error
W 10:13:46 Failed to read Sector 2409002 - Tracking Servo Failure
W 10:13:46 Failed to read Sector 2409003 - Tracking Servo Failure
W 10:13:46 Failed to read Sector 2409004 - Tracking Servo Failure
W 10:13:47 Failed to read Sector 2409005 - L-EC Uncorrectable Error
W 10:13:47 Failed to read Sector 2409006 - Tracking Servo Failure
W 10:13:47 Failed to read Sector 2409007 - L-EC Uncorrectable Error
W 10:13:48 Failed to read Sector 2409008 - Tracking Servo Failure
W 10:13:48 Failed to read Sector 2409009 - Tracking Servo Failure
W 10:13:48 Failed to read Sector 2409010 - Tracking Servo Failure
W 10:13:49 Failed to read Sector 2409011 - L-EC Uncorrectable Error
W 10:13:49 Failed to read Sector 2409012 - Tracking Servo Failure
W 10:13:49 Failed to read Sector 2409013 - L-EC Uncorrectable Error
W 10:13:50 Failed to read Sector 2409014 - Tracking Servo Failure
W 10:13:50 Failed to read Sector 2409015 - Tracking Servo Failure
W 10:13:50 Failed to read Sector 2409016 - Tracking Servo Failure
W 10:13:51 Failed to read Sector 2409017 - Tracking Servo Failure
W 10:13:51 Failed to read Sector 2409018 - Tracking Servo Failure
W 10:13:51 Failed to read Sector 2409019 - L-EC Uncorrectable Error
W 10:13:52 Failed to read Sector 2409020 - Tracking Servo Failure
W 10:13:52 Failed to read Sector 2409021 - Tracking Servo Failure
W 10:13:52 Failed to read Sector 2409022 - Tracking Servo Failure
W 10:13:53 Failed to read Sector 2409023 - L-EC Uncorrectable Error
W 10:13:53 Failed to read Sector 2409025 - Tracking Servo Failure
W 10:13:54 Failed to read Sector 2409152 - Tracking Servo Failure
W 10:13:55 Failed to read Sector 2409153 - Tracking Servo Failure
W 10:13:55 Failed to read Sector 2409154 - Tracking Servo Failure
W 10:13:55 Failed to read Sector 2409155 - Tracking Servo Failure
W 10:13:56 Failed to read Sector 2409156 - Tracking Servo Failure
W 10:13:56 Failed to read Sector 2409157 - Tracking Servo Failure
W 10:13:57 Failed to read Sector 2409158 - Tracking Servo Failure
W 10:13:57 Failed to read Sector 2409159 - Tracking Servo Failure
W 10:13:57 Failed to read Sector 2409160 - Tracking Servo Failure
W 10:13:58 Failed to read Sector 2409161 - L-EC Uncorrectable Error
W 10:13:58 Failed to read Sector 2409162 - Tracking Servo Failure
W 10:13:58 Failed to read Sector 2409163 - Tracking Servo Failure
W 10:13:59 Failed to read Sector 2409164 - Tracking Servo Failure
W 10:13:59 Failed to read Sector 2409165 - Tracking Servo Failure
W 10:13:59 Failed to read Sector 2409166 - Tracking Servo Failure
W 10:14:00 Failed to read Sector 2409167 - Tracking Servo Failure
W 10:14:00 Failed to read Sector 2409168 - Tracking Servo Failure
W 10:14:00 Failed to read Sector 2409169 - Tracking Servo Failure
W 10:14:01 Failed to read Sector 2409170 - Tracking Servo Failure
W 10:14:01 Failed to read Sector 2409171 - Tracking Servo Failure
W 10:14:01 Failed to read Sector 2409172 - Tracking Servo Failure
W 10:14:02 Failed to read Sector 2409173 - Tracking Servo Failure
W 10:14:02 Failed to read Sector 2409174 - Tracking Servo Failure
W 10:14:02 Failed to read Sector 2409175 - Tracking Servo Failure
W 10:14:03 Failed to read Sector 2409176 - Tracking Servo Failure
W 10:14:03 Failed to read Sector 2409177 - Tracking Servo Failure
W 10:14:03 Failed to read Sector 2409178 - Tracking Servo Failure
W 10:14:04 Failed to read Sector 2409179 - Tracking Servo Failure
W 10:14:04 Failed to read Sector 2409180 - Tracking Servo Failure
W 10:14:04 Failed to read Sector 2409181 - Tracking Servo Failure
W 10:14:05 Failed to read Sector 2409182 - Tracking Servo Failure
W 10:14:05 Failed to read Sector 2409183 - Tracking Servo Failure
I 10:16:48 Operation Successfully Completed! - Duration: 00:13:57
I 10:16:48 Average Read Rate: 6,008 KB/s (4.3x) - Maximum Read Rate: 10,347 KB/s (7.5x)

I know what a Tracking Servo Failure could indicate, but I have no reason to think there's a problem with the drive.

Now, with VStrip I got the following error:
VStrip lost sync (not authenticated?) [@LBA 1917155]
at which point it stopped..

So... bad disk, bad drive or my bad? :D

[LIGHTNING UK!]

Perhaps your drive just doesnt like that disc. It happens....quite often actually.

BTW, checking every cell has nothing to do with read errors. That is just for finding the decryption key.

Going by the sector numbers, you are likely to come across problems (skipping) later on in the video.

[diji1]

Lightning : Perhaps your drive just doesnt like that disc. It happens....quite often actually.

Glad to know I'm not the only one there then :\. I have an old Pioneer 6x which is fairly problematic with some dvd's - swapping the drive for another always fixes it.

[resonator]

I had the exact same problems. I'm running Win2K. I tried both Smartripper and DVDecrypter, but the broken blocks didn't stop. Now I tried the same disc under Win98 and ripping worked like a charm.

[Vosper]

I too am running win2k. I experienced no problems when watching the DVD, so why would it rip badly? Also, the reason I mentioned the key searching is that with both Vob and Cell searching turned on I experienced fewer bad blocks.

[LIGHTNING UK!]

I presume you mean watching on a standalone? These seem to have an incredible tollerance towards dodgy sectors and skip over them at an incredible rate. PC DVD drives just choke on them for a while, then fall over and die!

I have no idea why the cell searching improved matters....it shouldnt do...honest! Sounds like a job for the X-Files team! ;)

[Vosper]

No, i mean watching the movie on my PC, off the same drive I ripped from! that's why I was so perplexed :) But it's ok, don't think this one is going to be solveable :D