Burning DL media with PgcEdit

[frank]

I'm very happy, with the help of rOlZ we CAN implement the DL burning function into PgcEdit - THE BEST DVD EDITOR! :)If it is possible to add this feature in PgcEdit, I will be happy to do it.Some information about Pre-mastering LB you can find here http://www.mediachance.com/dvdlab/Helppro/layerbreak.htm
and at GEAR homepage.
Attention! The infos about DVD+R DL from mediachance and the LB calculation from GEAR are wrong.
I'm successful working with Philips DVD+R DL media.

The Rules
The file system layouter has to make sure

1. that L0 >= L1 or L0 > 1/2 the total iso sectors
L1 has a spiral track in the OPPOSITE direction of L0. (OTP = opposite track path).
This prevents the laser on L1 from acrossing the inner radius of the DVD.

Lead-out is padded (L1=L0) by the burning application for a continuous smooth read-out, so the reading laser on L0 has fully the same reflexion conditions.
DVDdecrypter makes it right!!

2. that the Layer Break (LB) aligned on cell boundary and at DVD ECC block boundary of 32KB. Every 16. block is an ECC control block.
-> LB address = cell address evenly divisible by 16.

Case 1: ic/2 <= LB <= dvd/2
ic = iso compilation size
L1 is padded by DVDD until L0 = L1.

Case 2: ic - dvd/2 <= LB <= ic/2
L0 is padded by PgcEdit to move LB lower than ic/2.
p = padding sectors

Comparing L0 with L1 we get
p + LB = ic - LB -> p = ic - 2 LB
p + LB <= dvd/2

The real Layer Break LB' in that case
LB' = L0 = p + LB = ic - LB

LB' has to be aligned according rule 2.


The procedure for PgcEdit

1. Set Layer Break Point in PGC Editor manually.
Search for a good cell with the help of preview.
Look for a chapter point.
LBcell = Entry VOBU sector > 1/2 total sectors
Note that LBcell refers to the start sector of vts title Vobs. (Fully mistake in GEAR!!! They refer to menu vob)

2. Make iso file. Launch ISObuster and look for the start LBA of the VTS title (point A) that includes the LBcell,
or PgcEdit: Calculate point A according to the ISO layout.
LB = A + LBcell

3. Calculate the file shift
Rule 2: x = LB/16

Example:
When we get x = 182543.3125, which is not an even number, then
we find that we are 0.3125 x 16 = 5 sectors past the start of an ECC block.
We have to shift the LB to the starting sector of an ECC block.
shift = 16 - 5 = 11.

4. To move the LB we need to move all of the files in the ISO by shift = 11.
But, hehePgcEdit increases the Last Sector of VMG/VTS field (at offset 0x0C in each IFO file). MKISOFS then places the data so that the next file starts at the right offset. Then PgcEdit has to fill field 0x0C of VIDEO_TS.IFO with shift added (but not in the bup, that would double the shift). Current mkisofs -dvd-video has no option to shift the starting sector of filesystem.

Create ISO.
We can test with ISObuster: All LBA starting from VIDEO_TS.VOB or VIDEO_TS.BUP have the shift added.

5. PgcEdit sets the Layer Break LB (sectors in L0) in DVDdecrypter ISO write mode.

6. For compatibility change Book Type in DVDdecrypter to DVD-ROM for DL media.

7. Burn ISO.

:)

Regards
frank

[FilipeAmadeuO]

That´s a nice guide.
But it would be great if PGCEdit sugested an layer break point and then created the iso file with the mds for dvddecrypter burning.
That would be a very nice feature.

[r0lZ]

I will see what I can do.
But I will need some other informations.

The first obscure point is the exact calculation of the alignment offset. Do I have to take into account the header added by MKISOFS? The ISO generated by MKISOFS is not the same length than images of the same DVD generated by other programs. Is it something I have to take into account?

Then PgcEdit has to fill field 0x0C of VIDEO_TS.IFO with shift added (but not in the bup, that would double the shift).I'm not sure you can put another value in the BUP file. Normally, the BUP file must be an exact copy of the IFO file. I think that his place on the disc do not matter, as the positions are probably calculated relative to the place of the IFO. Someone can confirm this point?


What is the exact capacity of a DL DVD? Is it a difference in capacity between a +R and a -R?


