VobBlanker 1.6.0.6 is out

[CoNS]

Okey, looking forward to the fix. I have very high expectations of this new option once it works as intended... :)

As a third thing, are you going to fix the Get VTS sector problem when either "Process Titles" or "Process Menus" are unchecked? (you reported this bug yourself when version 1.6.0.2 was announced)

[jsoto]

Originally posted by CoNS
As a third thing, are you going to fix the Get VTS sector problem when either "Process Titles" or "Process Menus" are unchecked? (you reported this bug yourself when version 1.6.0.2 was announced) Sure. Don't worry.

jsoto

[blutach]

Originally posted by jsoto
Vers 1.6.0.2 (13-12-2004)
BugFix: Replaced/Blanked Cell and the following one is now marked as system clock discontinuity.
BugFix: Now marks as system clock discontinuity the appropiate cells when cutting PGCs
This may sound like a silly question, but why do these need to be reset? Why are they bugs, if not reset?

Regards

[jsoto]

VobBlanker does not change SCR nor PTSs. So if you replace/blank a cell (with it's own timeline) the SRC/PTSs are not continuous--> must be marked in the IFO as discontinuous.

From my point of view, it is clearly a bug, although only a few players fail.

jsoto

[TomSem]

this warning screen is not visible in vbpreview.
After running through vobrator i've found the warning screen
in vobid 9. How can i blank this vobid ?
I've tried to blank it in vobblanker but has no luck yet.

any help ?

[blutach]

@jsoto

Thanks for that. But, if, for example, you cut the credits from the last cell from say midway to end of cell, well, on entry if it was a type "8" seamless playback, should it not stay that way?

And in a full cell blanking, if set to an 8, wouldn't you want it to stay seamless?

Or is what you are saying, that a type "8" changes to a 10 (seamless and SCR reset)?

:confused:

[jsoto]

@blutach
if, for example, you cut the credits from the last cell from say midway to end of cell, well, on entry if it was a type "8" seamless playback, should it not stay that way?
Cutting the "n" cell from midway to the end will produce a discontinuity in cell "n+1", which should be marked as discontinuous. Timeline between "n-1" and "n" is still continuous, but not between "n" and "n+1". Obviously, in your example, because "n" is the last cell, there is nothing to change.

in a full cell blanking, if set to an 8, wouldn't you want it to stay seamless? Full cell blanking replaces the cell with a blank one, which has it's own (fixed) timeline. So if the blanked cell is "n" , there are two discontinuities, from "n-1" to "n" and from "n" to "n+1", so cell "n" and "n+1" should be marked as discontinuous.

@TomSem
You can locate the Vobid in the cell list (cells button, in menu or title domain), and blank the cell.

jsoto

[blueboyec]

jsoto

Keep one angle request with all references to angles updates/corrected. Would be nice to have this capability in vobblanker.

I known ifoedit can do this but I do not believe it corrects all reference to angles. I asked if all references are corrected in the ifoedit thread but had no response.

[jeanl]

Given this (http://forum.doom9.org/showthread.php?s=&threadid=86760) I think you're right, IFoEdit does not correct everything the right way...

Jeanl

[lovelegend]

so can VobBlanker replace cells with multiangle?
I saw a working guide here about using pgcdemux and vobblanker to replace the LPCM audio stream with mp2 stream, but then jsoto said something about not supporting multiangle, I'm not sure if he was talking about pgcdemux or vobblanker, and that thread is deleted...

[jsoto]

PgcDemux does support multiangle. VobBlanker doesn't.

I saw a working guide here about using pgcdemux and vobblanker to replace the LPCM audio stream with mp2 stream...and that thread is deleted...
http://forum.doom9.org/showthread.php?s=&threadid=84887

jsoto

BTW, Currently PgcDemux does not support 24 bit LPCM (nor 20 bit). I'm going to release a version supporting 24 bits soon.

[jeanl]

jsoto,
What's the difficulty in processing multiangle cells? I'm asking out of curiosity, I'm trying to understand how all this work...
Jeanl

[jsoto]

Extracting the cell / Demuxing its streams is easy, nothing special, just take care with the angle.

But muxing/stripping or replacing is not so easy. You have to:
- ILV the cell with the other angles (VOBU by VOBU)
- Adjust all multiangle pointers inside the VOB.
- Manage the appropiate bits in PGC chain (this is the easy part, I think)

In any case, may be I can support blanking or replacing (deleting the multiangle) in VobBlanker in a future. This seems feasible to me.

jsoto

[blueboyec]

Is this the same as keeping only one angle out of several. This would be great, ifoedit and dvddecryter do not seam to be correcting all the pionter after keeping only one angle. DVDremake maybe doing it right but that maybe the only thing it can do that VOBblanker in combo with pgcedit cannot do? I still have to learn how to use pgcedit.

thanks for the great program!




Originally posted by jsoto


In any case, may be I can support blanking or replacing (deleting the multiangle) in VobBlanker in a future. This seems feasible to me.

jsoto

[sweetness]

Does vobblanker still have the problem with cutting the start and end of a cell?

i guess a work around would be to cut it with dvdshrink then replace it back. that's if there's only one cell in the chapter.
OR you can extract the cell, create ifo's for it, cut with dvdshrink then replace.
i think this should work (i'm not at home right now to test this)

everytime multiangle comes up for some reason or another the same cell cutting pops back in my head.:eek:

[jsoto]

Does vobblanker still have the problem with cutting the start and end of a cell? Sorry, not sure. May be the discontinuity bits (there are two bits involved) may solve the most of the situations. I need to check this

But I'm sure the problem will be the same if replacing the cell with a dvdshrink created one. I believe what dvdshrink/IFOedit does in cutting is also done by VobBlanker. In fact, dvdshrink does not allow you to cut a part of a cell in the middle (keeping the beginning and the end of it), which is the unsolved problem in VobBlanker.

jsoto

[blutach]

@sweetness

Because of the problem jsoto mentions, I use Shrink exclusively now to cut. Interestly, it sets flags as 2, 8, 8, ..... and ends with a 2.

You may like to consider this (http://www.videohelp.com/~r0lZ/pgcedit/third_party/blutach/adding_menus_to_dvd_shrink_reauthored_dvds.htm), which IMHO, is a foolproof way of putting a menu back into reauthored shrinked disk.

Regards

[jsoto]

Originally posted by blutach
Because of the problem jsoto mentions, I use Shrink exclusively now to cut. Interestly, it sets flags as 2, 8, 8, ..... and ends with a 2.
Currently VobBlanker is seting SCR discontinuity bit in the proper way, but not the "seamless" one. It will be fixed in next version (soon)

But, do not forget shrink does not adjust the PTSs neither SCR, so it should have the same issues than VobBlanker, because both are doing (more or less) the same.

jsoto

[blutach]

loking forward to next verson Jesus :)

[CoNS]

Yep, me too! :-) Especially due to the bugs in the "Process in input folder" function... When this function works as intended, I feel like the program is close to 100 % for the blanking part of DVD editing.

[jsoto]

Here it is.

Vers 1.6.0.3 (19-12-2004)
Added: Multiple selection in VTS list
Added: Menu options to Blank all and blank auto (all except the longest PGC)
Added: Deletion of 0 bytes Menus (originals or produced)
Added: Cell type marked as seamless and non STC discontinuity (cell type=8) when replacing PGCs in all cells, except the first one.
Merged: DVDPreview code is now fully aligned with PgcEdit.
Change: Calculate num VOBIDs only once per VTS. (not a bug, but a waste of time) (*)
Change: Load/Save project optimization in the case of VTS SKIP.
BugFix: Replaced/Blanked Cell and the following one is now marked as system clock discontinuity and non-seamless (type=2).
BugFix: Now marks as system clock discontinuity the appropiate cells when cutting PGCs and non-seamless (type=2).
Added: Working in input folder: Warning if VobBlanker_backup already exists, and delete all previous video files if exists
Added: Working in input folder: IFOs of Skipped VTSs are also backed'up.
Change: Working in input folder: Final DVD size adds size of skipped VTSs
BugFix: Working in input folder: Don't try to move menus if they don't exist.
BugFix: Working in Input Folder: Sectors adjustment-> Added an adjustment step in any case.
BugFix: Working in Input Folder: Skipping VIDEO_TS (Menu) did not work.

Enjoy...

(*) Now, VobBlanker loads Gardfield in 14 seconds..
jsoto

[CoNS]

Ahh, thanks jsoto :) I just tested the "Process in Input Folder" option with a disc that caused version 1.6.0.2 to fail - and it works now.

As this option is intended for processing a smaller part of the disc only and skipping the rest, could you add some feature where the program marks the untouched material as "skip" by default? (only when using this option) As it is now, I have to go through everything manually to skip all material I'm not blanking.

It would also be nice to be able to save the checkbox settings (in an .ini file) so that the program starts up with whatever settings you usually use.

Also, could you enable previewing on cell level (in the cell window)? Like in PgcEdit.

Finally, it would be nice if the content/structure of the disc was displayed like it is in PgcEdit with all the VTS menus and titles on one list. I know that you already said that it's not gonna happen, but I can't help mentioning it again!! It would make it easier to overview the disc, to find out where the stuff you wanna process is located, and to keep track of what you marked for processing. As it is now, you can't see in the main window with the VTST list if material in the VTSM is marked for blanking or not.

These are really just small details in the big picture. Overall, the program is simply great! Thanks for your effort and thanks for sharing it. KUTGW! :)

