VobBlanker 1.5.1.0 is out: A tool to blank, cut or replace titles and Menus

[DMagic1]

/me continues to be amazed by how far this project has come. :)

[jsoto]

@blutach
Has the "timing bug" been fixed where a PGC has been stripped/blanked? This is where the chapter times are thrown off by 6 or so frames every now and then? Not yet. I still have to reproduce it. but I have an idea.. are you using a non-usual resolution? (let say, different from 720x576/480)

As well, are you aware that if you selected to process menus only (and untick titles), then go in and set the menus you want to blank, the titles button became "re-ticked" when you returned to the main pane? (This happened in v 1.5.0.7 - has it been fixed?)
That's new for me. No it has not been fixed, but I've just tested it and I'm not able to reproduce , neither in 1508 nor in 1507... May be it depends on the DVD?
@DMagic1
Many thanks.
jsoto

[blutach]

Re resolution - straight PAL

Re Titles re-checking - I will continue to monitor in v5.0.8 and revert. Anyone else seen this "problem"?

[jsoto]

@blutach
Resolution. PAL, but is it 720x576? (there are other posibilities, 704x576, 352x576 and 352x288).

jsoto

[blutach]

Yep. Always 720 x 576

[CoNS]

jsoto, thanks again for sharing your hard work with the rest of us on a freeware basis. It is much appreciated.

Keep up the good work!

:thanks:

[Sir Didymus]

Originally posted by DMagic1
/me continues to be amazed by how far this project has come. :)

Me too. It's an excellent application. I am using VobBlanker in a (more or less) systematic way; it's my preferred tool on all of the others, when I have to customise my DVDs, and never had to complain about...

If only some skilled programmer could give some help (or some hints) in order to improve a little bit the preview, it would be more than excellent. [By the way Jsoto, it's a suggestion, it's not a complain, I am really fully happy as it is...] :)

Cheers,
SD

[doktor motte]

@jsoto:

:cool: thnx lot for your much work on vobblanker and the great improvement and stability it has.

Followed this thread in the background long time.

For me vobblanker works like a charm for the past ~70 backups i made.

So keep on your good, hard work and sharing with us your neat tools.

Cheerio mate ;)

[jsoto]

Thanks to all of you for your kind words.
Cheers.

[jsoto]

Bug reported by hocuspocus69:
- Cell extraction in VIDEO_TS.VOB does not work. (VobBlanker tries to find VTS_00_0.VOB)
jsoto

[2COOL]

@jsoto

Is there any room to put in a Chapter and Programs columns in Cell List? It would be very helpful so that when we do splits, we can blank at a known chaptered cell.

Request:

I'm envisioning of selecting a single cell in Cell list and there is a button named "Split". By clicking on this, you will have two options.

1. Blank this cell and previous ones.
2. Blank this cell and following ones.

or

1. Blank previous cells
2. Blank following cells

What do you think?

[jsoto]

Originally posted by 2COOL
Is there any room to put in a Chapter and Programs columns in Cell List? It would be very helpful so that when we do splits, we can blank at a known chaptered cell.
I'll look into it


Request:
I'm envisioning of selecting a single cell in Cell list and there is a button named "Split". By clicking on this, you will have two options.
1. Blank this cell and previous ones.
2. Blank this cell and following ones.
or
1. Blank previous cells
2. Blank following cells
What do you think? I believe you can do it with multiple selection, don't you?. Click on the cell you want to split and, after, shift+click on the begining cell or on the ending cell, click on blank, and you will have it.

jsoto

[2COOL]

Originally posted by jsoto
I believe you can do it with multiple selection, don't you?. Click on the cell you want to split and, after, shift+click on the begining cell or on the ending cell, click on blank, and you will have it. I know about this. Just wanted to see it automated for newbies.

[mrslacker]

First off, thanks jsoto and 2COOL for making my life easier. I previously used 2COOL's guides with jsoto's blankvob before I discovered VobBlanker. VB almost takes the fun out of the process! ;)

Anyway, I have two questions/observations regarding VobBlanker. First, I noticed with one DVD that immediatly after loading, VIDEO_TS shows a size of 96MB, menu 96MB, but a final size of ~1400kB. Nothing is set to blank and it is set to be processed. Is this a case of unreferenced material being chopped? Maybe reused material somehow saving space?? The VOB size is atually 96MB originally and its actually 1400kB when processed.

