Using DVDDecrypter 3.5.4.0 again for +DL

[wishfull]

Burner LG-GSA H10N latest firmware JL11, also older LG model 4163 firmware A106

 

-Bad burn +DL ImgBurn

-All settings default

-ISO file setting full 8.5 and no changes made before/during rip, all locks removed for easy zipping DVD when playing

-Layer break 0>1 calculated by DVDDecrypter or ImgBurn when disc burn starts

-Differences DvdDecrypter 3.5.4.0 vv ImgBurn 1.3

 

Switched back to DVDDecrypter for burning my +DL media. ImgBurn introduces lots of errors at the end of layer 0 and therefore sometimes a nonplayable disc or lots of the familiar colored squares. What media does not matter.

Possible fault: Faulty calculating layer break? Don't know and DLs are costing to much money to experiment forever.

 

Settings in ImgBurn tab write-write type: DAO and Incremental

Settings in DVDDecrypter tab ISO write mode: SAO and Packet

My burner default settings for ImgBurn DAO and for DVDDecrypter SAO.

 

3xA:

-Any possible advantage using DAO compared to SAO for +DL 8.5 or 4.7 discs?

-Anyhow, I'm happy with the old DVDDecrypter.

-Appreciate any serious advice.

[LIGHTNING UK!]

ImgBurn doesn't introduce anything! It sends commands -> drive deals with commands -> drive burns media.

 

SAO and DAO are one in the same. DAO is just the correct name for DVD burning.

 

The layer break position has nothing to do with burn quality, it's also much better in ImgBurn than it ever was in DVD Decrypter.

 

You are using Verbatim DVD+R DL media yeah? Forget about using anything except that.

[wishfull]

Dear L UK,

 

Yes, right. The drive burns the disc.

Still one thing puzzles me. How come the difference between DVDD and IMG and not one disc but many? There should not be any!

 

Note: Yes, also Verbatim and..... and......etc..

[LIGHTNING UK!]

I honestly have no idea why ImgBurn would be any different to DVD Decrypter.

 

If the drive is behaving itself, the two should behave identically.

 

Maybe a log from the burn would help.

 

Also, some graphs / scans from DVDInfoPro would be useful. Maybe I'll be able to spot where the problem is coming from.