[blutach]

Thanks jsoto for more great work.

One silly qn. Why have you stopped bundling preview.exe with your package?

Regards

[jsoto]

Originally posted by CoNS
..As this option is intended for processing a smaller part of the disc only and skipping the rest, could you add some feature where the program marks the untouched material as "skip" by default? (only when using this option) As it is now, I have to go through everything manually to skip all material I'm not blanking.
Skip is a full VTS operation. You have a "Skip all" button as well as multiple selection. I believe it is enough... Well, may be I can change the default to SKIP if you load the IFO with the option checked.
It would also be nice to be able to save the checkbox settings (in an .ini file) so that the program starts up with whatever settings you usually use. I'm thinking in store them in the registry
Also, could you enable previewing on cell level (in the cell window)? Like in PgcEdit. May be...

Finally, it would be nice if the content/structure of the disc was displayed like it is in PgcEdit with all the VTS menus and titles on one list. I know that you already said that it's not gonna happen, but I can't help mentioning it again!! It would make it easier to overview the disc, to find out where the stuff you wanna process is located, and to keep track of what you marked for processing. As it is now, you can't see in the main window with the VTST list if material in the VTSM is marked for blanking or not.Too much effort to do.

Originally posted by blutach
One silly qn. Why have you stopped bundling preview.exe with your package?
Opps. I didn't explain it... It is now included in the exe, you don't need an external application anymore.... and give the most of the credit to jeanl.

