Bad DVD9 writing with v2.3.0.0

[chompy]

Hi to all,

 

first of all I would like to thank LIGHTNING UK! for this great piece of software, that's said, I must say that last version (2.3.0.0) is giving problems creating DVD9 (I've only tried build mode): Everything goes find until 91% is reached, then buffers get empty and anfter a few seconds Imgburn writes again for one or two seconds until buffers get empty again and this process continues until 100% is reached... no Write Retries, no errors in log, but in verification process there's bad sectors and the resulting DVD isn't working neither on PC nor in standalone player.

 

I'm not having any problems with DVD5, but my two attemps with DVD9 have given two not working DVDs. I'm only using Verbatim DVD+R DL, and my burner is a Philips DVDRW885, which has never given any problems before with previous ImgBurn versions.

 

Finally I've gone back to v2.2.0.0 and there hasn't been any problem, I've got I perfect burn DVD9.

 

Is anybody having also this problem?

 

Greetings Chompy

 

(sorry I cannot find the logs for the bad burns, but as I said, there wasn't any errors in the log during burning, just in verification).

[LIGHTNING UK!]

The program can't make bad burns like that, it's just not possible. All it does is supply the drive with data, the drive does the burning and has full control of the burn quality.

 

If you get a read error during a verify, it means the drive failed to write to the disc / those sectors properly - again, there's nothing the program can do about that.

 

It's a shame you don't have the logs... those and the IBG (Graph Data) files can really help in situations like this.

 

It's odd that you say both buffers were emptying towards the end of the burn, that would indicate a problem reading from the hdd. If it was just the device buffer, I could perhaps understand it.

[chompy]

Sorry I'm just silly... I thought that going back to v2.2.0.0 had deleted my old logs, but I still have them. so here you have one of them:

 

; //****************************************\\

; ImgBurn Version 2.3.0.0 - Log

; s?bado, 31 marzo 2007, 22:27:24

; \\****************************************//

;

;

I 21:14:32 ImgBurn Version 2.3.0.0 started!

I 21:14:32 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 1)

I 21:14:32 Total Physical Memory: 1.048.044 KB - Available: 697.468 KB

W 21:14:32 Drive D:\ (FAT32) does not support single files > 4 GB in size.

I 21:14:32 Initialising SPTI...

I 21:14:32 Searching for SCSI / ATAPI devices...

I 21:14:32 Found 1 CD-ROM, 1 CD-RW, 2 DVD-ROMs and 1 DVD?RW!

I 21:14:53 Operation Started!

I 21:14:53 Building Image Tree...

I 21:14:53 Calculating Totals...

I 21:14:53 Preparing Image...

I 21:15:00 Using Layer Break LBA: 1969066 -> 1969072 (VTS_01, PGC: 1, Chapter: 16, Cell: 18, Vob/Cell ID: 2/17, Time: 01:14:16, SPLIP: Yes)

I 21:15:00 Image Size: 7.790.460.928 bytes

I 21:15:00 Image Sectors: 3.803.936

I 21:15:00 Operation Successfully Completed! - Duration: 00:00:06

I 21:15:26 Operation Started!

I 21:15:26 Building Image Tree...

I 21:15:26 Calculating Totals...

I 21:15:26 Preparing Image...

I 21:15:34 Using Layer Break LBA: 1969066 -> 1969072 (VTS_01, PGC: 1, Chapter: 16, Cell: 18, Vob/Cell ID: 2/17, Time: 01:14:16, SPLIP: Yes)

I 21:15:35 Image Size: 7.790.460.928 bytes

I 21:15:35 Image Sectors: 3.803.936

I 21:15:36 Operation Successfully Completed! - Duration: 00:00:10

I 21:15:36 Operation Started!

I 21:15:36 Source File: -==/\/[bUILD IMAGE]\/\==-

I 21:15:36 Source File Sectors: 3.803.936 (MODE1/2048)

I 21:15:36 Source File Size: 7.790.460.928 bytes

I 21:15:36 Source File Volume Identifier: 007 CASINO ROYALE

I 21:15:36 Source File Application Identifier: IMGBURN V2.3.0.0 - THE ULTIMATE IMAGE BURNER!

I 21:15:36 Source File Implementation Identifier: ImgBurn

I 21:15:36 Source File File System(s): ISO9660; UDF (1.02)

I 21:15:36 Destination Device: [0:1:0] PHILIPS DVDR885P P2.0 (H:) (ATA)

I 21:15:36 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2,4x)

