dual layer dvd9 rite

[LIGHTNING UK!]

Read the last line of post 47 ;)

[eriksen76]

Read the last line of post 47 ;)

Ups! my bad :o

So that is one of the improvements with IMGBURN compared with Dvddec. when it comes to burning DVD+R DL??

/Eriksen76

[LIGHTNING UK!]

Yes, that's one of the improvements :)

[Ajbolit]

Had tried multiple programs and so far end up with 6 DL coasters ((( Nero or ImgBurn would write them succesfully, but non of the discs would play in neither my PC or DVD player (philips 642). While trying to use the guide for PcgEdit got a following msg:
"Warning: There are 4 discrepancies in some VMGM/VTSI_MAT tables. Do you want to run the "Fix number of streams" macro to fix them?"

[LIGHTNING UK!]

Did you get ImgBurn to 'Verify' after it had burnt this disc?

If you did and it completed successfully, there must be an issue with your original image - at least when playing in the PC.

As for the standalone, it could just be that it doesn't support DL media - or you may need to configure bitsetting to make it look like a DVDROM disc.

[eriksen76]

Had tried multiple programs and so far end up with 6 DL coasters ((( Nero or ImgBurn would write them succesfully, but non of the discs would play in neither my PC or DVD player (philips 642). While trying to use the guide for PcgEdit got a following msg:
"Warning: There are 4 discrepancies in some VMGM/VTSI_MAT tables. Do you want to run the "Fix number of streams" macro to fix them?"

PGCEDIT also ask me this when "importing" the dvd files:

"Warning: There are 4 discrepancies in some VMGM/VTSI_MAT tables. Do you want to run the "Fix number of streams" macro to fix them?"

I always say no, and so far it works with no problems. Don't really think that its something to draw much attention to, as it asks me the question even on "untouched files" all the time.

Lightning UK, would be the one with the correct answer to this

/Eriksen76

[r0lZ]

This warning is issued when there are streams defined in some tables, but not used by any PGC, or (more serious) vice-versa. It has nothing to do with the burning or the format of the ISO.
BTW, you can turn this warning off with the menu Options -> Input/Output -> Automatically launch "Fix Number of Strings in VMGM/VTSI_MAT"?

[eriksen76]

Thanx for the answer, just a small one left

Do I use the same guide when burning DVD-R DL medias as when burning DVD+R DL medias.

Or do I have to make other settings?

So far I have only burned + medias, all successful

/Eriksen76

[r0lZ]

This guide (http://www.videohelp.com/~r0lZ/pgcedit/third_party/blutach/Burning%20With%20PgcEdit.htm) is a general guide, with explanation on how and why to use the 32K gaps method.
This one (http://www.videohelp.com/~r0lZ/pgcedit/third_party/blutach/dl_burning_with_pgcedit.htm) is specific to DL madia.
Both are made by blutach. Thanks again, blu!

For DL-Rs (not DL+Rs!), be sure to put the right value in the "DL DVD-R Layer 0 data zone capacity" field in the burn setup, and to specify the right DL media type in the main window, or you will burn a coaster!

[eriksen76]

This guide (http://www.videohelp.com/~r0lZ/pgcedit/third_party/blutach/Burning%20With%20PgcEdit.htm) is a general guide, with explanation on how and why to use the 32K gaps method.
This one (http://www.videohelp.com/~r0lZ/pgcedit/third_party/blutach/dl_burning_with_pgcedit.htm) is specific to DL madia.
Both are made by blutach. Thanks again, blu!

For DL-Rs (not DL+Rs!), be sure to put the right value in the "DL DVD-R Layer 0 data zone capacity" field in the burn setup, and to specify the right DL media type in the main window, or you will burn a coaster!

Thx, where is it that I find option to specify which media type I want to use?
(main window, you wrote?)

Maby you could provide me with a screenshot.

Thanx

/Eriksen76

[r0lZ]

I mean in the main burn dialog. I've added this button in v0.6.2, near the burn speed. In 0.6.3 beta, it is below the volume label field.

[eriksen76]

I mean in the main burn dialog. I've added this button in v0.6.2, near the burn speed. In 0.6.3 beta, it is below the volume label field.

Found it, thanx

By the way the new: Classic_0.91.7 is out. Do you encourage me to upgrade from Classic_0.91.6 to that version??

/Eriksen76

[r0lZ]

I've just downloaded it. Not tried it yet. But since mkisofs kept the same syntax, it should be OK to use the new version.

[eriksen76]

I guess I'll upgrade then :)

Old version was: 2.01.01a03X (i686-pc-cygwin)
New version is : mkisofs 2.01 X (i686-pc-cygwin

Just burned another DVD+R DL with success. No coasters so far.

Just want to thank you for all your help

Have a nice weekend

/Eriksen76

[mazafaka]

My problem step by step:
1. DVD DL rip with DVDdecrypter 3.5.5.0
2. Some changes in IFO with PgcEdit 0.6.0
3. Compiling ISO with PgcEdit & mkisofs 2.01
4. Burning with DVDdecrypter
Result: whole DVD plays fine on standalone but on PC 2nd layer unreadable (physically readable but files contain wrong data).
Next duplication from this disk impossible.
Have I discovered unknown copy protection mechanism???

When I burn DVD compilation with extra files/folders with Copy2DVD 3.1.1.135 result is the same

[setarip_old]

Have I discovered unknown copy protection mechanism???I doubt that very much, since you also say:Result: whole DVD plays fine on standalone

[blutach]

@mazafaka

What media are you using? Get real Verbatims and I think you'll be OK. Also, you can update PgcEdit (http://www.videohelp.com/~r0lZ/pgcedit/index.html) to 0.6.2

Regards

[mazafaka]

I doubt that very much, since you also say:

I can send you this disk and you'll never make a copy from it.
i've tryed all programs and operating systems.
@mazafaka

What media are you using? Get real Verbatims and I think you'll be OK. Also, you can update PgcEdit (http://www.videohelp.com/~r0lZ/pgcedit/index.html) to 0.6.2

Disc Regions are 1,2,3,4,5,6,7,8
Media code/Manufacturer ID MKM 001
Media Product Revision 00h
Format Capacity 7.89GB(8.47GB)
Book DVD-ROM
Media Type DVD+R DL
Data area starting sector 30000h
Data area end sector 3F177Fh
Layer 0 end sector 22D7FFh
Linear Density 0.293um/bit
Track Density 0.74um/track
Number of Layers 2
Layer Track Path direction (OTP) Opposite track path

I think it's UDF & ISO mismatches.

May be r0lZ or LIGHTNING UK! hame some ideas what could it be?

[r0lZ]

Could you post the DVD Decrypter log here?

Which version of mkisofs are you using when you burn? (You can check it in the burn setup dialog.)

Also, you can verify if there are UDF/ISO mismatches with IsoBuster (http://www.isobuster.com/).

[mazafaka]

unfortunately, log wasn't saved. But burprocess was ok. layerbreak setting too.
mkisofs 2.01x (i686-pc-cygwin)
ISO & UDF are identical

common rule in my case: adding extra files/folder leads to unreadable 2nd layer. if only ifo/bup/vob all ok.

recorder - plextor 740

[r0lZ]

common rule in my case: adding extra files/folder leads to unreadable 2nd layer. if only ifo/bup/vob all ok.
Humm! Good to know. I haven't tested a DL burn with DVD-ROM files. However, with single layer DVDs, it works.

Can you post a screenshot of IsoBuster with the start and end sectors of the files?

[mazafaka]

just burnt music video with PC content. and...successful. so strange :) but these files are from original dvd. I mean no files were added from my pc by me.

see personal message for files

another strange thing - one of my DL disks was successfully read under windows millenium (without udf reader installed)

now I understand nothin in DL recording :-)))

[[Tobi]]

After a long time, I want to begin a test with DL DVD-R again.
The functional way with PgcEdit and ImgBurn is clear for me.
What confuses me, is the message of ImgBurn.


Layer Jump Recording Disabled!
Cannot set the layer break position when burning DVD-R DL media in DAO mode.


I have read the whole thread, concerning Jump Layer Recording and do not understand it yet completely.
Can I ignore the warning really and continue?
I have a player, the DVD-R DL should can and now I want to know it.

Help would be nice.

Thanks

[r0lZ]

IMO, if the number of sectors in L0 is correctly configured in PgcEdit, and you have selected the DL DVD-R media type, it should work.
PgcEdit doesn't use the Layer Jump technique to set the layer break. So, currently, a big gap will be added at the beginning of L0 (between VIDEO_TS.IFO or VOB and VIDEO_TS.BUP) so that the first layer is completely filled with data.
The Layer Jump method may (perhaps?) be used to jump from L0 to L1 before the end of L0, but it's not needed when you burn an image made by PgcEdit. I'm not sure the Layer Jump method works well, and I have no intention to implement it, at least for now.

[LIGHTNING UK!]

Layer Jump is disabled within ImgBurn. The user cannot change that.

It's part implemented but tests have shown the drives don't do what I tell them! Totally my fault, I am sure, but I don't have the means to find out how Layer Jump Recording is actually supposed to be used. So rather than waste peoples discs, I disabled it until I can fix it. You can ignore the error so long as you let PgcEdit do the padding (as mentioned in the post above).

Unlike Nero and alike, I don't have a direct channel to talk to people who make the drives / firmware!

[[Tobi]]

Many thanks for the detailed information. I will ignore the error and try it now.
If interest exists, I can inform later as the result is.

[ron spencer]

informative posts all

[[Tobi]]

Here the result for the DVD-R DL.

If is a little bit wrong, please corrects me and says what is wrong. :)

Media Information

Unique Disc Identifier : [DVD-R-DL:MKM 01RD30 ]
Disc & Book Type : [DVD-R DL] - [DVD-R]
Manufacturer Name : [Mitsubishi Kagaku Media]
Manufacturer ID : [MKM 01RD30 ]
Blank Disc Capacity : [4,282,361,794 Sectors = 8,770.28 GB (8,167.96 GiB)]

---------------------------------------------------------------------------

PgcEdit

Layer break is at absolute sector 2039600. (Offset in L0 is 7.)
Layer break cell:
2039593: VTST 1 , 1 TTN 1 (1:44:15) Title 1 Cell 17 (00:00:38.12), V/CID: 2/1

The pad was 53303 for file VIDEO_TS.VOB
Total translation table size: 0
Total rockridge attributes bytes: 0
Total directory bytes: 4248
Path table size(bytes): 42
Max brk space used 9000
4044583 extents written (7899 MB)

ISO created OK.

---------------------------------------------------------------------------

ImgBurn.log

I 17:35:59 ImgBurn Version 1.1.0.0 started!
I 17:35:59 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2)
I 17:35:59 Initialising SPTI...
I 17:35:59 Searching for SCSI / ATAPI devices...
I 17:35:59 Found 2 DVD-ROMs and 1 DVD±RW!
I 17:38:14 Operation Started!
I 17:38:14 Source File: G:\FERTIGE IMAGES\DUAL_LAYER_TEST.ISO
I 17:38:14 Source File Sectors: 4.044.583 (MODE1/2048)
I 17:38:14 Source File Size: 8.283.305.984 bytes
I 17:38:14 Source File Application Identifier: MKISOFS ISO 9660/HFS FILESYSTEM BUILDER & CDRECORD CD-R/DVD CREATOR (C) 1993 E.YOUNGDALE (C) 1997 J.PEARSON/J.SCHILLING
I 17:38:14 Source File Implementation Identifier: mkisofs
I 17:38:14 Destination Device: [1:1:0] BENQ DVD DD DW1640 BSOB (I:) (ATA)
I 17:38:14 Destination Media Type: DVD-R DL (Disc ID: MKM 01RD30) (Speeds: 4x)
I 17:38:14 Destination Media Sectors: 4.171.712
I 17:38:14 Write Mode: DVD
I 17:38:14 Write Type: DAO
I 17:38:14 Write Speed: 4x
I 17:38:14 Link Size: Auto
I 17:38:14 Test Mode: No
I 17:38:14 BURN-Proof: Enabled
I 17:38:15 User Specified L0 Data Zone Capacity: 2.039.600
W 17:40:14 Layer Jump Recording Disabled!
W 17:40:14 Cannot set the layer break position when burning DVD-R DL media in DAO mode.
I 17:40:14 Filling Buffer...
I 17:40:16 Writing LeadIn...
I 17:40:31 Writing Image...
I 17:40:31 Writing Layer 0... (LBA: 0 - 2092895)
I 17:54:28 Writing Layer 1... (LBA: 2092896 - 4044582)
I 18:07:36 Synchronising Cache...
I 18:10:15 Operation Successfully Completed! - Duration: 00:32:00
I 18:10:15 Average Write Rate: 4.977 KB/s (3.6x) - Maximum Write Rate: 5.579 KB/s (4.0x)



First Physical Sector of Data Area: 196.608
Last Physical Sector of Data Area: 16.566.527
Last Physical Sector in Layer 0: 2.289.503

Layer 0 Sectors: 2.092.896 ( 51,75% )
Layer 1 Sectors: 1.951.696 ( 48,25% )



If I calculate, the result is:

LBA of the VOB (VTS_01_1.VOB): 249985
Start sector of the Cell: 1842911

249985 + 1842911 = 2.092.896



The test in Panasonic is still pending.

[LIGHTNING UK!]

Seeing as how 2.039.600 and 2.092.896 don't match, I'd say there is a problem somewhere?!

Over to r0lZ now for this one as he can explain his app a lot better than I can ;)

[r0lZ]

Tobi, are you sure you have correctly set 2092896 in the L0 value field in the burn setup?

[[Tobi]]

I have made screenshots (step by step).

http://img296.imageshack.us/img296/4760/imgburninformationsfensterdvdr.png (http://imageshack.us)


http://img18.imageshack.us/img18/3720/burnsetupfrdvdrdl4dc.png (http://imageshack.us)


If the problem gets away...

cell sector in PgcEdit + pad for VIDEO_TS.VOB ?
2039593 + 53303 = 2092896

Say to me sometimes please what is wrong.

[r0lZ]

I don't know! What are the symptoms? There is no error message in the ImgBurn log, so I guess it should work.

Could you post also a screenshot of the layer-break cell selection dialog (with the right cell selected?) I am interested to see the values at the top of this screen.

[[Tobi]]

Here it is...

http://img33.imageshack.us/img33/2564/setzendeslayerbreaksdvdrdl6fg.png (http://imageshack.us)

[LIGHTNING UK!]

Well it all looks ok to me!

Must just be that PgcEdit is passing the 'Sectors in L0' value rather than the 'Real position of layer break on DL DVD-R' value.

[r0lZ]

That's right. I just found the bug. It is fixed now.

BTW, there is also another bug in the GUI only. The 'Real position of layer break on DL DVD-R' is too high by 1. It should be 2092896. It is that number that is now passed to ImgBurn when a -R is burned.

[LIGHTNING UK!]

Oh right, I wasn't sure if that was displaying the value in terms of LBA or number of sectors. I know it can get confusing sometimes as I think I have both dotted around my program ;)

The value you're passing is the number of sectors in L0, but as LBA starts from 0, it's also what would then be the first LBA on the L1.

I'm sure the program would have moaned at that value anyway because it's not a multiple of 16 - so no harm would come to the poor (expensive) DVD-R DL disc! lol

[[Tobi]]

I'm sure the program would have moaned at that value anyway because it's not a multiple of 16 - so no harm would come to the poor (expensive) DVD-R DL disc! lol

Which program would have moaned?
Could you explain it?

By the way, the two euros were worth a test. I give to whole later one more chance.


Thanks

[r0lZ]

Tobi, if you want to test again with the same version of PgcEdit, I suggest you create the ISO, but don't launch ImgBurn from PgcEdit. Load the ISO in ImgBurn and either let the program decide where to put the LB, or set it manually to 2092896.

[LIGHTNING UK!]

ImgBurn would have moaned if the user specified LB wasn't a multiple of 16.

[[Tobi]]

Tobi, if you want to test again with the same version of PgcEdit, I suggest you create the ISO, but don't launch ImgBurn from PgcEdit. Load the ISO in ImgBurn and either let the program decide where to put the LB, or set it manually to 2092896.

Thanks, I try it.

ImgBurn would have moaned if the user specified LB wasn't a multiple of 16.

A check for the LB (from PgcEdit) and the risk would be clearly minimized.

Is not probably possible? (friendly asking)

[r0lZ]

The LB sector passed to ImgBurn is always a multiple of 16.
It's only in the interface for DL DVD-R, that a wrong LB, incremented by 1, was displayed.
The main bug was that the LB computed for DVD+Rs was always passed, regardless of the state of the Media Type button. But, of course, it's also a multiple of 16.

[uroscar]

Is there any way to change the booktype on a DVD+R DL that you have already burned?

Thanks

[ron spencer]

no it is not possible to change it

[mazafaka]

A new question for r0lZ )
Why it is not possible to set layer break as on pressed DVD?

[lrosado]

I have a question if all I do is Rip with DVDDecrypter, remove the FBI warnings only, and then use IMGTool Classic to create the ISO, then burn with IMGBurn, will I run into the layer break problem? Do I have to go through PGCEdit and create a new layer break before burning? I have done this this way already and the layer break in the original IFO and the Backup IFO is in the same place. Or is this wrong? Havent tried this on my standalone yet.

[r0lZ]

Yes, you have to use PgcEdit.
It is not sufficient to clear the seamless flag on the layer break cell. The ISO must also be properly formatted, so that the layer break cell starts at the right place. ImgTool classic cannot do that.

[lrosado]

I always thought if you leave the disk alone you didnt need to worry about the layer break. Thats why I didnt think removing small FBI warnings would mess up the layer break. What about if I just do an ISO image without changing anything, would I still need to use PGCEdit?

[r0lZ]

No, in this case, you should be able to burn the ISO image directly. This is a true 1:1 image, and, if you use DVD Decrypter to create the image, a MDS file is also created with the layer break position.

[lrosado]

So something as small as the FBI warnings would affect the layer break? I just played the burnt image in two different standalone DVD players with no problem. Cant DVDDecrpter create an .mds file off the new image you create to make sure the layer break isnt moved?

[r0lZ]

Even if there are no changes in the sizes of the files, when you save the DVD, the VTS pointers are computed again, from scratch. Often, those pointers will be different than in the original. Since they are used to inform the burning app on how the files must be layered out in the ISO, a minimal change in those pointers will move the layer break position.
The layer break must be at a precise position. If it is moved, the burning application will not be able to use that cell any more, and will probably use another one (if it finds another suitable cell), or will burn a coaster.
The job of PgcEdit is to recompute those VTS pointers so that the cell you have selected is positioned correctly. MKISOFS is a good program: it looks in the IFOs to use the right cell, and position it correctly in the ISO. ImgBurn, also an excellent program, can then switch to layer 1 when needed.

Nero is not suitable to burn DL-DVDs, unless you burn a 1:1 image, because it recomputes the VTS pointers. The layer break is placed at the position it selects, instead of the position requested by the user!

Of course, when you rip a 1:1 image of the original DVD, the files are not moved, and the VTS pointers not modified. You can therefore burn it directly on a DL DVD+R, including with Nero.

But note that you MUST rip your DVD in file mode and use PgcEdit to burn a DL DVD-R, because the -R (crappy) technology is not compatible with the standard position of the layer break. It must always be placed at the very end of layer 0. It's not compatible with a pressed DL-DVD, where the layer break is usually near the middle of the compilation. The +R technology has not this limitation.