VobBlanker 2.0.1.0 released

[jsoto]

Changelog v2.0.1.0:

Added: Subpictures stripping ability. Includes VOBs scan to calculate subs size.
Added: Global option to fix VOB internal pointers in any case.
Added: Option to fix VOB internal pointers in replacing titles.
Added: In preview dlg, added an option to save frame as BMP
Added: Added code to detect out of memory exceptions in Writepack method.
Added: Added option to autoplay when opening preview dialog.
Added: Option to copy color palette when replacing PGC.
Added: Options to copy Audio/subs tables and status when replacing PGC.
Added: Show # of buttons (BOVs) in Titles (Cells and PGCs). VOB scan is required
Added: Option to check/update STC discontinuity flags in PGC Playback tables, based on written VOB
Improvement: Subpictures stream control updates in the case of an AR change due replacing PGCs
Improvement: Use the number of audio packs scanned to re-calculate the audio size
Improvement: Subs SYNCI pointers are now calculated from scratch, decoding the subs.
Improvement: Option to delete unreferenced cells if they are last ones of a VOBID instead of blank it. Up to now VB was only deleting the last ones of the whole VOB
Improvement: Linked with new 2.0 DVDpreview version (Thanks, jeanl)
Improvement: Multiline tooltips
Improvement: Main window coordinates automatically saved/loaded
Changed:New exe, smaller, linked with MFC42 as shared dll. This seems to fix the missing buttons problem in some computers. As a drawback, Linux users (using wine) will need to put the library mfc42.dll in the same folder than VobBlanker.
Changed: New icons courtesy of M7S
Changed: Main dialog size reduced. Now it can be used with 800x600 resolution.
Changed: Show the main dialog before load the DVD to allow the progress bar to be visible when opening a DVD from shell with "open with.."
BugFix: Strip Titles failed if the first pack of a VOB file (except the first one) was a nav one.
BugFix: TMAPTI was filled wrong when blanking cells (splitting a DVD9 to 2xDVD5 i.e.)
BugFix: Fonts in Log window under Linux were too big.
BugFix: Resizing main dialog bug (in Getinitialcoordinates).
BugFix: Preview not always show a still when opening.
BugFix: Main dialog resizing bug
BugFix: A couple of bugs in preview fixed by jeanl


VobBlanker Navigation links
Versions <= 1.5 discussion thread:
http://forum.doom9.org/showthread.php?s=&threadid=73145
Versions = 1.6 discussion thread:
http://forum.doom9.org/showthread.php?s=&threadid=86437
Versions = 2.0.0 discussion thread:
http://forum.doom9.org/showthread.php?t=92481

jsoto

[Taelon]

Fantastic jsoto, thanks!

Just a minor note, the doom9 link still points to the old version at the moment.

There also seems to be a few issues for people trying to use copy protected or single VTS sources. http://forum.doom9.org/showthread.php?t=100184

[CoNS]

Thanks again for the new release, jsoto. :)

I'm trying to understand exactly how the Replace PGC function works, with all those nice new options (Settings -> More -> Replacing), compared to IfoUpdate/BatchUpdateIFO, and especially the new Import VTST function in the latest beta of PgcEdit, as discussed here (http://forum.doom9.org/showthread.php?p=713107#post713107) and in the following posts... Does VobBlanker's Replace PGC function leave the program/chapter per cell data, cell commands numbers and still times, PGC commands etc. untouched in the original DVD structure? Or does it depend on the Replacing settings?

When I need to replace PGCs, it's not because I've reencoded the video, but because I've been adding extra custom made subtitles in my native language. So, I've either been adding an extra subtitle stream after the last original subtitle stream, or I've been replacing one of the existing subtitle streams with a new one in a different language. Given that I've muxed the new replacement PGC into a VTST with the correct audio and subtitle stream attributes and assignments using MuxMan, which of the Replacing settings in VobBlanker would I want to select/deselect om these cases?