But it would be great if PGCEdit sugested an layer break point and then created the iso file with the mds for dvddecrypter burning.It would be great, right. :)
It should be possible to calculate the first and last cell where the LB can be placed, and also the 'best fit' one (the cell which divide the DVD in 2 almost equal parts).
I don't know the format of the MDS file for DVDD, but I suppose that it's not verry hard to generate this file automatically.

[blutach]

If I am not mistaken ImgTools Classic has recently come out with a new version (0.91.5) which has DL ISO making capabilities.

Certainly, DVD Decrypter can position the LB by just having the user nominate how many sectors he wants in layer 0.

Regards

[FilipeAmadeuO]

But using ImgTools Classic for creating the ISO, the IFO file is not modified for generating the layer break in the exact point that it will be.
The way to do it it by generating an ISO file and the MDS and burning with DVD Decrypter.

It would be great is PGCEdit would do it

[r0lZ]

Yes, but it's not so simple.
I have still some questions.

How to deal with DVD-ROM files? Are they added at the beginning of the compilation, on L0, or at the end, on L1?

Is it possible to place the LB in a menu domain? (I suppose so.)

Reused cells might be a big problem. Is it legal to have, say, a cell on L0, if this cell is also called from another PGC, after (or before) some cells on L1?

[blutach]

@rolz - DVD_ROMs are definitely at the end on L1.

I think the LB can be in a menu, in fact, that might be preferable. Of course, the way most movies are organised, the LB is dead smack in the middle of the flick. But in episodic DVDs, there's no resaon, AFAIK, tat it can't be at the start of an episode.

As for re-used cells, good question! You wouldn't want the pause every time, would you?

Regards

[blutach]

But using ImgTools Classic for creating the ISO, the IFO file is not modified for generating the layer break in the exact point that it will be.
The way to do it it by generating an ISO file and the MDS and burning with DVD Decrypter.

It would be great is PGCEdit would do itIf you have an ISO, DVD Decrypter can generate the MDS, with the required LB info.

@r0lZ - perhaps an email to LUK! may be in order?

Regards

[FilipeAmadeuO]

DVD Decrypter can generate an MDS file but it do not uses the layerbreak.
It simply divides the dvd into two parts (i think is how it work)

[frank]

Do I have to take into account the header added by MKISOFS?Yes, but it's already included at point A. See procedure section 2:
Calculate point A according to the ISO layout, or we have to read it from a first iso creation (without the shift, as GEAR does).
LB = A + LBcell

We need the first loading address A0 of files to move, usually the LBA of VIDEO_TS.IFO. It depends from the ISO creating program and headers.
MKISOFS mostly sets A0 = 283. Because MKISOFS doesn't allow specifying that (GEAR does it, 640 + shift), we only can move files after VIDEO_TS.IFO using the tricky method.
I'm not sure you can put another value in the BUP file. Normally, the BUP file must be an exact copy of the IFO file. You are right. :thanks:
A more clean solution is to create a shifting VIDEO_TS.VOB, or blowing up an existing one by the requested shifting blocks (black frames).
The LBA of VIDEO_TS.BUP represents the start point A0, that has to be moved to
A1 = A0 + shift
Then all files after this point are moved by MKISOFS, and LB is in the right position.
LB = A + LBcell + shift
How to deal with DVD-ROM files? Are they added at the beginning of the compilation, on L0, or at the end, on L1?Ohh... I never used that. That files are used by the iso file system on a PC. Everyone who wants to backup all crappy features should use DVDdecrypter's iso read/write option, and automatic LB setting.
Is it possible to place the LB in a menu domain? (I suppose so.)Yes. Rule 2: Cell boundary... Why not a menu?
Is it legal to have, say, a cell on L0, if this cell is also called from another PGC, after (or before) some cells on L1?There is only ONE Layer Break with seamless playing at end of L0. All other laser movings through the layers produce a player stop because of head positioning. But they work.
What is the exact capacity of a DL DVD? Is it a difference in capacity between a +R and a -R?Not much.

Parameters of a DVD+R DL (shown by DVDdecrypter):
PHILIPS-CD2-00
Free sectors: 4 173 824 = 8 547 991 552 Bytes = 7.96 GBytes
Sectors in L0:2 086 912 --- 2 074 496 for DVD-R DL (GEAR)
First phys. sector of data area: 196 608
Last phys. sector in L0: 2 283 519

So we get common values for DVD+R DL and DVD-R DL.
Free sectors: 4 148 992
Sectors in L0:2 074 496

Attention! The capacity of a pressed DVD-ROM is greater than the capacity of a burned DVD+/-R DL.

[r0lZ]