Second, I blanked three titles (previews) that play before the main menu (different title) and my standalone won't make it through the studio intro, the blanked previews, and to the main menu. It appears to freeze after the studio intro. As far as I can remember there were no cell commands (no warnings from VobBlanker at least) that got chopped. Is there any reason or scenario when I would still need to mock strip with IfoEdit? I thought that was coded into VB a while ago. Strangely, PgcEdit traces to the main menu just fine, as does MPC. They don't care about sectors... hence my thoughts about the mock strip.

Thanks for any thoughts or explainations. I'd like to give some more info, but I'm at work. I plan to try unchecking Pre->Post (Safely) to just let the 0.15 sec vobs play. My standalone might just be finicky. Its one of the picky Sonys that gave problems with many DVD Rebuilder versions.

Your a hero, jsoto! I love the menu capabilities in 1.5.

[jeanl]

mrslacker,
How did you burn your DVD?
I ran into similar problems (although not related to vobblanker) when using Nero in File mode. Mpucoder had something to say about it:
http://forum.doom9.org/showthread.php?s=&postid=568536#post568536
but I was never able to confirm the problem.
My problem was a DVD, which played fine in PowerDVD and on standalone if burned with DVDDecrypter. When burned with Nero in File mode, then PowerDVD froze toward the beginning...
I also posted the problem here:
http://forum.doom9.org/showthread.php?s=&threadid=85267

I'd be curious to see if you're just seeing another instance of the same problem...
Jeanl

[jsoto]

Originally posted by mrslacker
Is this a case of unreferenced material being chopped?
It should be, in other case there is an error in VobBlanker. You can confirm it in dvdshrink.
To save space (i.e. reusing a LU) it is required some manual settings.
Is there any reason or scenario when I would still need to mock strip with IfoEdit?
AFAIK, no. There are some scenarios related with cutting cells in the middle that can freeze, but AFAIK, never if blanking complete cells (or PGCs). Please note these scenarios are not fixed with IFOEdit's mock strip, because they are related with PTSs and SCRs, not fixed by IFOEdit's mock strip.
So, I believe your problems can be related with post-->pre. Try without changing post--> pre. You always can do it later with PgcEdit. If not, may be your problem is the one jeanl is pointing out..

jsoto

[blutach]

@mrslacker

I always do a mock strip after CUTTING titles in VobBlanker. I find the chapter points are off by 6 or so frames here and there, which a mock strip in IfoEdit corrects nicely.

As well, in VobBlanker, I leave the pre to post UNCHECKED, as it uses a slightly different algorithm to PgcEdit (which I have never had a problem with).

Using this method, I have never had a bad blank with VobBlanker.

As to your VIDEO_TS.VOB question: VobBlanker blanks unreferenced material by default. This means that sometimes you will end up with no VIDEO_TS.VOB at all, which Nero (for example) will protest about. Don't worry about it.

Regards and good luck

[mrslacker]

Regarding the disc that freezes after the studio logo:

@jeanl
I did burn with nero. It was version 6.6 which, according to blutach, should be fine. I tried burning with ImgTool/DVDDecrypter anyway and got the same results.

@jsoto
You were right. I unchecked the Pre->Post conversion and the disc works fine on my standalone. I just have to wait a couple seconds for it to play the "blank" vobs. No sweat. I wonder why this was a problem when there were no cell commands present. I assume VobBlanker also changes the number of cells and the playback time to zero? I don't know if that kind of thing is necessary... I just saw that process in a 2COOL guide once. Its probably my picky player.

Not that I don't trust VobBlankers unreferenced material decisions, but it would be nice to have the option to hold on to this stuff. I can't say why... maybe I'm a minimalist when it comes to editing. :)

@blutach
As well, in VobBlanker, I leave the pre to post UNCHECKED, as it uses a slightly different algorithm to PgcEdit (which I have never had a problem with).
I'll be doing the same from now on as well.

Also, what I said to jsoto. I clearly don't have a good picture of the methods of the two programs. I'll have to read the PgcEdit v0.3 thread more closely at some point.

@all
thanks!

[mrslacker]

Regarding the other disc with disappearing material:

Originally posted by jsoto
It should be, in other case there is an error in VobBlanker. You can confirm it in dvdshrink.
jsoto

I verified with Shrink that it was unreferenced material being stripped. The material was several versions of the studio logo... weird! Thanks for the tip. You too blutach.

[jeanl]