(BTW, there's a tiny cosmetic bug in the tooltip for the Replacing setting "Copy VTS Audio/Sub tables from replacing IFO" in the linebreak)

[jsoto]

Thanks again for the new release, jsoto. :) Glad to be useful.
I'm trying to understand exactly how the Replace PGC function works...... Does VobBlanker's Replace PGC function leave the program/chapter per cell data, cell commands numbers and still times, PGC commands etc. untouched in the original DVD structure? Or does it depend on the Replacing settings? Yes, VB does not change the number of cells/program/chapters neither the original VID/CID sequence. If the replacing PGC has less cells than the original, VB appends blank cells. If the replacing PGC has more cells, VB joins the last ones in one bigger cell.

When I need to replace PGCs, it's not because I've reencoded the video, but because I've been adding extra custom made subtitles in my native language. So, I've either been adding an extra subtitle stream after the last original subtitle stream, or I've been replacing one of the existing subtitle streams with a new one in a different language. Given that I've muxed the new replacement PGC into a VTST with the correct audio and subtitle stream attributes and assignments using MuxMan, which of the Replacing settings in VobBlanker would I want to select/deselect om these cases??Assuming there is only one PGC in the VTS, you have to check the new ones:
Copy PGC subs palette
Copy VTS stream control
Copy VTS Audio/Subs tables
And uncheck Fix Sub streams indexes (in fact it has no sense if you copies the table)

But if the VTS has more than one PGC, the best option is to remux the new streams (audio/subs) in free stream ids, i.e. using audio 0x83 if it is the first stream unused in the original VTS.
After replacing, adjust with pgcEdit the new audio/subs: You have to add one stream more in the VTS, with the right attributes, and disable it (if it is not) in all the PGCs except the replaced one.