5. PgcEdit sets the Layer Break LB (sectors in L0) in DVDdecrypter ISO write mode.
How should I do that? As you know, DVD Decrypter's site is closed, as well as the support forum. I don't find the info on how to pass the LB sector number to DVD Decrypter. Please help!

[FilipeAmadeuO]

It´s possible to define the layerbreak in DVD Decrypter (Settings - ISO Write mode - Layer Break).
The only thing that PGCEdit has to do is to tell in which sector is the layer break on the ISO.
About the MDS file i don´t know how is it done. Maybe someone else....

[frank]

DVD Decrypter's site is closed, as well as the support forum.Bad news.
I thought there are some CLI commands.
Let's google... or post in the burning forum?

BTW: I never used MDS files to burn the PgcEdit iso with DvdDecrypter.

[r0lZ]

I've found a description of the MDS file format here (http://developer.berlios.de/docman/display_doc.php?docid=840&group_id=2545). Unfortunately, seems it has no provision for the layer break information.

But I use now another method: the layer break value is written in the setups of DVD Decrypter directly in the registry. This way, everything is automatic, and you will be able to launch the ISO creation followed directly by the burn process from PgcEdit. (This method works only with the standalone executable, because the function to access the registry is not present in the source-only distribution of PgcEdit).

Anyway, thanks for your help.

[FilipeAmadeuO]

Excelent. Please post the new version, si we can try it.
Thanks for your excelent work

[r0lZ]

If you really wants it, here it is (http://www.videohelp.com/~r0lZ/pgcedit/beta/PgcEdit_winexe_0.6.0beta2.zip) . But take care. This beta has not been tested carefully. Don't blame me if you burn a coaster...

[FilipeAmadeuO]

How can it be done ? I´m trying Burn DVD/Create ISO options and it gives an error. Do PGCedit sugests and ideal layer break position or does change the IFO automaticaly ?

[r0lZ]

How can it be done ? I´m trying Burn DVD/Create ISO options and it gives an error. Do PGCedit sugests and ideal layer break position or does change the IFO automaticaly ?
What error did you got? Please report it here. It's important for me!

PgcEdit display all the cells that are within the layer break position range. It hilites in green the PGCs that are good candidates for the layer break. Dark green: Cell 1 of the PGC - it's the best choice. Light green: Cells that have already a non-seamless flag - It's probably the position of the original LB. You may preview the cells. You have to select the cell you want.

Then, the seamless flag is removed on the selected cell, and the DVD is saved, with an offset to store the VOB files so that the selected cell begins at an error correction bloc boundary. The layer break sector number is communicated to DVDD by the registry (if the option to burn the DVD with DVDD is ON), and, optionally, you have the option to copy this number in the clipboard.

Finally, the ISO is created, and the burn process is started.

[FilipeAmadeuO]

Here is my log message :

mkisofs log for DVD "TEAM_AMERICA"
From: "C:\TEAM_AMERICA"
DVD-TEXT General Name: ""
Provider ID: ""
Number of VTS: 7
Output file: "C:\TEAM_AMERICA.ISO"
Volume label: "TEAM_AMERICA"



Error creating ISO:
child killed: SIGABRT

Test command was:

"C:\DVD Copy\PGCEdit\bin\mkisofs.exe" -dvd-video -print-size -V "TEAM_AMERICA" -p "PgcEdit" -m "PgcEdit_backup*" -m "MenuShrinkBackup*" -m "VobBlanker_backup*" -m "Copy of *" "C:\TEAM_AMERICA"

[r0lZ]

Strange. I have changed nothing in this part of the burn function.
This error comes from a safety check I do before generating the ISO. I ask mkisofs to report the size of the DVD. If it finds an error, it should say what's wrong. But in this case (SIGABRT), it crashes. Maybe there is something illegal in your DVD, or maybe you've found a bug in MKISOFS. I really don't know. Anyway, this error is not related to DL burning, since everything related to DL comes after this part.

Please try to burn another DVD, and let me know.

[r0lZ]

Beta 3 is here (http://www.videohelp.com/~r0lZ/pgcedit/beta/PgcEdit_winexe_0.6.0beta3.zip).

Fixes a bug in the calculation of the minimum valid sector for the layer break.

@FilipeAmadeuO: Still no idea for your problem with mkisofs.

[r0lZ]

"C:\DVD Copy\PGCEdit\bin\mkisofs.exe"I see now that you have moved mkisofs.exe in the bin subfolder of PgcEdit. OK. But you must also copy cygwin1.dll in the same folder, or mkisofs will not work. Perhaps it's the problem ?

[blutach]

Here is my log message :

mkisofs log for DVD "TEAM_AMERICA"
From: "C:\TEAM_AMERICA"
DVD-TEXT General Name: ""
Provider ID: ""
Number of VTS: 7
Output file: "C:\TEAM_AMERICA.ISO"
Volume label: "TEAM_AMERICA"



Error creating ISO:
child killed: SIGABRT

Test command was:

"C:\DVD Copy\PGCEdit\bin\mkisofs.exe" -dvd-video -print-size -V "TEAM_AMERICA" -p "PgcEdit" -m "PgcEdit_backup*" -m "MenuShrinkBackup*" -m "VobBlanker_backup*" -m "Copy of *" "C:\TEAM_AMERICA"@r0lZ - this error seems similar to the one I emailed you about a week ago. The rountine doesn't even start. I did not get that child killed Sigabrt message though.

@filipe - try moving all the subfolders (PgcEdit_backup, VobBlanker_backup etc) out of the project folder and try again. Make sure you have also installed cygwin.dll

Regards

[FilipeAmadeuO]

I havent copied the cygwin.dll so it can be the problem. Gonna try tonight

[frank]

:D :D :D :thanks: to rOlZ
I'll test tonight.

[FilipeAmadeuO]

The creating of ISO works OK when i copied the cygwin.dll
Now i have to try to copy to a DVD+R DL.
Thank you very much.

[frank]

There is really an error in the minimum valid sector of beta 3.
But Layer Break calculation is OK. :)

I created an ISO and viewed with ISObuster the LBAs.

The total number of sectors in my ISO is 3 625 963, PgcEdit shows 3 626 104.
The difference = 141 sectors, but we are on the sure side, ok.

Then the min LB sector in ISO must be 3 626 104 / 2 = 1 813 052, PgcEdit shows 1 551 616.

That is too low.
You'll get a coaster because the returning laser on L1 acrosses the inner radius of the DVD! See rule 1.

[r0lZ]

There is really an error in the minimum valid sector of beta 3.
But Layer Break calculation is OK. :)