jsoto

[blueboyec]

jsoto,

Read somewhere in the tread that vobblanker automatically removes unreferenced material. DVDrebuiler always chokes in the rebuilding phase when trying to process a VTS that had its unreferenced material removed by vobblanker. Requesting that unreferenced material be automatically blanked (not remove) to prevent DVDrebuilder from choking. Hope this is possible?

[jsoto]

@blueboyec
What you ask is possible (not easy) but I cannot believe what are you saying. Unreferenced material removed by VobBlanker is unreferenced in the PGC tables of the IFO. VobBlanker also removes it from ADMAP and ADT tables (if it is there), so the final IFOs have no reference at all to this material, and DVD-RB cannot complain about it. I have many success reports of people using VobBlanker+DVD-RB (or VobBlanker+dvdshrink)

I've to confess I cannot follow DVD-RB forum (it is very active) but I usually do a search trying to find potential VobBlanker issues. What I see is some hard DVD-RB testers recomending VobBanker as a preprocess step to DVD-RB...

Please note the unreferenced material deleted by VobBlanker is completely unreferenced, so you cannot access it. There are some DVDs with other kind of unreferenced material: Cells included in PGCs not easy to play (usually you need to apply some hidden tricks to access to). This material is not deleted by VobBlanker.

However, I do believe that a bug could be somewhere in VobBlanker, producing DVD-RB to fail.