(BTW, there's a tiny cosmetic bug in the tooltip for the Replacing setting "Copy VTS Audio/Sub tables from replacing IFO" in the linebreak)thanks.
jsoto

[bloodem]

just a small question, maybe you guys know... So, If I open a DVD, and let's say... I blank one little PGC and then save it... something happens to the main movie... the slider doesn`t work like it normally does. For example, if I move it to the middle of the movie and then back at the beginning... it doesn't exactly go at the beginning... it gets stuck at about 4-5 minutes into the movie, and the only way I can go at the beginning is by manually choosing Chapter 1. What could be the cause for this? Perhaps an option I forgot to enable/disable?

[jsoto]

@bloodem
Which version?. There was a bug in 2.0.0.3/2.0.0.2 (and previous) which shows just this behavior

BugFix: TMAPTI was filled wrong when blanking cells (splitting a DVD9 to 2xDVD5 i.e.)

EDIT: Processing with 2.0.1.0 again the already processed DVD (just keeping all the PGCs) should fix the problem

jsoto

[DMagic1]

Nice work again.

[bloodem]

@bloodem
Which version?. There was a bug in 2.0.0.3/2.0.0.2 (and previous) which shows just this behavior


EDIT: Processing with 2.0.1.0 again the already processed DVD (just keeping all the PGCs) should fix the problem

jsoto


yes, I was using 2.0.0.2, I`ll try 2.0.10 and see if it works. Anyway, thanks a lot, great program BTW!

[blutach]

Thanks jsoto :)

Regards

[CirTap]

excellent work! you have another fan! :D

[jm1647]

jsoto - the main dialog page looks good at 800x600 - Thanks!!

[OvERaCiD23]

Not related to this release, I finally used the Motion2Still feature yesterday on "The Upside of Anger". It reduced the main menu from 700MB to ~200MB; they had multiple cells for each animated chapter menu. I've used VobBlanker for a long time just for blanking titlesets but never menus; I am quite pleased with the results (I was leary that my menu would be f***ed up, as I've had that in the past with other programs).

[jsoto]

Thanks for your good feedback, guys. It motivates me to continue working...
jsoto

[dragongodz]

Thanks for your good feedback, guys. It motivates me to continue working..
a big thank you in appreciation of the work you are doing. i know fully well how rare thanks are given...never enough. ;)

[zacoz]

I think the number of views of the VobBlanker threads give some indication that there are alot of people out there who appreciate your efforts - explicitly stated thanks always means that much more though I guess. :thanks:

Maybe we need a separate Thank You thread for some of the key software contributors :D

[Adub]

I have a slight problem with VobBlanker v. 2.0.1.0
When ever I run a dvd through it, and I open up the end result in PowerDVD and click the play movie button and the menu just jumps right back to the begining of itself. No actual movie or anything. On one DVD I could go to the scene selection and it would work, but I just tried it on snatch with the scene selections and it jumped right back to the main menu. I am kind of a newbie with VobBlanker so any help would be appreciated.
P.S. I am trying Snatch again without blanking anything to see what happens.
I will post back with my progress.

Okay, Proccessing Snatch through VobBlanker with out touching it did exactly what it was supposed to, nothing. The movie worked flawlessly when I loaded it into PowerDVD.
I Shall try Snatch agian, but blank the full screen and see what happens.

[Adub]

Good news, It worked!
I guess what was happening was just an isolated case. It was with the movie Saints and Soldiers. it would just not allow me to play the movie with the play button.
Anyway, I do not blame VobBlanker. I think this is my fault. Thanks for a Great Program Jsoto. I really appreciate the work that you do.

[2COOL]

@jsoto

I did a simple rip of my Maid in Manhatten R1 backup and wanted to blank out my aspect ratio menu. When I opened it with v2.0.1.0, I got an error.

http://img217.imageshack.us/img217/4333/screenhunter0238ko.gif

I successfully loaded with v2.0.0.1. The loading stops at 87%. It's only with this DVD I have encountered this so far.

Update: I found out what my problem was. I was missing a Title VOB. Blanked my Title in VTS_02_0.IFO in PgcEdit and it loaded fine with VB.

[blutach]

You own Maid in Manhattan?????

:rolleyes:

Regards

[2COOL]

You own Maid in Manhattan?????You know, I kinda like J-LO's cinderalla-type movies but you should know that any DVD out of my line of taste are for "testing" purposes. ;)

[Chetwood]

I've just updated to this version but as with 2.002 I get the same error message when ripping an episode DVD:

Error reading input VOB: Unsynchronized

Curiously I also get this message when using Vobblanker as a first step instead of fiddling around with settings in PgcEdit. On top of that DVD Shrink encodes the complete DVD flawlessly. Any suggestions? Thx.

[jsoto]

Unsynchronized VOB means VobBlanker has found a pack which does not start with 0x01ba.
AFAIK, all packs (including the padding ones) have to start with 0x01ba.
May be it is a dummy of an ARccOS disk?

jsoto

[Chetwood]

MMh, I just ripped it with DVDD did not notice anything special. I'm also surprise that Shrink did not complain, usually it's the first to do so when analyzing a disc.

[jsoto]

Could you isolate the cell where VB complains? It should be easy looking into the log file.
After, try to extract the cell with VobBlanker. Does it complain again? (It is a different part of code, so if it does, we can assume there is an offending pack.)

If the cell is not too large, you can load it in VobEdit and try to find the offending pack, or you can email the cell to me.

jesus_soto_viso (-at-) terra (-dot-) es

jsoto

[Chetwood]

Well, the cell is 387 MB which is too large for my connect. In the meantime I've tried it with DVDRemakePro which also breaks off when processing this movie. So here is the log file, I'm pasting it cause I don't know how long it'll take the attachment to be approved:


Version 2.0.1.0. Starting new process:


=========== STARTING VTS_01 ====================
VTS 01: Opening IFO
VTS 01: Processing VOB (Menus)
--------------MENU VOB PREPARING PHASE-
VTS 01: Keeping Menu LU 01, PGC 21
NOTE: Deleted 11 unreferenced cells (the last ones of each VOBID)
--------------MENU VOB WRITING PHASE STARTED-
VTS 01: Blanking unref Cell VID/CID: 01/01
VTS 01: Blanking unref Cell VID/CID: 02/01
VTS 01: Blanking unref Cell VID/CID: 03/01
VTS 01: Blanking unref Cell VID/CID: 04/01
VTS 01: Blanking unref Cell VID/CID: 05/01
VTS 01: Blanking unref Cell VID/CID: 06/01
VTS 01: Blanking unref Cell VID/CID: 07/01
VTS 01: Blanking unref Cell VID/CID: 08/01
VTS 01: Blanking unref Cell VID/CID: 09/01
VTS 01: Blanking unref Cell VID/CID: 10/01
VTS 01: Blanking unref Cell VID/CID: 11/01
VTS 01: Blanking unref Cell VID/CID: 12/01
VTS 01: Blanking unref Cell VID/CID: 13/01
VTS 01: Blanking unref Cell VID/CID: 14/01
VTS 01: Blanking unref Cell VID/CID: 15/01
VTS 01: Blanking unref Cell VID/CID: 16/01
VTS 01: Blanking unref Cell VID/CID: 17/01
VTS 01: Blanking unref Cell VID/CID: 18/01
VTS 01: Blanking unref Cell VID/CID: 19/01
VTS 01: Blanking unref Cell VID/CID: 20/01
VTS 01: Blanking unref Cell VID/CID: 21/01
VTS 01: Blanking unref Cell VID/CID: 22/01
VTS 01: Blanking unref Cell VID/CID: 23/01
VTS 01: Blanking unref Cell VID/CID: 24/01
VTS 01: Keeping Cell VID/CID: 25/01
VTS 01: Keeping Cell VID/CID: 26/01
--------------MENU VOB WRITING FINISHED-
VTS 01: Cell data array filled (Menus)
VTS 01: Processing IFO (Menu)
Looping into Menu PGCs and cells
PGCN Pointer: Pointing Prev PGCN to itself in LU 1, PGC 21
Building VTSM_C_ADT table
Filling VTSM_VOBU_ADMAP table
VTS 01: Processing VOB (Titles)
--------------TITLE VOB PREPARING PHASE-
VTS 01: Keeping PGC 01
VTS 01: Keeping PGC 02
VTS 01: Keeping PGC 03
VTS 01: Keeping PGC 04
VTS 01: Keeping PGC 05
VTS 01: Keeping PGC 06
VTS 01: Keeping PGC 07
--------------TITLE VOB WRITING PHASE STARTED-
VTS 01: Keeping Cell VID/CID: 01/01
VTS 01: Keeping Cell VID/CID: 01/02
VTS 01: Keeping Cell VID/CID: 01/03
VTS 01: Keeping Cell VID/CID: 01/04
VTS 01: Keeping Cell VID/CID: 01/05
VTS 01: Keeping Cell VID/CID: 01/06
VTS 01: Keeping Cell VID/CID: 01/07
VTS 01: Keeping Cell VID/CID: 02/01
VTS 01: Keeping Cell VID/CID: 02/02
VTS 01: Keeping Cell VID/CID: 02/03
VTS 01: Keeping Cell VID/CID: 02/04
VTS 01: Keeping Cell VID/CID: 02/05
VTS 01: Keeping Cell VID/CID: 02/06
VTS 01: Keeping Cell VID/CID: 02/07
VTS 01: Keeping Cell VID/CID: 03/01
VTS 01: Keeping Cell VID/CID: 03/02
VTS 01: Keeping Cell VID/CID: 03/03
VTS 01: Keeping Cell VID/CID: 03/04
VTS 01: Keeping Cell VID/CID: 03/05
VTS 01: Keeping Cell VID/CID: 03/06
VTS 01: Keeping Cell VID/CID: 03/07
VTS 01: Keeping Cell VID/CID: 03/08
VTS 01: Keeping Cell VID/CID: 03/09
VTS 01: Keeping Cell VID/CID: 04/01
VTS 01: Keeping Cell VID/CID: 04/02
VTS 01: Keeping Cell VID/CID: 04/03
VTS 01: Keeping Cell VID/CID: 04/04
VTS 01: Keeping Cell VID/CID: 04/05
VTS 01: Keeping Cell VID/CID: 04/06
VTS 01: Keeping Cell VID/CID: 04/07
VTS 01: Keeping Cell VID/CID: 04/08
VTS 01: Keeping Cell VID/CID: 05/01
VTS 01: Keeping Cell VID/CID: 05/02
VTS 01: Keeping Cell VID/CID: 05/03
Error reading input VOB: Unsynchronized
VTS 01: Keeping Cell VID/CID: 05/04
WARNING: No Navs found!: outputting a blank cell
VTS 01: Keeping Cell VID/CID: 05/05
WARNING: No Navs found!: outputting a blank cell
VTS 01: Keeping Cell VID/CID: 05/06
WARNING: No Navs found!: outputting a blank cell
VTS 01: Keeping Cell VID/CID: 05/07
WARNING: No Navs found!: outputting a blank cell
VTS 01: Keeping Cell VID/CID: 06/01
WARNING: No Navs found!: outputting a blank cell
VTS 01: Keeping Cell VID/CID: 06/02
WARNING: No Navs found!: outputting a blank cell
VTS 01: Keeping Cell VID/CID: 06/03
WARNING: No Navs found!: outputting a blank cell
VTS 01: Keeping Cell VID/CID: 06/04
WARNING: No Navs found!: outputting a blank cell
VTS 01: Keeping Cell VID/CID: 06/05
WARNING: No Navs found!: outputting a blank cell
VTS 01: Keeping Cell VID/CID: 06/06
WARNING: No Navs found!: outputting a blank cell
VTS 01: Keeping Cell VID/CID: 06/07
WARNING: No Navs found!: outputting a blank cell
VTS 01: Keeping Cell VID/CID: 06/08
WARNING: No Navs found!: outputting a blank cell
VTS 01: Keeping Cell VID/CID: 06/09
WARNING: No Navs found!: outputting a blank cell
VTS 01: Keeping Cell VID/CID: 07/01
WARNING: No Navs found!: outputting a blank cell
--------------TITLE VOB WRITING FINISHED-
VTS 01: Cell data array filled (Titles)

PostCommands changed into Precommands in 0 PGCs of a total of 0

Finished with ERROR. Process Aborted and not completed


I'm quite certain this already happened before I maipulated some stuff in PgcEdit so I guess it's a badly authored DVD or something.

[blutach]

Feature suggestion

I wonder if it is possible to implement a multiple cuts per session. As we all know, right now, you can cut once, process and if you have more, you must do it all over again.

I suspect this might come in handy for many a user.

Regards

[jsoto]

@Chetwood
The problem is in Cell 05/03. I'm interested to know if VobBlanker is able to extract the cell (which means a bug in VB) or not (which probably means a corrupted VOB)

@blutach.
Yep, it could be done, but I'm not going to work on it. I have other priorities (cell splitting, external I-Frame to be used in motion2still). But, in fact, lately I'm a little bit lazy and I'm not working at all in VobBlanker...

jsoto

[blutach]

OK :) Have fun.

Regards

[Chetwood]

Same error message, so seems to be a corrupted bug, it stopped playing back in PowerDVD in the middle of the cell. Weird though that I could shrink it without any error messages, Shrink is usually more picky about what it processes.

[HKT3020_1]

Question concerning the latest build of Vob blanker, I'm not exactly sure but perhaps it was 2 versions before the current release available today but what seems to be happening is Vob blanker no longer updates the id tags for audio. In previous versions of Vob blanker I was able to strip audio tracks from the main movie and it would no longer be available on say...a Sony DVD player. What I find is after watching a few DVDs, the audio tracks even though are stripped are still there. This would mean I would have to use IfoEdit to remove the Id tags available for removed tracks. Is there a fix to this or just something that was left out by mistake? :confused:

[jsoto]

Yes, I've included the stream status clearing as an option (default unchecked) because some players do not work with a non consecutive audios in a PGC. If you want VobBlanker to clear the status flag, you must check
"Clear audio/subs status when blanking/stripping"

See http://forum.doom9.org/showthread.php?p=592918#post592918

jsoto

[MarkP]

I've just updated to this version but as with 2.002 I get the same error message when ripping an episode DVD:

Error reading input VOB: Unsynchronized

Curiously I also get this message when using Vobblanker as a first step instead of fiddling around with settings in PgcEdit. On top of that DVD Shrink encodes the complete DVD flawlessly. Any suggestions? Thx.

@Chetwood

Did you ever resolve this if you did can you share how as getting the same problem.

@jsoto

You mention in one of your replies about loading the offending cell into VobEdit can you explain what to do after that as have no idea.

I have narrowed it down to 1 cell which i cannot extract same error Unsynchronised

Any help greatly appreciated.

[Chetwood]

I solved it by re-ripping the DVD. This time there were no errors.

[jsoto]

@MarkP
Load the offending cell in VobEdit is just to see the problem, checking if all the packs start with 0x01ba, but not to fix it.
There is no way to fix the problem without loosing data... Unless you are able to rerip without errors.

jsoto

[voo_doo99]

@jsoto
I do not understand the intended use of the 'Final' and 'To be proc.' size boxes. Because when I skip the main titleset then 'Final' would show some confusing low size number. It would be really helpful if it shows the updated DVD size after each selected blanking and also the size reduction in MB, which will help to plan the amount of blanking needed. I use VB all the time but the current size reporting does not help at all. Could you enhance it?
:thanks:

[sweetness]

@voo_doo99
if you use the Use Input Folder option, you will see that the Final size will change to reflect the "real" size of you project.
if you skip a VTS w/o the Use Input Folder option that VTS is not copied into that working folder. then the size of your project is what is processed (incomplete).

i was going to suggest a "skip but copy option" but then i realized that would be the same as processing the VTS untouched.
BUT wait what about multi angle VTS? maybe after all it would be good option for those people that do not want to touch the original structure or working from an image. but then again maybe not. i don't know :confused:

[jinjin_jp]

Thanks very much for very useful program.
I have the problem when Motion2Still Menu in StarWars I, but not in StarWars III, I tried to know the reason, but can't.

The problem is only in chapter menu. When replay menu, no button isn't highlighted. There are 30 cells of chapter menu, not all is problematic, some are highlighted.

I think common fearure of these cells is that, button and highlited subpicture isn't in first part of the cell and appears a littele later.
In log of VobBanker processing, there is no error, but are warnings like below,
1)"WARNING:Truncating audio. Buttons start in the middle of cell:**" is 30, which are equivalent for cells of chapter menu, when setting 'with audio".
2)"WARNING: Something was wrong in subs size in Cell:**" is 14, which are parts of cells of chapter menu, when setting 'without audio".
StarWars III has has similar construction of menu, but button and highlited subpicture appears from first of the cell.
So I supposed "it is the reason?".

But
1)By deleting the first part of each cell in which isn't button and highlited subpicture, the problem wasn't fixed.
2)By Motion2Sill after processing with IfoEdit(MenuExtras), the problem wasn't fixed, too.
3)By Motion2Sill after processing with VobBlanker(Keep), the problem wasn't fixed, too.

And I'm confused because
WAR of the WORLD (2005) whose main menu is similar (button and highlited subpicture isn't in first part of the cell and appears a littele later) has no problem.

As other tests
1)SubEdit ends by error when input above VOB file processed by VobBlanker.
2)There is no problem when Motion2Sill Menu with MenuShrink.

Please help me.

[jeanl]

jinjin_jp,
I do remember the original star wars menus (1-2-4-5-6) were difficult ones to get right for menushrink. As you mention, star wars 3 works fine with menushrink. It's difficult to figure out exactly why vobblanker shows this error. There might be something unusual in the subpic data, or a problem that never happened before, by chance.

I'm interested in the kind of error that SubEdit reports after processing by vobblanker (or does it simply crash?!)

jeanl

[jinjin_jp]

jinjin_jp,
I do remember the original star wars menus (1-2-4-5-6) were difficult ones to get right for menushrink. As you mention, star wars 3 works fine with menushrink. It's difficult to figure out exactly why vobblanker shows this error. There might be something unusual in the subpic data, or a problem that never happened before, by chance.
MenuShrink(2.3) has no problem in STAR WARS III.
I remember MenuShrink beta0.800 had the problem, but after ver.1.00 no problem in STAR WARS III.

I'm interested in the kind of error that SubEdit reports after processing by vobblanker (or does it simply crash?!)
The screen when error occured is below, please see.
Error message is "Because the problem occurred, it quits SubEdit MFC Applications." in English.
http://img507.imageshack.us/img507/553/subediterror0511271se.th.jpg (http://img507.imageshack.us/my.php?image=subediterror0511271se.jpg)

By the way when using ver.0.59, it shows ver.0.58 incorrectly.
But the function of display of background video has no problem, it is easier to use, thanks very much.

[jeanl]

jinjin_jp can you send me just the beginning of the vob, or maybe the entire vob since it must be small, by email at jeanldvd at free dot fr? I'd like to make subedit a bit more gracious in its failing!
jeanl

[jinjin_jp]

@jeanl
O.K. I will send.
Should I send the file after processed by VobBlanker, not before processed?

[jeanl]

Thanks jinjin_jp

Vobblanker somehow created a faulty subpic pack, see this:

http://img483.imageshack.us/img483/5592/foo7vo.png (http://imageshack.us)

As you can see, the subpic pack has an offset to commands that larger than the subpic size itself... I've modified SubEdit to report the error ... before crashing!!!
Thanks!
Jeanl

[jsoto]

Strange... IIRC I did the test with SW I....
This seems to be the error:
2)"WARNING: Something was wrong in subs size in Cell:**" is 14, which are parts of cells of chapter menu, when setting 'without audio".
I'll look into it.

[jsoto]

Seems SWI R2 has not the problem...
@jinjin_jp
can you send me ( jesus_soto_viso at terra dot es ) just one faulty cell, before processing? You can extract it with VobBlanker.

jsoto

[jinjin_jp]

@jsoto
O.K. I will send you soon. I selected the cell(V/C-ID=27/1) which is pointed in jeanl's post.

[jsoto]

@jsoto
O.K. I will send you soon. I selected the cell(V/C-ID=27/1) which is pointed in jeanl's post.
Got it , thanks. I've seen the problem, but I'm afraid about modify the code to fix it, there are other DVDs that can be affected. So I need to think on it a little more and take my time here...

jsoto

[blueboyec]

Jsoto,

Any new updates? Was hoping you would add the ability to read ISO images.

Thanks for the great program!

BBec

[jsoto]

I'm woking on it, but lately I'm very busy at work so I've few free time....

Anyway, I'm working on bug fixing, external I-frame in motion2still (for background changes), and finally cell-split.

No plans to read ISO images...I think it is out of scope of VB.

jsoto

[jeanl]

I agree jsoto! I think it would be a lot of work, and what would the use be? If you're stuck with an ISO file, simply mount it using deamon tool. I'm guessing vobblanker will work just fine then (as long as you don't try to process in place!).
jeanl

[FilipeAmadeuO]

...external I-frame in motion2still (for background changes)...
jsoto

It would be great to change the background just by importing and BMP/JPEG.
Is it possible to include in the next version ?