I created an ISO and viewed with ISObuster the LBAs.

The total number of sectors in my ISO is 3 625 963, PgcEdit shows 3 626 104.
The difference = 141 sectors, but we are on the sure side, ok.The total numbers of sectors displayed in the GUI is the compilation size, ie. the number of sectors without the padding sectors added to align the layer break cell. It should be the reason of the difference. I will verify that point.

[EDIT:] Obviously, I am wrong, since the size displayed by PgcEdit is greater than the actual size of the ISO. Strange...
Did you checked the 32K gap option before burning?


Then the min LB sector in ISO must be 3 626 104 / 2 = 1 813 052, PgcEdit shows 1 551 616.

That is too low.
You'll get a coaster because the returning laser on L1 acrosses the inner radius of the DVD! See rule 1.Well, your method was used in beta 2, but seems it's wrong.
It is theorically possible to fill the whole DVD-9, right? So, if you want, you can have L1 = whole disc size / 2, and L0 = compilation size - (whole disc size / 2), plus the padding sectors. In your case, this is:
L1 = 4 148 992 / 2 = 2 074 496
L0 = 3 626 104 - 2 074 496 = 1 551 608
Since 1 551 608 is not divisible by 16, the first valid sector is 1 551 616.

The gap is added just after VIDEO_TS.VOB (or between VIDEO_TS.IFO and VIDEO_TS.BUP if there is no VMGM VOB), and is therefore always on L0. The requirement of L0 >= L1 is therefore respected.

For example, if you select a cell that starts at original sector 1 551 616, the layer sizes are finally:
L1 = 2 074 496
L0 = 1 551 616 + 522 880 gap = 2 074 496
Both layers are equal.

Am I right?

[jinjin_jp]

Hello. I'm at first in this forum.

There is a information which is the method on the same concept(if could correct IFO before DVDDecrypter writing).
*ttp://yaki2fan.hp.infoseek.co.jp/dec_dl.html (Japanese)

The point is to correct ifo which controls the start sector of some file by IfoEdit ,for make appropriate blank sectors between appropriate some files.
(In this case, End sector of 3.Cell of VTS_02, is 2,074,138. and we want this value to 2,074,144.
correct IFO: VIDEO_TS.IFO,VMG_PTT_SRPT,Title_1:Title set starting sector +6. and the same Title_2,3,4...
So made 6 blank sectors after VIDEO_TS.BUP.)