So, could you give me an example? (IFOs before and after will help)

jsoto

[CoNS]

I have used VobBlanker for preprocessing the disc before encoding with DVD-RB for some time now. I have done around 15-20 discs this way and have never experienced any problems. It's my experience that DVD-RB eats the VobBlanker output raw :)

The only error I've got using DVD-RB was a time when I tried to encode a disc which I had authored using the DVD author function in DVDShrink adding multiple titles to the disc.

[blueboyec]

jsoto,

The DVD’s that I have been having problems with are the Seinfeld series DVDs. They all seem to have unreferenced material and when DVDrebuilder tries to process (during rebuild phase) it chokes on a VTS that the unreferenced material was removed. The first three disks I tried to process after using VOBblanker, DVDrebuilder choke so I just processed the DVD with DVDrebuilder without preprocessing and all went well. I have preprocessed many DVDs with VOBblanker and have very few problems sending through DVDrebuilder.

On the 4th Seinfeld DVD DVDrebuilder choked again when it was on VTS 7 ,tried it twice; there was an unreferenced material which was removed by VOBblanker. The third time I processed this DVD with VOBblanker and skipped VTS 7 them copied the original VTS 7 to the process DVD folder and did a get VTS with ifoedit. DVDrebuilder did ok until it reached VTS 12 and it choked, unreferenced material was removed from here.

The forth time I preprocessed this DVD with VOBblanker; I skipped VTS 7, 12 and 13. These three VTS all have unreferenced material. I then moved the original VTS 7, 12, and 13 to the processed DVD folder did a get VTS with ifoedit and ran it through DVDrebuilder and all when well.

Based on the above I am assuming that removing the unreferenced material from the vts is what was making DVDrebuilder choke. Could be wrong thought? Well try to send you the before and after VOBblanker processed ifos.

I forgot that after processing DVD with VOBblanker I always use DVDshink to shrink menus and remove non English audios. Could this be the cause of the problem? Will also send you the ifos processed with DVDshrink.

Thanks for the help and the great program.

[jsoto]

I forgot that after processing DVD with VOBblanker I always use DVDshink to shrink menus and remove non English audios. Could this be the cause of the problem? I don't believe it, but if shrink was able to open VobBlanker output, that means the DVD structure and ADT/ADMAP tables are pretty good. Shrink complains if a pointer is not ok...

I'll do my best trying to find the problem, but seems not easy...

jsoto

[blueboyec]

jsoto,

I will do another test using VOBblanker to preprocess the 4th Seinfeld disk including vts 7, 12, and 13 (vts with unreferenced material) and then process through (without also preprocess with DVDshrink to shrink menu and removing audios) DVDrebuilder. I will report results tomorrow.

[lark]

just a wild quess,

Originally posted by blueboyec
The third time I processed this DVD with VOBblanker and skipped VTS 7 them copied the original VTS 7 to the process DVD folder and did a get VTS with ifoedit.

...

I then moved the original VTS 7, 12, and 13 to the processed DVD folder did a get VTS with ifoedit and ran it through DVDrebuilder and all when well.


could the magic lie in the get vts in ifoedit...?
i.e. that fixes something that vobblanker broke?

regards
t :)

[jsoto]

could the magic lie in the get vts in ifoedit...?
i.e. that fixes something that vobblanker broke? I believe no. What blueboyec is doing is manually replacing some VTSs after VobBlanker runs, and, after that, you need to do a "get VTS sectors".

jsoto

[lark]

yep, i sure know, you need to do that,
but what i was trying to propose, was that perhaps there's something wrong (or extra) in the IFOs that vobblanker creates, since copying the over the original VOBs and running get vts sectors fixes the problem for RB...