Originally posted by mrslacker
Regarding the disc that freezes after the studio logo:
@jsoto
You were right. I unchecked the Pre->Post conversion and the disc works fine on my standalone. I just have to wait a couple seconds for it to play the "blank" vobs. No sweat. I wonder why this was a problem when there were no cell commands present. I assume VobBlanker also changes the number of cells and the playback time to zero? I don't know if that kind of thing is necessary... I just saw that process in a 2COOL guide once. Its probably my picky player.

@jsoto: I wonder what it is that makes skipping not work with vobblanker? I thought vobblanker and pgcedit used the same technique, unless there were cell commands and/or buttons?
Is it because vobblanker moves the commands from post to pre (instead of adding pre-commands)? That would indeed explain it, but I don't remember now...
Jeanl

[mrslacker]

Originally posted by jeanl
I thought vobblanker and pgcedit used the same technique, unless there were cell commands and/or buttons?
Is it because vobblanker moves the commands from post to pre (instead of adding pre-commands)? That would indeed explain it, but I don't remember now...
Jeanl

Not sure what you mean here.

Changing post to pre:
Number of Pre Commands: original pre + original post
Number of Post Commands: 0
vs.
Adding pre commands:
??Leave the post commands & append them to the pre commands??

The discussion (http://forum.doom9.org/showthread.php?s=&postid=544570#post544570) between jsoto and r0lZ makes PgcEdit's three options seem equivalent to VobBlanker's options of safely, always, and never (unchecked), at least for non-menu PGCs.

I appreciate the enlightenment! :thanks:

[jsoto]

Here: http://forum.doom9.org/showthread.php?s=&threadid=82672, we've discussed about changing post into pre.
pgcEdit and VobBlanker options are basically the same, but pgcEdit method is a little bit better than VobBlanker one, because there are some cases where the postcommands still can be executed.

But, in both methods, there are not covered scenarios which will produce a non-functional navigational DVD. So, guys, I believe this is something we have to live with. We need to test before burn, and when we find one of these cases, there are two options: blank without changing post into pre (and waiting some seconds) or manually (using pgcEdit) try to find the root cause and solve the problem in a different way.

About unreferenced material, it's not easy (due VobBlanker internal logic) to keep it. And,... frankly, I do not find any reason to do it.

Please notice that unreferenced material are cells which are not included in any PGC. This should not be confused with non-entry PGCs (occasionally accessed using some navigational tricks); in this last case, the cells are listed in the PGC, so they are referenced material.

In my experience, the unreferenced material I've found always has been weird, like a scene/logo repeated many times.

jsoto

[mrslacker]

@jsoto
pgcEdit and VobBlanker options are basically the same, but pgcEdit method is a little bit better than VobBlanker one, because there are some cases where the postcommands still can be executed.

Wow, I didn't see that daughter thread. VobBlanker is quite a bit more sophisticated than I knew in searching for contingencies (infinite loops,etc.) and modifiying disruptive pre-commands! Very impressive.

I now see the benefits of preserving post commands, jsoto and jeanl. I hadn't thought through the scenario in which precommands would redirect the logic before reaching the newly moved pre-commands. That's a clear issue. I'll be ordering more DVD+RWs. ;)

Still, I wonder why PgcEdit successfully traced through the disc that froze on my standalone. I'll have to investigate this some more.

[blutach]

Originally posted by mrslacker
I now see the benefits of preserving post commands, jsoto and jeanl. I hadn't thought through the scenario in which precommands would redirect the logic before reaching the newly moved pre-commands. Taking nothing away from jsoto, whom I respect very much, but this is why PgcEdit's Kill Playback is the method I use to bypass unwanted material.


Still, I wonder why PgcEdit successfully traced through the disc that froze on my standalone. I'll have to investigate this some more. This is puzzling. You might like to step through. Could it be your "trace defaults" do not exactly mirror your set top box/TV setup? This happened to me once (I had the aspect ratio set "incorrectly") and once I changed it, I found I actually went to another set of PGCs.

Regards

[r0lZ]

Originally posted by mrslacker
Still, I wonder why PgcEdit successfully traced through the disc that froze on my standalone. I'll have to investigate this some more. Don't thrust the trace to much. There are still bugs and probably some omissions. Furthermore, because the trace doesn't actually play the video, it doesn't check for the consistance of the various video related tables. However, it will display a warning if it try to play a cell in a dummy PGC.

[Mr.Shine]

Originally posted by jsoto
About unreferenced material, it's not easy (due VobBlanker internal logic) to keep it. And,... frankly, I do not find any reason to do it.


Interesting, right when I get off the ground and decide to actually write a post on the 0-byte-VOB issue, I notice that it has already been discussed. Disappointing, though, that jsoto is not planning to change it. I prefer keeping those unreferenced menu VOBs, and if it's only to make sure that (a) BUP and IFO are always in different ECC blocks and (b) sector pointers are always valid, regardless of the imaging/burning program used. I've been going the painful way of manually linking the unreferenced material to a PGC before processing with VobBlanker and unlinking afterwards in the past. Guess I'll have to continue doing that.
However, how about an option to add dummy cells to VOBs resp. VTSs that'd be be smaller than 32k after processing, to make them at least 32k. This would would save a bit space (since most unreferenced dummy-VOBs I've seen were >100kb or even several MBs) and also fix the ECC-block/VTS-pointers issue.