I 21:15:36 Destination Media Sectors: 4.173.824

I 21:15:36 Write Mode: DVD

I 21:15:36 Write Type: DAO

I 21:15:36 Write Speed: MAX

I 21:15:36 Link Size: Auto

I 21:15:36 Test Mode: No

I 21:15:36 BURN-Proof: Enabled

I 21:15:36 Optimal L0 Data Zone Capacity: 1.969.072

I 21:15:36 Optimal L0 Data Zone Method: IFO Cell Boundary

I 21:15:43 Filling Buffer... (20 MB)

I 21:15:44 Writing LeadIn...

I 21:15:53 Writing Image... (LBA: 0 - 3803935)

I 21:15:53 Writing Layer 0... (LBA: 0 - 1969071)

I 21:36:53 Writing Layer 1... (LBA: 1969072 - 3803935)

I 21:58:19 Synchronising Cache...

I 21:58:20 Closing Track...

I 21:58:22 Finalising Disc...

I 22:11:58 Image MD5: c21cf76d4c0cdee536c5a368f38853d5

I 22:11:59 Operation Successfully Completed! - Duration: 00:56:22

I 22:11:59 Average Write Rate: 2.989 KB/s (2.2x) - Maximum Write Rate: 3.360 KB/s (2.4x)

I 22:11:59 Cycling Tray before Verify...

I 22:12:17 Device Ready!

I 22:12:18 Operation Started!

I 22:12:18 Source Device: [0:1:0] PHILIPS DVDR885P P2.0 (H:) (ATA)

I 22:12:18 Source Media Type: DVD+R DL (Book Type: DVD-ROM) (Disc ID: MKM-001-00)

I 22:12:18 Image File: -==/\/[bUILD IMAGE]\/\==-

I 22:12:18 Image File Sectors: 3.803.936 (MODE1/2048)

I 22:12:18 Image File Size: 7.790.460.928 bytes

I 22:12:18 Image File Volume Identifier: 007 CASINO ROYALE

I 22:12:18 Image File Application Identifier: IMGBURN V2.3.0.0 - THE ULTIMATE IMAGE BURNER!

I 22:12:18 Image File Implementation Identifier: ImgBurn

I 22:12:18 Image File File System(s): ISO9660; UDF (1.02)

I 22:12:19 Verifying Sectors... (LBA: 0 - 3803935)

I 22:12:19 Verifying Layer 0... (LBA: 0 - 1969071)

I 22:21:32 Verifying Layer 1... (LBA: 1969072 - 3803935)

W 22:26:51 Failed to Read Sector 3225280 - Unrecovered Read Error

W 22:26:51 Sector 3225280 maps to File: VIDEO_TS\VTS_01_6.VOB

W 22:26:52 Failed to Read Sector 3225281 - Unrecovered Read Error

W 22:26:52 Sector 3225281 maps to File: VIDEO_TS\VTS_01_6.VOB

W 22:26:53 Failed to Read Sector 3225282 - Unrecovered Read Error

W 22:26:53 Sector 3225282 maps to File: VIDEO_TS\VTS_01_6.VOB

W 22:26:54 Failed to Read Sector 3225283 - Unrecovered Read Error

W 22:26:54 Sector 3225283 maps to File: VIDEO_TS\VTS_01_6.VOB

W 22:26:55 Failed to Read Sector 3225284 - Unrecovered Read Error

W 22:26:55 Sector 3225284 maps to File: VIDEO_TS\VTS_01_6.VOB

W 22:26:56 Failed to Read Sector 3225285 - Unrecovered Read Error

W 22:26:56 Sector 3225285 maps to File: VIDEO_TS\VTS_01_6.VOB

W 22:26:57 Failed to Read Sector 3225286 - Unrecovered Read Error

W 22:26:57 Sector 3225286 maps to File: VIDEO_TS\VTS_01_6.VOB

E 22:26:58 Failed to Read Sector 3225287 - Unrecovered Read Error

E 22:26:58 Sector 3225287 maps to File: VIDEO_TS\VTS_01_6.VOB

E 22:26:58 Failed to Verify Sectors!

E 22:26:58 Operation Failed! - Duration: 00:14:40

I 22:26:58 Average Verify Rate: 7.338 KB/s (5.3x) - Maximum Verify Rate: 10.318 KB/s (7.4x)

I 22:27:24 Close Request Acknowledged

I 22:27:24 Closing Down...

I 22:27:24 Shutting down SPTI...

