VobBlanker 2.1.2.0 released

[jsoto]

Here it is.

Full changelog

Added: Two MRU (Most Recent Files) menus added. One for DVDs and other for project files
Added: Option to split the cell in two when "cutting inside" a cell
Added: Buttons to go to cut points in preview
Added: Smart GAPs: If configured, VobBlanker guarantees the gap creating (if needed) creates an empty menu of a calculated size that guarantees a different ECC block and 1/2 turn physical separation.The menu is made by one unreferenced blank cell and padding packs. This allows the user to burn with Nero using the smart gap trick
Added: Warn the user if a substream is selected to be stripped and kept simultaneously.
Added: One Sequence Title PGC checking
Added: Splitting extracted file in 1 GB files in Cell extraction.
Added: Default folders configuration (output, input and auto-save)
Added: Registry keys to control (using regedit) HDD buffering and MRU lists size
Improvement: VobBlanker is now faster when input and output folders are in the same hard drive. (i.e checking "Use Input folder"). The improvement depends on the HDD and how it is configured. The difference could be minimum or more than two time faster depending on the HDD
Improvement: TMAPTI is always created from scratch. Entries are created to all PGCs even the Non one-sequence-title-PGC ones, Only the ones shorter than one sec (usually dummies) will be empty.
Improvement: The messages detecting pointers mismatch now show the detailed list of cells
Improvement: TMAPTI entries accuracy improvement.
Changed: VobBlanker automatically saves the log and project files if auto-save folder is configured.
Changed: When stripping, if the same substream is selected to be kept and stripped (in different tracks) VobBlanker will not remove the stream from the VOB
Changed: Numbering of subs and audio tracks from 0 to n-1 instead of 1 to n.
Changed: Default when splitting cells: add program/chapter
Changed: CFileDialog management changed internally. (No more assertion failures in Debug mode)
BugFix: VobBlanker backup folder was not deleted if the process was aborted.
BugFix: Replacing/blanking reused cells sometimes did not work fine.
BugFix: VobBlanker was not creating VTSM_C_ADT if it was cleared
BugFix: Sometimes, cutting Cells an extra Nav Pack was written.
BugFix: TMAPTI end byte was not always the last byte of last entry
BugFix: Deleting ADT & ADMAP menus tables in menus (when deleting all the cells) IFO was not compressed, and ADT & ADMAP title tables were not moved to previous sectors
BugFix: Menu stream Attributes were not cleared when deleting a zero bytes menu.
BugFix: VTS substreams list was wrong in the case of more than 8 subs
BugFix: The warning if a cut was going to create orphan subs was not always issued.


jsoto

[blutach]

Many many thanks jsoto. Huge work and great changelog.

Happy New Year :)

Regards

[BigCondor]

Thanks jsoto for all the hard work. Just looking at the log is really good enough!

Happy New Year everyone!

[linx05]

A big thanks to you. We've got VobBlanker out, now it is New Years Eve. Let the party start!

[r0lZ]

Nice present for the new year, Jsoto!

[Hubbabub]

Thank you very much for the new VobBlanker version.
VobBlanker is one of the must have dvd tools.

I'm still a learning newbie when it comes to editing dvd files.



Btw.
HAPPY NEW YEAR !

[dirio49]

Thanks, jsoto

Happy new year.

[Sir Didymus]

Thanks jsoto!
Your work is really much appeciated!

Cheers,
SD

[2COOL]

Many thanks ol' friend! ;)

[Dr.Khron]

Thank you very much, VobBlanker is an amazing tool.

However, would someone please explain this one to me?
I don't really understand it... does this have anything to do with the layer break on DL discs?

Added: Smart GAPs: If configured, VobBlanker guarantees the gap creating (if needed) creates an empty menu of a calculated size that guarantees a different ECC block and 1/2 turn physical separation.The menu is made by one unreferenced blank cell and padding packs. This allows the user to burn with Nero using the smart gap trick

[jsoto]

Guys,
Thanks for your posts, but don't forget I'm also accepting bug reports, if any :p (So many thanks posts are a little embarrasing...)

@2COOL
Glad to see you again!!

