Understanding Read Errors ?

[beammeup]

Hi,

I've made about 300 DVD's this year without a problem but I've made a few coasters in the last few weeks.

I can't really pin point the problem.

I get a few lock ups, and digital blocking effects, or a Disk error from my DVD players. This doesn't happen to every disk however.

Here's the simple log file from DVDinfo Pro on one of my coasters

Media ID Code - RITEKG04
Media Type - DVD-R
Read Error list
1. Error - LBA = 000b0550h
2. Error - LBA = 000b0551h
3. Error - LBA = 000b0552h
4. Error - LBA = 000b0553h
5. Error - LBA = 000b0554h
6. Error - LBA = 000b0555h
7. Error - LBA = 000b0556h
8. Error - LBA = 000b0557h
9. Error - LBA = 000b0558h

Does anyone know the main casues of these types of errors ?

Is it Bad media - Is it low system resources when burning the DVD.
Is it a corrupt mpg2 file before authoring. Is it corrupt authoring. ????

I always use Ritek G04's - r
MPG2 files are created with Procoder 1.5 @ about
6500 - 7000 CBR - 192 audio - program stream
Authoring is done with TMPGenc Author

All these coaster DVD's have only one 3 - 4 gig file with about 20 - 30 chapters. I use motion chapter pictures on a 8 second cycle

Can anyone shed some light on what might be causing these errors

Thanks
Scott

[Baldrick]

Tried scan with nero cd dvd speed, under Extra->Scandisc? Maybe just a problem the dvdinfopro scannner. Check at the dvdinfopro forum, www.speedlabs.org

[jkdawg]

I basically have the same situation, only i'm using the import dvd feature in TMPGenc. Nero ScanDisc said it was all OK, but my dvd player locks up when playing. I will try the other program to scan.

[BetaMaster]

My guess would be bad media. The numbers listed correspond to consecutive sectors of the disk, so it's a "bad spot", most likely due to the quality of the media rather than issues with your player or software. If you get the errors in the exact same spot every time, then I would blame it on your burner.

From my limited understanding, the burn (and the press on a commercial disk) encodes not just data, but a large number of error correcting codes that actually take up more space than the data itself. The reader and its hardware uses this information to make sure that it is properly reading the data. When you do a PI scan with KProbe or Nero CD Speed, what the software is doing is reading the number of error-correcting codes that seem to be in error themselves. However, the readers are very error tolerant, and even a large number of errors in a sector (up to 256 is still acceptable) won't affect the player's ability to read the disk. However, as the number of errors rises, the ability of the player to read the disk degrades to the point that it can't read it, even at 1X.

A lot of things can cause such errors, such as imperfections in the dye surface, or dyes that can't properly withstand the writing laser and get destroyed in the process.