but as said, this was just wild quess.

btw i've never had problems with vobblanker ;-)

regards
t :)

[Sir Didymus]

Originally posted by blueboyec
jsoto,

Read somewhere in the tread that vobblanker automatically removes unreferenced material. DVDrebuiler always chokes in the rebuilding phase when trying to process a VTS that had its unreferenced material removed by vobblanker. Requesting that unreferenced material be automatically blanked (not remove) to prevent DVDrebuilder from choking. Hope this is possible?

Hi blueboyec.

Have to totally disagree with your statement. I remove Unreferenced Material in a systematic way (always using VobBlanker) and never had any issue feeding DVD-RB with VobBlanker processed material...

Originally posted by Jsoto
I've to confess I cannot follow DVD-RB forum (it is very active) but I usually do a search trying to find potential VobBlanker issues. What I see is some hard DVD-RB testers recomending VobBanker as a preprocess step to DVD-RB...
Me being one of them..., and I follow very carefully the DVD-RB forum. I can guarantee you that if I had even the minimun problem related by sure to VobBlanker, I would have reported it in this forum...

Originally posted by blueboyec
I forgot that after processing DVD with VOBblanker I always use DVDshink to shrink menus and remove non English audios. Could this be the cause of the problem? Will also send you the ifos processed with DVDshrink.
Dont't want to give answers to your question, but adding some ones (in the given order) to you:
- why using a third applications for removing audio streams ? Rebuilder does the job properly and flawlessly.
- why don't you simply check if just VobBlanker+Rebuilder work properly or not (I will be very surprised of the contrary...) ?
- if you have to reduce menus, and you get into some troubles, why don't you try to produce an oversized encoding, shrinking the menues after the Rebuild step ?

Cheers,
SD

Edit: me voting for keeping the process as it is: if unreferenced material is actually unreferenced it means it is not playable. So removal, IMHO, is the proper way of handling them...

[blueboyec]

jsoto,

Sent you the ifo files. Ran the Seinfeld disk with only VOBblanker preprocessing and RB choke on VTS 7 rebuilding phase. Will do more testing by skipping processing of each individual VTS that have unreferanced material to see if RB only chokes on these VTS and report back in a couple of day. Just trying to trouble shoot.

all

thanks on the comments.

[blutach]

Originally posted by Sir Didymus
Edit: me voting for keeping the process as it is: if unreferenced material is actually unreferenced it means it is not playable. So removal, IMHO, is the proper way of handling them... Me too. Get ridda the rubbish!

[jsoto]

@blueboyec

Mmm, I've seen a reordered VOB with some holes in ADT table: This is the summary:
CID/VID 1/1
CID/VID 1/5
CID/VID 1/3
CID/VID 1/6

I've authored a DVD with the same order in the VOB and IFO and start DVD-RB on it without any problems.

But, to be sure, could you change the following VOBID/CELLID, using VIDChanger in single cell mode

FROM 1/5 TO 1/2
FROM 1/6 TO 1/4

And test again?

jsoto

VIDChanger steps:
Select MODE=Single Cell
Load VTS_07_0.IFO
Select in Cell list combo 1/5
In New Vob Cell, select 1 as VobId and 2 as CellId
PROCESS!
Select in Cell list combo 1/6
In New Vob Cell, select 1 as VobId and 4 as CellId
PROCESS!
You're done.

[jsoto]

I believe I've found the problem. But seems to me not easy to solve...
I'm geting an Error #0003 in DVD-RB (rebuild phase) using a similar processed VOB.
Is it the same you are experiencing?

This is the original VOB layout:

[00000000] Number of VOB IDs in VTS_VOBs 1 [0001]
[00000004] End byte of VTS_C_ADT table 79 [0000004f]
[00000008] 1. Cell: VOB ID 1 [0001]
[0000000a] 1. Cell: Cell ID 1 [01]
[0000000c] 1. Cell: Start sector 0 [00000000]
[00000010] 1. Cell: End sector 134936 [00020f18]
[00000014] 2. Cell: VOB ID 1 [0001]
[00000016] 2. Cell: Cell ID 2 [02]
[00000018] 2. Cell: Start sector 134937 [00020f19]
[0000001c] 2. Cell: End sector 136798 [0002165e]
[00000020] 3. Cell: VOB ID 1 [0001]
[00000022] 3. Cell: Cell ID 3 [03]
[00000024] 3. Cell: Start sector 136799 [0002165f]
[00000028] 3. Cell: End sector 242782 [0003b45e]
[0000002c] 4. Cell: VOB ID 1 [0001]
[0000002e] 4. Cell: Cell ID 4 [04]
[00000030] 4. Cell: Start sector 242783 [0003b45f]
[00000034] 4. Cell: End sector 244650 [0003bbaa]
[00000038] 5. Cell: VOB ID 1 [0001]
[0000003a] 5. Cell: Cell ID 5 [05]
[0000003c] 5. Cell: Start sector 244651 [0003bbab]
[00000040] 5. Cell: End sector 377583 [0005c2ef]
[00000044] 6. Cell: VOB ID 1 [0001]
[00000046] 6. Cell: Cell ID 6 [06]
[00000048] 6. Cell: Start sector 377584 [0005c2f0]
[0000004c] 6. Cell: End sector 377619 [0005c313]


As you can see, cells 1/2 and 1/4 are very small. They are both unreferenced material.

These are the PGCs:

PGC_1 (program chain): [Title(TTN): 1] [00:18:58.21 / 30 fps] (Programs: 4) (Cells: 4) (uses VOB-IDs: 1)
[Ch 01] [Pg 01] [Cell 01] [V/C Id: 1/ 1] : time: 00:06:31.02 / 30 fps [Pos: 00:06:31.02] [Frames: 11732] SP/ILVU/DISC/SA:[ no/ no/yes/ no]
[Ch 02] [Pg 02] [Cell 02] [V/C Id: 1/ 5] Layer Br.: time: 00:07:05.23 / 30 fps [Pos: 00:13:36.25] [Frames: 24505] SP/ILVU/DISC/SA:[ no/ no/yes/ no]
[Ch 03] [Pg 03] [Cell 03] [V/C Id: 1/ 3] Layer Br.: time: 00:05:20.16 / 30 fps [Pos: 00:18:57.11] [Frames: 34121] SP/ILVU/DISC/SA:[ no/ no/yes/ no]
[Ch 04] [Pg 04] [Cell 04] [V/C Id: 1/ 6] Layer Br.: time: 00:00:01.10 / 30 fps [Pos: 00:18:58.21] [Frames: 34161] SP/ILVU/DISC/SA:[ no/ no/yes/ no]

PGC_2 (program chain): [Title(TTN): 2] [00:06:32.12 / 30 fps] (Programs: 2) (Cells: 2) (uses VOB-IDs: 1)
[Ch 01] [Pg 01] [Cell 01] [V/C Id: 1/ 1] : time: 00:06:31.02 / 30 fps [Pos: 00:06:31.02] [Frames: 11732] SP/ILVU/DISC/SA:[ no/ no/yes/ no]
[Ch 02] [Pg 02] [Cell 02] [V/C Id: 1/ 6] Layer Br.: time: 00:00:01.10 / 30 fps [Pos: 00:06:32.12] [Frames: 11772] SP/ILVU/DISC/SA:[ no/ no/yes/ no]

PGC_3 (program chain): [Title(TTN): 3] [00:07:07.03 / 30 fps] (Programs: 2) (Cells: 2) (uses VOB-IDs: 1)
[Ch 01] [Pg 01] [Cell 01] [V/C Id: 1/ 5] : time: 00:07:05.23 / 30 fps [Pos: 00:07:05.23] [Frames: 12773] SP/ILVU/DISC/SA:[ no/ no/yes/ no]
[Ch 02] [Pg 02] [Cell 02] [V/C Id: 1/ 6] : time: 00:00:01.10 / 30 fps [Pos: 00:07:07.03] [Frames: 12813] SP/ILVU/DISC/SA:[yes/ no/ no/ no]