@Dr.Khron
Smart GAPs have nothing to do with DL. They are GAPs between the IFO and BUP (IFO's backup) files to guarantee a different error correcting block and to physically positioning the files with 1/2 turn offset in the DVD, so they cannot be affected simultaneously by the same radial scratch. There is a complete discussion in VobBlanker's beta thread. You can start reading here
http://forum.doom9.org/showthread.php?p=902262#post902262

There is another difference between GAPs created only with IFO internal pointers and VobBlanker's ones. Because VobBlanker's ones are done by a menu file (unreferenced, but a real file), they are honored by any burner SW, including Nero.

jsoto

[BigCondor]

Regarding to the post of editing chapters
http://forum.doom9.org/showthread.php?t=119911

blutech suggested a method of splitting a cell to adjust the chapter point. Wouldn't be a good idea to add merge cells in your future versions so that there won't be any extra cells after the adjustment?

[blutach]

Actually BigCondor, I see little benefit in merging cells if they are properly muxed to begin with. Plus, you may need more messing around with chapter points.

Regards

[Susana]

Graciass :thanks:

[BigCondor]

@blutach

Thanks, I see your point, sometime merging may create some issues. I just only want to minimize the number of cells. At extreme cases the number of cells may be doubled. But anyway, merging can be of use in some cases.

[wildchild77]

Another Thans for a great program!

I have had ver. 2.1.1.0 running on Linux Ubuntu 6.10 for a while now as well as on my WindowsXP box. Here are some screenshots under Ubuntu & Wine

http://www.geocities.com/wildchild778877/Screenshot-31.png

http://www.geocities.com/wildchild778877/vobblank3.png

[jsoto]

@BigCondor
Merging cells takes a lot of effort (similar to split them) and has not too much sense, so I'm not going to include it in VB...
But, here is a manual method (I've just tested it, and works fine):
- Extract with VB the cells (consecutive) to be merged in only one VOB file.
- Delete with pgcEdit all the cells except the first one (it should be good to have an option to do not process TMAPTI, in order to save time, but I didn't find it). Adjust programs and chapters
- Replace with VobBlanker the remaining cell with the VOB file from step one. VobBlanker will merge all the cells in only one.
-Adjust in pgcEdit the seamless flags (if needed)
-Adjust in pgcEdit all the navigation commands, deleting programs and chapters needs a deep analysis of the DVD navigation commands

You're done!.

@wildchild77
Ubuntu. Amazing visual effects using compiz. Try it if you didn't.
BTW, I've just tested VobBlanker in vista. It works fine, although there is a minor issue with the previews (like many other players) when using the new scheme with transparencies...Vista automatically changes to "classic" scheme.

@Susana
De nada, lo hago encantado. Es agradable ver compatriotas por aqui

Chapter editing:
VobBlanker 2.1.3 is going to have multiple split per cell in only one VobBlanker process. Wait and see..
Of course, programs/chapters navigation adjustments will be pgcEdit bussiness...

jsoto

[jsoto]

Merging cells:
I've found two minor issues with the manual procedure described in my previous post:
- Internal Vob pointers have to be adjusted, and VobBlanker does not turn on the internal flag automatically. So , for the moment, check "Fix always VOB SYNCI/SRI pointers in Titles"
- When deleting unreferenced cells, the fixing pointers phase seems to work with the original list of cells. That means, in some cases the pointers could not be fixed (depending on cells VID/CID numbering), and in others they are fixed twice (a waste of time). I need to check this more deeply..

jsoto

[BigCondor]

@jsoto
Thanks for your advice, I'll take note of that and test it when I have time. I think the process doesn't have practical advantage but it helps to get better understanding of DVD structure and I need some time to digest. In reality, I would rather mark the cells myself before authoring.

[wildchild77]

I just installed VobBlanker 2.1.2.0 on Ubuntu Edgy 6.10 using Wine Ver.0.9.28 and it keeps crashing at 98% - 99%. I have had good results using VobBlanker 2.1.1.0 on this same set-up. I did get a lot of warning messages on the newer version and will do some more testing

@jsoto sorry for hijacking this thread! I will post some of the errors and info in a new thread in the Linux section, any advice or thoughts on your part would be welcome.

[jsoto]

Which errors do you get?
Try disabling the MegaBuffer in the Registry
HKEY_CURRENT_USER/Software/jsoto's tools/VobBlanker/General/Write HDD using MegaBuffer

and let me know

registry in wine:
http://www.codeweavers.com/support/docs/wine-user/registry

jsoto

[wildchild77]

@jsoto I have started a new thread in the Linux section
http://forum.doom9.org/showthread.php?p=926741#post926741

Thanks for the link and info I will be doing more testing when I get the time, thanks again for the great little program!

[SYL]

@Dr.Khron
Smart GAPs have nothing to do with DL. They are GAPs between the IFO and BUP (IFO's backup) files to guarantee a different error correcting block and to physically positioning the files with 1/2 turn offset in the DVD, so they cannot be affected simultaneously by the same radial scratch. There is a complete discussion in VobBlanker's beta thread. You can start reading here
http://forum.doom9.org/showthread.php?p=902262#post902262

There is another difference between GAPs created only with IFO internal pointers and VobBlanker's ones. Because VobBlanker's ones are done by a menu file (unreferenced, but a real file), they are honored by any burner SW, including Nero.

jsoto

Can Smart Gaps cause a delay in the menus or in the movie on settop players?

And to burn with Nero using smart GAPs, do we have to enable any option in Nero or just burn as usual?

Thank you for VobBlanker.

[jsoto]

Can Smart Gaps cause a delay in the menus or in the movie on settop players?Not at all. They are made by unreferenced material. Never are going to be accessed by the settop (even corrupted, the DVD will work)
And to burn with Nero using smart GAPs, do we have to enable any option in Nero or just burn as usual?No. Nero does not honor the internal pointers of the IFOs, so you cannot burn DVDs with GAPs created only with them (Nero recalculated the pointers and removes the GAPs). With the smart GAPs created by VobBlanker, the menu file exists (unreferenced, yes, but it exists), so Nero accepts it w/o any problem.

jsoto

[Video Dude]

My older Toshiba SD-2700 player gives a disc error message for movie only DVD Shrink reauthored discs that I processed with VobBlanker using the smart gaps. I took the same DVD Shrink output, but used PCGEdit with 32K gaps and the disc played.

I have no problems with Smart Gaps on my other 5 players.

But I did find a solution. Before I used VobBlanker to create the Smart Gaps, I used PGCEdit and created a new menu. PCGEdit also created a 10 KB VIDEO_TS.VOB file. Then I processed with VobBlanker and the VIDEO_TS.VOB increased to 72 KB. Burnt with ImgBurn and the disc plays perfect in my Toshiba SD-2700.

[blutach]

That would seem to indicate Video Dude, that your Toshiba requires all VOBs to be referenced - smart gaps only inserts a file but totally unreferences it in the IFO.

Regards

[jsoto]

Well, I´m inserting unreferenced menus to be able to delete them after, if you change your mind, just adjust sectors again in VobBlanker w/o the smart GAPs option.

I can easily do the same than pgcEdit when inserting the GAPs (adding a PGC referencing the blank cell). The problem is how detect it later in order to remove it... (I'm not going to code the remove uncalled PGCs, like in pgcEdit 8).

I'll think a bit on this..

BTW, I've seen a lot of unreferenced menus in originals..., well may be at least one cell was always referenced..

jsoto

[blutach]

Seems this is player specific jsoto; and an old player at that.

Regards

[r0lZ]

Maybe it is sufficient to create the VOBU tables without PGC?

[jsoto]

VOBUS table (VOBU_ADMAP) and Cell Adress Table (C_ADT)are already created.

I'm convinced it is due Menu Pgc unit table PGCI_UT. Shrink (it was not standard) already complained about a 0 in the pointer (a non-exsistent table). Currently VobBlanker s creating the table (one sector) but completely empty, with #LUs = 0.

I'm going to add a never called dummy PGC (menu type none: no root, no audio, etc), and I hope Video Dude will be able to test it. May be it is enough, and the cell in the VOB will continue been unreferenced.

jsoto

[r0lZ]

... but PgcEdit's Delete Uncalled PGC will delete it! ;)

[jsoto]

And what happens if it is the last one?

[r0lZ]

In the menu domain, everything is deleted, including the VOBU tables. (In the title domain, the whole VTS is removed, unless a menu PGC is still called.)
Anyway, that's not really a problem, as VB is often used just before burning, and after whatever the user wants to do with PgcEdit.

[jsoto]

So, PGC Unit table is also deleted..

I'm wondering if the problem is a PGC Unit table existent but empty. May be it is enough to create one LU with zero PGCs..

Anyway, a never called dummy PGC does not enlarge the IFO and creating it is completely safe...

jsoto

[jsoto]

@Video Dude
Please try
http://download.videohelp.com/jsoto/betas/VobBlanker_2130b2_exe.zip
But be sure the original has no menu at all before apply VobBlanker's smart GAPs creation.
jsoto

[Video Dude]

I tested it and it works. The player played it with no disc error message.

Great programming. It worked on the first try. :)


Sorry if I gave you extra work. It seemed like the majority of players had no problems.

[jsoto]

Sorry if I gave you extra work. It seemed like the majority of players had no problems.
No extra work at all. I think the new IFO is more standard now.
jsoto

[Dr.Khron]

Doesn't ImgBurn also put in 32K padding for you?

Since I make all my ISO's with ImgBurn, is this feature in VobBlanker redundant? Will ImgBurn alter the padding that VobBlanker puts in place?


No. Nero does not honor the internal pointers of the IFOs, so you cannot burn DVDs with GAPs created only with them (Nero recalculated the pointers and removes the GAPs).

Is this true with ISO files as well?
I assumed that a properly padded ISO file would burn the same way regardless of burning app.

[jsoto]

Doesn't ImgBurn also put in 32K padding for you?Yes

Since I make all my ISO's with ImgBurn, is this feature in VobBlanker redundant? More or less... but VobBlanker also calculates the optimum physical position, so the GAP is usually larger than 32K
Will ImgBurn alter the padding that VobBlanker puts in place?No, ImgBurn (or pgcEdit) add the 32K GAPs if there is no menu file (or if it is shorter than 32K), but VobBlanker does create a menu file larger than 32K
No. Nero does not honor the internal pointers of the IFOs...
Is this true with ISO files as well?
I assumed that a properly padded ISO file would burn the same way regardless of burning app.
Nero recalculates the pointers in DVD-VIdeo mode. In ISO mode it "only" burns the iso image, w/o modifying anything (never tried, but I'm pretty sure..)
Using VobBlanker GAPs + Nero you do not need the ISO image creation.

jsoto

[blutach]

Just to add to jsoto's last point - you can use VobBlanker (http://jsoto.posunplugged.com/vobblanker.htm) and ImgBurn (www.imgburn.com), too, since it accepts DVD files for burning.

Regards