Now to something else that I believe hasn't been discussed yet.

A while ago, I was trying to fix a DVD that had the last few MBs missing due to read error on the original. When I just ran it through VobBlanker, it complained at the end of the incomplete VOB and cancelled processing. Instead, could it be implemented that VobBlanker gives the option to clip the incomplete VOB to the last complete GOP it finds and continue processing (like I had to do manually with the Prev/Cut feature)?
I believe VobBlanker generally relies too much on sector pointers in the IFOs. I tried manually adjusting a few pointers on the above mentioned DVD, and suddenly VobBlanker processed it without complaining. Of course, the DVD froze at the end (due to broken VOBU, I believe?), so I still had to fix it with Prev/Cut, but it was only a what-if test anyway. :)
Relying on those pointers also creates issues with processing VOBs that are larger than the IFO says, e.g. when I replaced single cells with larger ones, or am trying to replace a complete VTS with a larger one.
Therefore, I'd much prefer it if VobBlanker worked independently of the sector pointers, assumed them to be wrong by default and recreated them, much like IfoEdit's mock-strip does. There have been cases where I had to mock-strip in IfoEdit AND run through VobBlanker afterwards. I'd like to skip IfoEdit's mock-strip completely, as it happened to me in the past that it broke more than it fixed.

I hope my suggestions are useful! :)

[blutach]

@Mr Shine

Unreffed material - If you use PGCEdit to Kill Playback of all VMGM PGCs, then it will replace the cells (incl unreffed material) with a 10k blank VOB (or anything else you want to replace it with). This is a very handy way of killing FBIs and stupid authoring promos in one click.

VOBBlanker's pointers - are sometimes out by a few frames here and there in the timings. The best way to go after a Prev/Cut in VobBlanker is to immediately do a mock strip in IfoEdit, which clears things up nicely. Can never think of a situation where IfoEdit's strip broke anything of mine (although sometimes you do need to check the layer break flags in the PGCs).

Regards

[2COOL]

Originally posted by blutach
If you use PGCEdit to Kill Playback of all VMGM PGCs, then it will replace the cells (incl unreffed material) with a 10k blank VOB (or anything else you want to replace it with). PgcEdit's Kill Playback macro only edits the IFO's command table. There should be no edits/changes to the VOBs. If you choose to blank all the VMGMs, you do have the option there to do a Kill Playback. ;)

[jsoto]

Unreferenced material: well, to have different ECC blocks for IFO and BUP is a reason. May be I can add an option to do it automatically. Up to now it is really easy to do it. Just create with BlankVob a _0.VOB file with the needed number of sectors (one blabnk cell= 5 sectors) and adjust sectors with IFOEdit.
I believe VobBlanker generally relies too much on sector pointers in the IFOs Yes, absolutely. Dvdshrink does too.
I agree with blutach, I've never seen a problem with an IFOEdit's mock strip. (I did a lot of them before VobBlanker exists, believe me, but only with PAL material), so if you have a sector pointer problem, try with IFOEdit, and if you are lucky, it will be solved.
The best way to go after a Prev/Cut in VobBlanker is to immediately do a mock strip in IfoEdit, which clears things up nicely. Disagree. Up to now, (keeping away the few frames difference which IMHO is not a problem) VobBlanker issues when cutting cells in the middle are not solved by IFOEdit's mock strip, because they are related with SCR and PTSs counters, which are not modified by IFOEdit's mock strip.

jsoto

[Mr.Shine]

