ImgBurn Verifying Problem

[Maculosa]

Hi, I have done few movie backup (all ripped with ANYDVD) and i burn them with ImgBurn (build mode) When burning i got no error, but just after i do the verifying process and i got many errors... Like this : (small part of log life)

I 21:44:11 Verifying Sectors... (LBA: 0 - 3999151)
I 21:44:11 Verifying Layer 0... (LBA: 0 - 2018207)
W 21:44:15 Miscompare at LBA: 390, Offset: 0
W 21:44:15 Device: 0x44
W 21:44:15 Image File: 0x00
W 21:44:15 Total Errors in Sector: 60
I 21:44:15 Verifying Sectors...
W 21:44:16 Miscompare at LBA: 391, Offset: 1
W 21:44:16 Device: 0x15
W 21:44:16 Image File: 0x00
W 21:44:16 Total Errors in Sector: 190
I 21:44:16 Verifying Sectors...
W 21:44:16 Miscompare at LBA: 392, Offset: 1
W 21:44:16 Device: 0x01
W 21:44:16 Image File: 0x00
W 21:44:16 Total Errors in Sector: 299
...

But when i play my backup dvd in my home dvd player everything is playing fine...

Why these is all those errors but dvd working fine ???

Thanks

[guns1inger]

I don't use the verify function in any burning software because it has always returned false negatives. That is, it has always reported failures when the files were fine. Others here don't use the verify functions because they report all is fine when the disc is patently screwed. There are too many factors involved to rely on the verify function to any degree.

I have greater success using the read and speed tests in DVD Info Pro, and run all my discs through those instead.

[LIGHTNING UK!]

There's no such thing as a false negative where verifying in ImgBurn is concerned.

Either the data matches or it doesn't, it's as simple as that.

Miscompares are normally caused by:

1. Something modifying the data somewhere between it being read from the drive and returned to the program that asked for it. This is something AnyDVD and alike can do - hence why it should be disabled when burning / verifying.
2. Faulty memory (bad overclock?) - run memtest+ for a few hours.
3. Some other type of corruption within the system. Maybe a faulty cable to the drive?

[guns1inger]

As I have said before, I have repeatedly had Imgburn fail to verify even small text files that have been happily read afterwards, on different machines and burner combos. I don't use AnyDVD or DVD43 or similar. And it's not just Imgburn. Nero used to do it, Prassi does it. Never had a burning app verify to a degree that I felt safe in trusting it's output in all my years of computing.

This is nothing against Imgburn, which I love and recommend at every opportunity.

[MOVIEGEEK]

I don't use verify because the disc is already burned and there's nothing you can do about it.
If I am really concerned about write quality I use Nero CD-DVD Speed.
BTW:thanks Lightning UK for ImgBurn and that other marvelous program!

[LIGHTNING UK!]

guns1inger,

That's fair enough but the application is only as reliable as the hardware.

The verify feature is only issuing the same 'Read (10)' command *any* program would issue (even the OS) to read the disc/file. You can't read a sector in any other way!

So if you're getting read errors, it just means at that moment in time, that drive couldn't read that specific sector (which may or may not be part of a file).

As you've found yourself, it doesn't mean another drive couldn't read it. That's one benefit of having several drives. When one doesn't like something, often another one will handle it just fine. No 2 drives are created equal.

Moviegeek,

A verify isn't a test of the burn quality, just as a PIPO scan in cdspeed or dvdinfopro isn't a test of burn accuracy. You can't substitute one for the other, it's like comparing apples and oranges. Fair enough if it's burnt and verify fails then you can't fix it, but at least you'll know you need to burn another copy!

[lordsmurf]

As much as I love your software LightningUK, the verify feature doesn't return useful results. It's the same with Nero, Prassi and several others. It's been that way since 2001. The same drives function fine with a Nero CD-DVD Speed / KProbe / DVDInfo / etc. testing methods, but those "verify" features never work right.

I've long thought those tests are limited by what may be a forced read speed. System bottlenecks, totally unrelated to the drive and disc, are likely culprits. I would not blame RAM or bad cables, although such things are surely possible. But so are many other issues.

None of these programs can tell you "burn quality" anyway, as media is much more complex than that. Most of those tests are statements about the drives and computers in use, than they are about the disc in the drive.

To the original poster, error correction kicks in on players, so it can sometimes still play an imperfect burn.

Using good media is really the key here anyway, not testing.

[Midzuki]

So far, Nero Burning ROM has never given me false positives
nor false negatives regarding its function "verify written data".
And the few cases of "data verification failed" I have gotten
invariably meant I had bought a crappy disk
(usually a rewritable one). Just my US$ 1.99 for this day.

================