PGC_4 (program chain): [Title(TTN): 4] [00:05:21.26 / 30 fps] (Programs: 2) (Cells: 2) (uses VOB-IDs: 1)
[Ch 01] [Pg 01] [Cell 01] [V/C Id: 1/ 3] : time: 00:05:20.16 / 30 fps [Pos: 00:05:20.16] [Frames: 9616] SP/ILVU/DISC/SA:[ no/ no/yes/ no]
[Ch 02] [Pg 02] [Cell 02] [V/C Id: 1/ 6] Layer Br.: time: 00:00:01.10 / 30 fps [Pos: 00:05:21.26] [Frames: 9656] SP/ILVU/DISC/SA:[ no/ no/yes/ no]



After VobBlanker process, VOB layout is:

[00000000] Number of VOB IDs in VTS_VOBs 1 [0001]
[00000004] End byte of VTS_C_ADT table 55 [00000037]
[00000008] 1. Cell: VOB ID 1 [0001]
[0000000a] 1. Cell: Cell ID 1 [01]
[0000000c] 1. Cell: Start sector 0 [00000000]
[00000010] 1. Cell: End sector 134936 [00020f18]
[00000014] 2. Cell: VOB ID 1 [0001]
[00000016] 2. Cell: Cell ID 5 [05]
[00000018] 2. Cell: Start sector 134937 [00020f19]
[0000001c] 2. Cell: End sector 267869 [0004165d]
[00000020] 3. Cell: VOB ID 1 [0001]
[00000022] 3. Cell: Cell ID 3 [03]
[00000024] 3. Cell: Start sector 267870 [0004165e]
[00000028] 3. Cell: End sector 373853 [0005b45d]
[0000002c] 4. Cell: VOB ID 1 [0001]
[0000002e] 4. Cell: Cell ID 6 [06]
[00000030] 4. Cell: Start sector 373854 [0005b45e]
[00000034] 4. Cell: End sector 373889 [0005b481]


and, using VIDChanger it could become

[00000000] Number of VOB IDs in VTS_VOBs 1 [0001]
[00000004] End byte of VTS_C_ADT table 55 [00000037]
[00000008] 1. Cell: VOB ID 1 [0001]
[0000000a] 1. Cell: Cell ID 1 [01]
[0000000c] 1. Cell: Start sector 0 [00000000]
[00000010] 1. Cell: End sector 134936 [00020f18]
[00000014] 2. Cell: VOB ID 1 [0001]
[00000016] 2. Cell: Cell ID 2 [05]
[00000018] 2. Cell: Start sector 134937 [00020f19]
[0000001c] 2. Cell: End sector 267869 [0004165d]
[00000020] 3. Cell: VOB ID 1 [0001]
[00000022] 3. Cell: Cell ID 3 [03]
[00000024] 3. Cell: Start sector 267870 [0004165e]
[00000028] 3. Cell: End sector 373853 [0005b45d]
[0000002c] 4. Cell: VOB ID 1 [0001]
[0000002e] 4. Cell: Cell ID 4 [06]
[00000030] 4. Cell: Start sector 373854 [0005b45e]
[00000034] 4. Cell: End sector 373889 [0005b481]

which is "ordered" again.

As you can see, all Cells in all playback tables are type=2, meaning a discontinuity in SCR and PTSs, with the exception of PGC #3 (cells 5 & 6)