I 22:27:24 ImgBurn closed!

 

Greetings,

Chompy

 

EDIT:

I also have to say that I had to use FixVTS in order the be able to open this compilation in DVD Remake, and that what I burned is the result obtained from DVD Remake (which never has given any problem before)

Edited April 1, 2007 by chompy

[LIGHTNING UK!]

8 bad sectors in a row (at least)... are you sure you can't see any visible defects on the media?

 

There's not a different colour ring around the 2/3rds mark on the disc?

 

Like I say, I couldn't make the program burn a sector that then couldn't be read back even if I tried!

 

Whatever's going on there, it's out of my control.

 

If the buffers are dying and the drive coughs and splutters, it's burnproof stuff will kick in. If that's not doing it's job properly and isn't zero loss linking as it should do, that's where your errors might be coming from.

[chompy]

8 bad sectors in a row (at least)... are you sure you can't see any visible defects on the media?

 

There's not a different colour ring around the 2/3rds mark on the disc?

 

Like I say, I couldn't make the program burn a sector that then couldn't be read back even if I tried!

 

Whatever's going on there, it's out of my control.

 

If the buffers are dying and the drive coughs and splutters, it's burnproof stuff will kick in. If that's not doing it's job properly and isn't zero loss linking as it should do, that's where your errors might be coming from.

 

Thanks LIGHTNING UK!,

 

I'll check that bad burned discs and I'll try to find that different colour ring, but two consecutive defective Verbatims? Maybe...

 

I must admit that the source was quite problematic: 007 Casino Royale, which gave me lots of problems (?Arcoss protected?), but FixVTS seemed to fix them all. Could it be that "corrupted" VTS was the cause of that problem? (The final copy that was correctly burnt with v2.2.0.0 was "reconstructed" with DVD Rebuilder (no compression)).

 

Greetings

[lfcrule1972]

Sorry chompy we can only help you with queries on the actual burn. We cannot help you with anything to do with copyright protection removal problems such as you mention above

[LIGHTNING UK!]

The drive doesn't care about the content of your image, it could be all zeroes for all it cares.

 

The problem here is just that it can't read back (full stop) what it just wrote.

 

Of course, that should NEVER happen unless:

 

1. your media is rubbish

2. your drive is rubbish

3. the drive doesn't support the media

 

By 'rubbish' I mean it could be rubbish in general, just a 1 off fluke or that it needs cleaning.

[chompy]

The drive doesn't care about the content of your image, it could be all zeroes for all it cares.

 

The problem here is just that it can't read back (full stop) what it just wrote.

 

Of course, that should NEVER happen unless:

 

1. your media is rubbish

2. your drive is rubbish

3. the drive doesn't support the media

 

By 'rubbish' I mean it could be rubbish in general, just a 1 off fluke or that it needs cleaning.

 

1. My media is always Verbatim+R for DVD5 and Verbatim+R DL for DVD9, but I know that they can also be sometimes bad.

2. It's true that my Philips isn't the best burner available, but it has never given problems burning DVD9 (+50 with v2.1.0.0 and v2.2.0.0) before.

3. In Philips support site Verbatims are said to be fully compatible.

 

The same day, before, between and after getting these bad burnt DVD9s I got perfect burnt DVD5s (DVD+R and DVD+RW) with the same files that copied altogether in one DVD9 gave problems, and maybe it was by chance, but when I reinstalled v2.2.0.0 my first attemp with those files worked perfectly.

 

Another strange thing is that the two times the buffers started dying at the same point 91%, another chance?

[LIGHTNING UK!]

I really can't account for buffer issues.

 

The program always reads as quickly as it can from the hdd and sends the data to the drive as often as it lets it.

 

From start to finish, the program just repeats the same 'Write (10)' command over and over and over again (with only the LBA changing), so percentages don't even come into it.

 

Again, I can't introduce errors onto the disc, only the drive can do that. I truely have no idea why you're getting them. If I did, I'd tell you. At the moment, iffy burnproof code is my only explaination (based on what you've said about buffer issues).

 

The IBG file (Graph Data) would have shown us any slow downs / buffer issues - it's good practice to autoexport that info (configured in the settings) and then you've always got it to refer back to.

[chompy]

OK lots of thanks!!

 

As you said, the problems could be due to bad media... Next time I burn a DVD9 (I don't have anything to burn right now, so maybe it will be with incoming v2.3.1.0) I'll enable autoexport IBG, so I'll be able to post it if I get this problem again.