Originally posted by jsoto
Unreferenced material: well, to have different ECC blocks for IFO and BUP is a reason. May be I can add an option to do it automatically. Up to now it is really easy to do it. Just create with BlankVob a _0.VOB file with the needed number of sectors (one blabnk cell= 5 sectors) and adjust sectors with IFOEdit.


That's the quick and dirty way, yes. However, that would just be a dummy file, not an unreferenced VOB. Meaning that if I send the disc through a transcoder afterwards, it wouldn't see the dummy file at all and I'd need to re-add it and re-adjust VTS pointers after transcoding again. Better if this VOB were actually known in the IFO, just not referenced by any PGC, like it is on the original disc. Looking forward to VobBlanker doing that for me. In the meantime, I'll be continuing the painful way. I'm a perfectionist, after all!

I agree with blutach, I've never seen a problem with an IFOEdit's mock strip. (I did a lot of them before VobBlanker exists, believe me, but only with PAL material), so if you have a sector pointer problem, try with IFOEdit, and if you are lucky, it will be solved.


I never said IfoEdit's mock-strip fails on many DVDs. I didn't want to go into it, because it doesn't belong into this thread, so just a quick example (that actually happened to me): In a VTS of the more complex kind, ie. one where main feature, all extras, trailers etc. were in one single VTS, after mock-stripping, cell commands weren't being executed anymore and still pictures weren't still anymore. So all extras played in a row instead of returning to the menu after each one and I had a great 30fps diashow instead of one with "Next" and "Prev" buttons! For some reason IfoEdit decided to redo the complete PGC play maps, ignoring all info that was in there before... The missing stills were fairly easy to fix, but I still have no idea why all cell commands were suddenly being ignored. VobBlanker processed that DVD fine, so I "mock-stripped" using VobBlanker in the end.

[r0lZ]

That's true. After a mock strip, IfoEdit forget most of the cell playback table, including the cell commands numbers.

[jsoto]

@Mr.Shine
Ah!. You are right. The still times are lost in IFOEdit's mock strip...

EDIT: Didn't see r0lZ's answer, which is more complete..

jsoto

[blutach]

Originally posted by 2COOL
PgcEdit's Kill Playback macro only edits the IFO's command table. There should be no edits/changes to the VOBs. If you choose to blank all the VMGMs, you do have the option there to do a Kill Playback. ;) [/B] Ahem. That's what I meant - sorry :)

[blutach]

Originally posted by r0lZ
That's true. After a mock strip, IfoEdit forget most of the cell playback table, including the cell commands numbers. I found this out recently, too. Is Derrow fixing this, do you know?

@2COOL - maybe your mock strip guide could be updated with this info?

Regards

[jsoto]

Better if this VOB were actually known in the IFO, just not referenced by any PGC, like it is on the original disc. I know, but not "like in the original". I've found many DVDs with a lot (tens oo hundreds of Megabytes) of unreferenced material. I'm assuming you are requesting 16 sectors (32 KB), aren't you?.

jsoto

[blutach]

My 2 cents worth.

I kinda like the fact that VobBlanker eliminates unreffed crap and have never had a playback problem by having no VIDEO_TS.VOB (for example). That said, I do tend to use the PgcEdit method of blanking all VMGMs and killing playback, as mentioned earlier.

Regards

[jsoto]

I've found one scenario where IFOEdit and VobBlanker output different frame count

I'm backing up an original (PAL) with a blank cell of 10 frames. As mpucoder said here (http://forum.doom9.org/showthread.php?s=&postid=462625#post462625) the minimum cell time should be 12 frames. This is the final value you get after a IFOEdit's mock strip. I've also coded this restriction in VobBlanker, but seems there are cases where this restriction is not applied (keeping the PGC, i.e.), so the final value after VobBlanker process is the same than the original: 10 frames

Well, I'm going to modify VobBlanker to guarantee a 12 frames length in all the cases, but it is a false value, because the actual number of frames (inside the VOB) is lower.

@blutach:
Could you confirm if this is the case you are reporting?.

jsoto

[Mr.Shine]

Originally posted by jsoto
I know, but not "like in the original". I've found many DVDs with a lot (tens oo hundreds of Megabytes) of unreferenced material. I'm assuming you are requesting 16 sectors (32 KB), aren't you?.

jsoto