But SCR (I'm guessing now) is "continuous" or, at least it always go up in the original VOB,
but not in the VobBlanker processed one (please note "re-ordering" the VOB using VIDChanger just change VID/CID but not the SCR,
so the problem is not solved) I believe this kind of SCR irregularities are not well accepted by DVD-RB.

@blueboyec:
Could you cut your VOB (VTS_07_1.VOB) with Cutfile from 134850 up to 136826 (using 2048 bytes per block) and send it to me? I'd like to see the Navpacks inside.
(The resulting file will be 4046848 bytes. If you are on dialup, I'll try to find other way.)

jsoto

[blueboyec]

jsoto,

DVDrebuider GOOD/chokes on VTS 7 says:

All good:
- Processing VTS_07
- Rebuilding segment 0 VOBID: 1 CELLID: 1
- Rebuilding segment 1 VOBID: 1 CELLID: 2
- Rebuilding segment 2 VOBID: 1 CELLID: 3
- Rebuilding segment 3 VOBID: 1 CELLID: 4
- Rebuilding segment 4 VOBID: 1 CELLID: 5
- Rebuilding segment 5 VOBID: 1 CELLID: 6

Cokes:

- Processing VTS_07
- Rebuilding segment 0 VOBID: 1 CELLID: 1
- Rebuilding segment 1 VOBID: 1 CELLID: 5 it cokes here and quits

Based on your write up and the above info I do believe the problem is the reordering. This hardly ever happens so maybe we can live with it.

Do not have the original DVD anymore, give it back my sisterinlaw, if I can get it back I will try to do as you ask. Most of the things you are asking me to do are foreign to me but I will try? Will not be able to do until after new years.

Hope you and your family have a happy holidays. And as always, thanks for the great program and your hard work!

[jsoto]

I do believe the problem is the reordering No, this is not the problem. I was able to rebuild unordered DVDs without problems. I believe the problem is the SCR "discontinuities" due the deleted material.

This hardly ever happens so maybe we can live with it. I hope so.
I do not want to modify SCR/PTSs. Sure I'll introduce more bugs than the things I can fix. However, I should do it when cutting part of the middle of a cell..

jsoto

[blueboyec]

jsoto,

Would blanking the Unreferenced Material, not deleting them, solve the problem? If not, I beleive we can live with VOBblanker as is. Do not want more problems introduced to solve something that hardly ever happens.

Forgot to report that DVDrebuilder was able to process VTS 12 and VTS 13 and they had Unreferenced Material. DVDrebuilder only ckoked on VTS 7, odd.

thanks

blueboyec

[jsoto]

Forgot to report that DVDrebuilder was able to process VTS 12 and VTS 13 and they had Unreferenced Material Ah!!. So I believe the problem occurs when SCR goes backwards in the VOB (which is not the case of VTS12 & 13, it only in 07).

jsoto

[blueboyec]

jsoto,

I am glad that the info I am postings is helping because I do not understand the inner workings of DVDs (SCRs tables etc). Glad there are programing experts here at Doom9 like you to help us that are just users. Is there anything else I can look at that can help.

Thanks

Blueboyec

[Wheelie4]

I still hadn't gotten familiar with VobBlanker. I had a little problem backing up RE2 with DVD Decrypter but finally got it done. Then editted with DRM. I noticed others say they ripped RE2 with no problem using VobBlanker. My question is does VobBlanker remove all those protections like DVD Decrypter or must AnyDVD or DVD43 be running in the background?

[sweetness]

Wheelie4,
do you mean prohibited user operations (POUs)? i don't think vobblanker can but ifoedit and pgcedit can. or if there in the vob you can check out vobPUO 0.1 ->edit POUs in VOBs (http://forum.doom9.org/showthread.php?threadid=86318)

[Wheelie4]

No not PUO's, I was refering to the others like CSS, Macro, RPC.

[sweetness]

no vobblanker does not do that. but i never had a problem with DVD Decrypter, IMHO it's the best one out there.

[Wheelie4]

I never had a problem with DVD Decrypter until RE2. It's commented here (http://forum.dvddecrypter.com/index.php?showtopic=15390) by the maker of DVD Decrypter.

[jsoto]

Just to clarify: VobBlanker is able to remove (not edit) the PUOPs in IFOs and even in VOBs. You have two checkboxes in the GUI (default checked) for this.
jsoto

[Wheelie4]

Thanks jsoto and sweetness. I saw the PUOP IFO/VOB removal options. I just wasn't sure about CSS, RPC and Macro removal.