flow of the method,
1.create ISO file by ImgToolClassic
2.mount by DaemonTools
3.examin LBA(sector) of each file by DVDDecrypter
4.asuume which VOB file has LayerBreakPoint
...in this case,
....LBA(sector) of the first file(VIDEO_TS.IFO) is 287(*1) to 290
....total file size is 8,252,915,712 bites, so 8,252,915,712/2,048 = 4,029,744(*2) sectors
....the sector of LayerBreakPoint would be over 2,015,015(*3)(=(287(*1)-1+4,029,744(*2))/2)
....LayerBreakPoint would be in VTS_02_1.VOB , because it's LBA(sector) is 1,912,532(*4) to 2,436,818
5.examin the end sector of each Cell of VTS_02_*.VOB by IfoEdit(VTS_C_ADT) or PgcEdit(Edit PGC)
6.asuume which Cell should the last of layer 0
...in this case,
....the start sector of VTS_02_1.VOB is 1,912,532(*4)
....the end sector of assumed Cell should be over 102,483(*5)(=2,015,015(*3)-1,912,532(*4))
....the last cell of layer 0 would be Cell 3 , because the end sector(VTS_C_ADT) of Cell 3 is 161,605(*6) (>102,483(*5))
7.correct Cell type for LayerBreaPoint by IfoEdit(VTS_PGCITI) or PgcEdit(Edit PGC)
...in this case,
....correct Cell type of Cell 4(=3+1) , 8 to 0 , or 10 to 2
8.calculate the value setted for DVDDecrypter(Sectors in L0)
...in this case,
....the end sector of Cell 3 of VTS_02_1.VOB is 2,074,138(*6)(=1,912,532(*4)+(161,605(*6)+1)
....sectors in L0(DVDDecrypter) must be over 2,074,138(*6) ,and divisible by 16
....so sectors in L0(DVDDecrypter) is 2,074,144(*7)(=129,634 x 16)
9.correct IFO for adjust the end sector of Cell 3 of VTS_02_1.VOB is 2,074,144(*7) ,by IfoEdit
...in this case,
....2,074,144(*7) - 2,074,138(*6) =6 sectors ,so make 6 blank sectors after VIDEO_TS.BUP
....correct IFO (VIDEO_TS.IFO,VMG_PTT_SRPT,Title_1:Title set starting sector) add 6 ,and the same Title_2,3,4...
10.confirm blank sectors by DVDDecrypter
...in this case,
....LBA(sector) of VIDEO_TS.BUP is 291 to 294
....LBA(sector) of VTS_01_0.IFO is 301 to 303 ,so created 6 blank sectors(295 to 300)
11.create ISO file by ImgToolClassic
12.write ISO file by DVDDecrypter(ISO Write Mode)

I hope if automatically calculated and corrected IFO like this.
But the problem is unknown the start sector of VIDEO_TS.IFO before create ISO at first.

I'm sorry not good at English.

[frank]

Did you checked the 32K gap option before burning?It was off.
BTW: What about to increase the 10k dummy VOBs in PgcEdit to 32k? Then we can forget this option, and any burning program does it right.
The gap is added just after VIDEO_TS.VOB (or between VIDEO_TS.IFO and VIDEO_TS.VOB if there is no VMGM VOB), and is therefore always on L0 :cool: That's our very cool way out!
I've read last year a request to MKISOFS (cdrtools) developer to add that loading sector shift option but he didn't, he had to release his rc without newer options. Maybe this option comes in the next time.
It is theorically possible to fill the whole DVD-9, right? So, if you want, you can have L1 = whole disc size / 2, and L0 = compilation size - (whole disc size / 2), plus the padding sectors.Oh no. That's not the way how DVDD writes DL media![deleted, see rOlZ below] L0 is the first layer that the laser writes towards the outer area. Usually DVD-VIDEO media have OTP tracks. At LB the laser breaks into L1 and RETURNS to the inner radius. Logical sector adresses (LBA) are linear counted until LB and then continue on L1 until max LBA is reached near the INNER radius! I think the LBA management is in that first physical data sectors of layers that we can't access. The iso file is written by DVDD without a gap. Imagine it's folded on LB. Padding sectors are added automaticly by DVDD to the Lead-out (on L1), so L0 = L1.
In beta 3 you would produce really L1 > L0 --> coaster.[deleted, see rOlZ below]
If you want filling up L0 then you can select the LB near L0max = 2 074 496. But what follows? L1 is much shorter and DVDD has to write more padding sectors until the laser reaches track 0 (begin) of DVD. Not to be recommended. Data errors are greater on the end of disk and a waste of time caused by padding.

Understand me?

[r0lZ]

In beta 3 you would produce really L1 > L0 --> coaster. No, since PgcEdit adds the padding sectors in the ISO, after VIDEO_TS.VOB, in L0.
The user must have the largest choice of cells to place the LB. If he choose the first sector in the list, the pad after VIDEO_TS.VOB will be huge, and L0 and L1 will be equal. OK, it's not recommended to write near the outer edge of the media, but it can be done, and PgcEdit must support that.

With this method, if the user selects a cell before <total compilation size> / 2, the two layers will be exactly equals in the ISO. Why could it not work?

Of course, if the cell is after <total compilation size> / 2, your method is used, and DVDD will pad L1 so that it is the same length than L0. Anyway, if he choose the last cell, the end of L0 (and therefore also the start of L1) will also be near the outer edge.

Note that I have changed the calculation method of the first valid sector when I saw an unmodified DVD with the original layer break position largely before the first valid sector. It was impossible to place it at the original location! (Thanks to Blutach for pointing me in this direction.)

[frank]

Ok, will test again. But I remember that I had no big gap after the TS.VOB.

I only generate the iso and view it. I must burn separately because of Book Type changing.

[r0lZ]

@jinjin_jp: Thanks for your help, and welcome to the forum.

I will try your method, but IMHO, it is equivalent to the method I have implemented, although the padding is placed elsewhere.

[r0lZ]

Ok, will test again. But I remember that I had no big gap after the TS.VOB.

I only generate the iso and view it. I must burn separately because of Book Type changing.I have to verify that also. Maybe the pad is wrong.

Burning the ISO separately should not be a problem.

[frank]

Hehe, you are right! Where was my math brain... :rolleyes:
I see, we can shift the LB < total compilation size / 2 by filling up L0.

I didn't select such lower cell but will test tonight.
Now I need a beer.

[frank]

:( Sorry, padding doesn't work in beta 3 for cell < <total compilation size> / 2

total compilation size 3 626 104 + 10 = 3 626 114
LB = L0 = 1 787 136

L1 = 1 838 978
DVDD outputs error L1 > L0!

Only shift pad = 10 is done.
No padding after VIDEO_TS.VOB, the total compilation size has NOT been increased.

The gap is added just after VIDEO_TS.VOB (or between VIDEO_TS.IFO and VIDEO_TS.VOB if there is no VMGM VOB)You mean between VIDEO_TS.IFO and VIDEO_TS.BUP, right?

[FilipeAmadeuO]

Has anyone tried RecordNow 7.3 ?
It inserts the layerbreak automaticaly and it inserts Padding sectors automaticly to the end of DVD on L1, so L0 = L1.
Also i think the best way is to sugest the ideal layerbreak place, so LO is bigger and very close to L1.

[jinjin_jp]

@jinjin_jp: Thanks for your help, and welcome to the forum.

I will try your method, but IMHO, it is equivalent to the method I have implemented, although the padding is placed elsewhere.

Thanks for comment to my post, and I'm very glad for receive reply from author of PgcEdit directly, I frecuently use PgcEdit very useful.

In above my post, the example is about create blank sectors between VIDEO_TS.BUP and VTS_01_0.IFO.
And there is another method which is about create blank sectors between VIDEO_TS.VOB and VIDEO_TS.BUP like PgcEdit, at '*ttp://yaki2fan.hp.infoseek.co.jp/dec_dl.html'.
...(a)correct IFO : VIDEO_TS.IFO , VMG_PTT_SRPT , Title_1:Title set starting sector and the same Title_2,3,4... , +6.
...(b)and add correct IFO :VIDEO_TS.IFO , VMGM_MAT . Last Sector of VMG , +6.
So made 6 blank sectors after VIDEO_TS.VOB.

I think the meaning of each IFO correction.
(a)the start sector of VTS_01_0.IFO ,when the start sector of VIDEO_TS.IFO is 0.
(b)the end sector of VIDEO_TS.BUP ,when the start sector of VIDEO_TS.IFO is 0.

And more,we will be able to create after another file by correct IFO.(but I've not confirmed actually)
(1)VIDEO_TS.IFO , VMGM_MAT . Last Sector of VMG ,
.....which means the last sector of VIDEO_TS.BUP ,when the start sector of VIDEO_TS.IFO is 0.
(2)VIDEO_TS.IFO , VMGM_MAT . Last Sector of VMGI ,
.....which means the last sector of VIDEO_TS.IFO ,when the start sector of VIDEO_TS.IFO is 0.
(3)VIDEO_TS.IFO , VMG_PTT_SRPT , Title_*:Title set starting sector (VTS_** icludes Title_*) ,
.....which means the start sector of VTS_**_0.IFO ,when the start sector of VIDEO_TS.IFO is 0.
(4)VTS_**_0.IFO , VTSI_MAT , Last Sector of VTS ,
.....which means the last sector of VTS_**_0.BUP ,when the start sector of VTS_**_0.IFO is 0.
(5)VTS_**_0.IFO , VTSI_MAT , Last Sector of VTSI ,
.....which means the last sector of VTS_**_0.IFO ,when the start sector of VTS_**_0.IFO is 0.
(6)VTS_**_0.IFO , VTSI_MAT , Start of VTSM_VOBS ,
.....which means the start sector of VTS_**_0.VOB ,when the start sector of VTS_**_0.IFO is 0.
(7)VTS_**_0.IFO , VTSI_MAT , Start of VTSTT_VOBS ,
.....which means the start sector of VTS_**_1.VOB ,when the start sector of VTS_**_0.IFO is 0.

But I wonder one thing about (6).
In the case the size of VTS_**_0.VOB is 0KB ,the value(6) of original IFO(for example Matrix 1, Time Machine, A.I.) is 0.
After GetVTS by IfoEdit ,this value change to the size(sector) of VTS_**_0.IFO (I remenber the same about PgcEdit).
the other hand after CorrectDVDsectors by DVDFab(=DVDToolbox),this value doesn't change and same as original .
Is which right? Does anyone have information about this?

I'm sorry not good at English.

[r0lZ]

:( Sorry, padding doesn't work in beta 3 for cell < <total compilation size> / 2

total compilation size 3 626 104 + 10 = 3 626 114
LB = L0 = 1 787 136

L1 = 1 838 978
DVDD outputs error L1 > L0!

Only shift pad = 10 is done.
No padding after VIDEO_TS.VOB, the total compilation size has NOT been increased.

You mean between VIDEO_TS.IFO and VIDEO_TS.BUP, right?I know. I am currently working on this bug. But it's late, here, ane next beta will be for tomorrow.

And, yes, I mean VIDEO_TS.BUP. (error fixed in previous post)

[r0lZ]

Has anyone tried RecordNow 7.3 ?
It inserts the layerbreak automaticaly and it inserts Padding sectors automaticly to the end of DVD on L1, so L0 = L1.
Also i think the best way is to sugest the ideal layerbreak place, so LO is bigger and very close to L1.The good point for PgcEdit is that it will NOT insert the LB automatically: you have the choice of where to put it, with preview.

The layer break should effectively be placed near the middle of the compilation, but there are cases where a better place can be found.
In beta 4, PgcEdit sets the default layer break like this:
- If a cell 1 of any PGC exists in the valid range, it is selected as it's the best choice, since the LB will not be noticed.
- Else, if there is already a non-seamless flag on a cell, it is selected, as it's probably the original layer break location, or the one that has been set previously by the user.
- Else, if the VOB ID change once (and only once), then the first cell with the new VOB ID is selected, as a change in VOB ID often indicate the location of the original layer break.
- Else, the cell that is near the middle of the compilation is selected. Note that this cell do not need to be after the middle, as explained above.

In fact, it's a little bit more complicated, because a good cell can be reused in another PGC, and not be a good one in that PGC. But it's the idea.

[r0lZ]

@jinjin_jp: Sorry, I don't understand.
Do you mean that the value of Start of VTSM_VOBS in VTSI_MAT is wrong if the VOB file is empty? I don't think so.

[jinjin_jp]

@jinjin_jp: Sorry, I don't understand.
Do you mean that the value of Start of VTSM_VOBS in VTSI_MAT is wrong if the VOB file is empty? I don't think so.

Sorry, I can't judge wrong or not.
But I suppose it's wrong from my experience following.

2 or 3 years ago, I found some of DVD can't play normally by PC player after getVTS by IfoEdit0.95, but no problem before getVTS.
Common point is to have 0KB VTS_**_0.VOB.(these DVD are Matrix 1, Time Machine, A.I.)
..Matrix 1(VTS_01 and 03), Time Machine(VTS_01), A.I.(VTS_01 and 03) are 0KB.
And about Matrix 1,main menu and main movie in VTS_02 can played normally, but when jump from menu to extras in VTS_01 or 03,display is disappeared.
The other hand, getVTS(CorrectDVDsectors) by DVDFab(=DVDToolbox) has no problem,
and when delete 0KB VTS_**_0.VOB, there is no problem, too.
Compare IFO, DVDFab(CorrectDVDsectors) is same as original, and getVTS(IfoEdit) is changed.

But now I am cofused.
Bcause when IfoEdit0.96 is released, I tried the same test.
Result was, IFO is changed, but no problem play by PC player.
So reinstall IfoEdit0.95 and tested, and results was no problem play by PC player.
Different from previous test results, I think somethig change except for IFO in my PC, but I can't find out.

Sorry not for usefull informetion.

[FilipeAmadeuO]

jinjin_jp - That problem is a weel known bug of Ifoedit. The best way is to delete the 0Kb file and do Get VTS sectors again.

Rolz - Please do not forget that some VTS´s use repeated PGC´s. Sometime ago i backup Alien 3 - special edition and record now only created the layerbreak in the longest PGC. But there is another PGC in seamless brenching that uses a major part of the vob id´s. Please insert the layerbreak in every PGC with the select VOB ID and CELL ID.

[jinjin_jp]

jinjin_jp - That problem is a weel known bug of Ifoedit. The best way is to delete the 0Kb file and do Get VTS sectors again.

Thanks for the information.
I understand.

[r0lZ]

Rolz - Please do not forget that some VTS´s use repeated PGC´s. Sometime ago i backup Alien 3 - special edition and record now only created the layerbreak in the longest PGC. But there is another PGC in seamless brenching that uses a major part of the vob id´s. Please insert the layerbreak in every PGC with the select VOB ID and CELL ID.
That's correct, and PgcEdit handles this situation. I do most of the tests with Shrek 2, which has main movies cells reused in 2 or 3 PGCs. To test, you can also create a new Play All title, or clone the PGC. You will see that the seamless flag is cleared in all PGCs.

But take care. The current version do not remove the old layer break(s). When burning, if the original layer break is still present, it will (probably) be selected by default, but if you select another one, you will end up with two pauses instead of one.

[r0lZ]

@jinjin_jp: Furthermore, PgcEdit now detect when a VOB is present but empty, and offer to delete it. It's the safest way to handle this problem.

[FilipeAmadeuO]

Rolz - Why PGCEdit don´t remove the old layer break ? Can you include in the layerbreak screen an option to remove old layerbreaks ?

[jinjin_jp]

@r01Z: It's good method and feature, thanks.
and also when transcording in full disc mode ,0KB VTS_**0.VOB files are deleted.(I tested about DVD2one and DVDShrink)

But there is a information about InterVideoDVDCopyPlatinum,it newly creates 0KB VTS_**0.VOB files .in spite of original doesn't have.
*ttp://www.geocities.jp/dvd_freedom/jikkenshitsu/page010.html
(bottom figure of the page)

[frank]

The good point for PgcEdit is that it will NOT insert the LB automatically: you have the choice of where to put it, with preview.Agree!!! And you can shift the LB to lower LBAs than other pay ware because PgcEdit can insert padding sectors in L0 before the LB. The features beat all known burning programs. :cool:
I can show you the damned coasters produced by Nero!

I'm not sure what iso creating program jinjin_jp used.
AFAIK there was a bug in earlier versions of MKISOFS in DVD-VIDEO iso with unused 0 byte menu vobs. MKISOFS created by Jörg Schilling is used in his CdrTools and in ImgToolClassic. Latest stable release of CdrTools is v2.01.

[jinjin_jp]

I'm not sure what iso creating program jinjin_jp used.
AFAIK there was a bug in earlier versions of MKISOFS in DVD-VIDEO iso with unused 0 byte menu vobs. MKISOFS created by Jörg Schilling is used in his CdrTools and in ImgToolClassic. Latest stable release of CdrTools is v2.01.

We can use ImgToolClassic to create ISO file which has blank sector according to IFO corrected.
(old version of ImgTool(Classic?) didn't create blank sectors ,in spite of IFO describe blank sectors.
I happened to find this change of feature in version 0.91.4 last summer.)

About unused 0 byte menu vobs, I've never tested with ImgToolClassic, but I think to avoid the problem by delete these files.