Of course. Keeping tens or hundreds of MBs with stuff that is never played anyway kinda defeats the purpose of making a DVD smaller! What I mean with "like in the original" is that the VMGM_C_ADT and VMGM_VOBU_ADMAP (are there any more?) tables are filled properly, so the 32kb VOB does logically belong to the disc, even though it's not linked to any PGC.

Oh, and most likely 30kb would already be sufficient. Since the IFO takes up at least 1 sector, the maximum needed to reach the next ECC block is 15 sectors, 30kb.

[blutach]

Originally posted by jsoto
@blutach:
Could you confirm if this is the case you are reporting?.

jsoto @jsoto

What I am saying is this:
Let's say I am cutting the credits out - assume it is part of the last cell of the PGC. VOBBlanker does this beautifully of course (except lately I have been getting warnings about GOPs, but that is another matter).

Now, comparing the revised PGC's chapter times with those of the original, I get errors here and there - there is no way to predict exactly where, but when an error occurs, it is always by 6 frames. The cells in which the errors occur are not tiny ones. This happens in almost all the cuts I do. The cumulative time to the end of the 2nd last cell (the one before the cutting) also changes by a bit.

Also, the playback seems to finish a little bit before the playing time is scheduled to end (a few seconds here and there).

An IfoEdit mock strip always cures these errors! (although I have considered just changing the chapter times in PgcEdit - Rolz is this a viable method?)

Hope I am making myself clear.

Best regards

[r0lZ]

@blutach
You cannot change the chapter times in PgcEdit.
But you can fix the total playback time of the PGC if it is wrong, just by entering the PGC selector.

[lovelegend]

I have no patient to read through 17 pages of messages, so I'm not sure if my suggestion was asked before... :p

I've a DVD-9 which has 26 chapters/cells, I used VobBlanker to blank out last 14 cells to make disc 1, and blank out the first 12 cells to make disc 2. However, I found that I can't simply use VobBlanker to join those 2 discs back to one disc (I tried to open disc 2, select cell 1-12 and press "Replace" and choose vob of disc 1, but it would treat the whole disc 1 as one cell... ^^")

Although I know I can use DVD Decrypter to copy out and split into individual cells, but I'm afraid DVD Decrypter is not cutting at the right points (I checked the chapter information output by DVD Decrypter and it didn't match that of I saw in IfoEdit or PgcEdit, there is few frames difference)...

Therfore, is it possible to make VobBlanker such that if I selected cell 1-12, pressed "Replace" and pointed to another vob with same number of cells, then VobBlanker would replace cell 1-12 of the pointed vob to the cell 1-12 selected vob?

[sweetness]

@lovelegend
to do what you want you would have to extract each cells. then replace the cells one by one in the other disc.

double click on your entry and Cell List should pop up. then click on ExtAll Mult (makes one vob for each cell)
now you would have to replace each one in the other disc. should would.

[jsoto]

@blutach
Sorry, but I'm unable to reproduce your lost frames in PAL. I've tried with 3 DVDs and the cell times after a VobBlanker cut are exactly the same than the originals.
So, I'd like to have one example. Could you send me your VobBlanker project file ( an ini file) and the log?

BTW, what I found reviewing the code is a clear bug in NTSC. I'm using always 25 fps to calculate the number of frames of the last VOBU. This will produce a small difference in NTSC.

jsoto

[lovelegend]

@sweetness
I see.... thanks for the reply, I didn't notice the extract button... ^^"

[blutach]

@jsoto

Will do, after next project. But, log shows it completes without any warnings.

Also PAL here.

Regards

[blutach]

@jsoto

Before and After IFOs, Log and Ini file mailed to you.

Regards

[jsoto]

Finally found and fixed!.

Many thanks for your support

jsoto

[Surf]

Hi Jsoto,

Would it be too much to ask for the CUT function be available at the cell level?
Example: there are 4 trailers I like to preserve in a program chain, your current CUT function can only chopp the beginning of Cell#1 and the ending of Cell#4. My goal is to remove the green preview rating screen and er..."now available in DVD" :D for a reason. So far I have circumvented by using Shrink to chop/re-author them 4 trailers and then replace each cell with the respective one.

Thanks in advance,

[blutach]

@surf

You know you can blank at the cell level?

Regards

[jsoto]

@Surf
Cut function in VobBlanker still has some difficult bugs which have to be fixed so I'm not going to complicate more this function (at least for the moment).

BTW, not sure if dvdshrink reauthor + VobBlanker cell replace will work properly. Test carefully your DVD and let me know.

jsoto