VobBlanker 2.1.3.0 released (6th-May-2007)

[Robotik]

I'm using padding packs becasue they allow me to adjust exactly the number of sectors. If not, I would need a lot of blank cells, of all the possible different sizes. Other posibility is to use audio packs coded with silences, but in the case of growing an existing menu, the same audio parameters (code, bitrate, # of channels, etc) should be used...too complex.


i've seen 1-frame blank cells without audio/subs up to 300 kB on commercial dvds, i don't know how they do it, but anyway, yeah, i don't think it's worth the effort to figure it out.

does ImgBurn accept dvd files for input? that way i can pass Shrink for iso creation. (i'm not at home right now, can't check it)

[r0lZ]

Yes, ImgBurn v2 has a Build mode to burn directly the DVD files to disc (or to create an ISO.) Very nicely done! Try it!

[Robotik]

thanks, it seems i'm going to change my habits

[jsoto]

Sorry
beta 3 has an internal pointer corrupted (TMAPTI). I think it wasn't dangerous, because TMAPTI is built from scratch, but you never know, so please use beta4.

jsoto

[blutach]

@jsoto

I am getting Runtime error 9 in DVD Rebuilder (http://dvd-rb.dvd2go.org/) after using smart gaps in VobBlanker (http://jsoto.posunplugged.com/vobblanker.htm) Beta 4.

Was this not fixed somewhere?

Regards

[jsoto]

@jsoto
I am getting Runtime error 9 in DVD Rebuilder What does Runtime error 9 mean?. I'm not too familiar with DVD-RB... The DVD to be used as input in DVD-RB opens fine in shrink, doesn't it?

Was this not fixed somewhere?No, I do not remember that.

May be DVD-RB does not like padding packs... I'll do some tests this weekend.

jsoto

[blutach]

Hola Jesus!

Runtime 9 is some sort of error that DVDRB doesn't like the input. I'll follow up with jdobbs as to exactly what it is.

I have done some more tests. It croaked on a VOB of 10k the first one inserted by smart gaps - I thought this was a strange size because it wouldn't get a 32k gap in total). Other VOBs with padding packs were accepted. Perhaps the frame was incomplete, though this is unlikely. I removed all small VOBs inserted by VB with FixVTS and ran Adjust Sectors again. This time DVDRB is happy, including the padding packs.

May be input error on my part. In any event, it's silly for me to adjust sectors with smart gaps before Rebuilder.

I wouldn't worry for now.

Thanks for looking into it for me.

Regards

[jsoto]

It croaked on a VOB of 10k the first one inserted by smart gaps - I thought this was a strange size because it wouldn't get a 32k gap in total).
It can happen in the case of a small title VOB. If the VOB is too small, VobBlanker creates a menu VOB to shift the BUP up to 1/2 turn, and the result can be any size (minimum 10K, which is the blank cell itself).

I wouldn't worry for now.OK, but if I find some time I'll do some tests..

jsoto

[jsoto]

Seems I've broken the "split when cutting inside" feature in latests betas... Don't worry, you'll notice if you try to use it, because VobBlanker stops with an error.
jsoto

[jinjin_jp]

I tested to creat small gap.
At first I prepared DVD-Video by DVDShrink Re-Author mode.
It arranged altenatively 13 VTSs that odd number is 8KB and even number is about 600-1000MB.
The result (newly created VTS) are
VIDEO_TS.VOB：66KB(*1)
VTS_01_0.VOB：60KB(*2)
VTS_03_0.VOB：82KB
VTS_05_0.VOB：96KB
VTS_07_0.VOB：112KB
VTS_09_0.VOB：126KB
VTS_11_0.VOB：138KB
VTS_13_0.VOB：34KB(*3)

(*1) I thought that innner file is 32KB.
(*2)I thought that more outer file is bigger. Should I see adding VTS_01_1.VOB(8KB)? It is 68KB and bigger than VIDEO_TS.VOB.
(*3)I thought that more outer file is bigger.
The result was not what I thought. Is there my misunderstanding?

Regards.

[jsoto]

Here is a complete description of the algorithm
http://forum.doom9.org/showthread.php?p=902262#post902262

In the VMG , more or less 72KB are required (you have to substract the IFO size). This means 1.5 turns, becasue 0.5 turns is not enough to guarantee 32KB
The same for the first VTS...

And, in the last VTS it can be 34KB.., because there is more room per turn

jsoto

[jinjin_jp]

Here is a complete description of the algorithm
http://forum.doom9.org/showthread.ph...262#post902262
Thanks for the explanation. I read through,(It serves as a reference to me though I can't understand so much.)
But I can't from the link (http://www.megaupload.com/?d=HRUNZWRN). It isn't possible to see any longer?

In the VMG , more or less 72KB are required (you have to substract the IFO size). This means 1.5 turns, becasue 0.5 turns is not enough to guarantee 32KB
The same for the first VTS...
Quote from your another post(#89) in the thread (http://forum.doom9.org/showthread.php?p=904047#post904047).
If VIDEO_TS.IFO final size is 16 KB after the processing...
The optimum size of the gap is 29KB -16KB = 13KB, so the starting point of both files (IFO & BUP) will be separated by 29KB (1/2 turn), but adding one turn to be larger than 32 KB
13KB+59KB= 72KB.
(1)VIDEO_TS.IFO final size is 20 KB after the processing.
.....the optimum size of the gap is 29KB -20KB = 9KB.
.....one turn to be larger than 32 KB, 9KB+59KB= 68KB.
----->created VIDEO_TS.VOB = 66kB.
(2)VTS_01_0.IFO final size is 18 KB after the processing, and VTS_01_1.VOB = 8KB.
.....the optimum size of the gap is 29KB -18KB -8KB = 3KB.
.....one turn to be larger than 32 KB, 3KB+59KB= 62KB.
----->created VTS_01_0.VOB = 60kB.
The result is almost same as you say, but each seem to be short by 2KB. Where did I miscalculete?

And, in the last VTS it can be 34KB.., because there is more room per turn
This means like below?
(3)VTS_13_0.IFO final size is 18 KB after the processing, and VTS_13_1.VOB = 8KB.
.....the optimum size of the gap is 60KB(this is my assumption) -18KB -8KB = 34KB.
.....no need to one turn to be larger than 32 KB.
----->created VTS_13_0.VOB = 34kB.

Regards.

[Sir Didymus]

Hi jinjin_jp !

Regarding the link, sorry for the trouble...
It depends I don't have a personal permanent area where to leave the document...
Well, it seems it was not a good idea to use Megaupload... Let's see if Sendspace is better...

here is the new link:

http://www.sendspace.com/file/0bjnur

I edited the broken link also in the original discussion.

Concerning the difficulties to understand the content, please consider that in the following page of the same discussion, a sample of "C like" code was also presented, as a reference...

Finally, since English is not my mothertongue, I admit the lack of synthesis and the very bad description in the referenced thread is entirely due to my faults. I am sure you understand what I mean... ;-)

In case you need further clarifications on the algorithm, please feel free to get in touch with me via PM...

Cheers,
SD

[jinjin_jp]

@Sir Didymus
Thanks for the new link. I almost understood about calculation except for several. May I ask question?
I couldn't understand
(1)the meaning of "Recording size(bit)" = "User Data Size(bit)" *1024/512.
and what I wanted to most know is
(2)how to calculate 59KB(29KB) and 142KB(58KB) of
--> 59 KB of data is the track lenght in the inner radius (24 mm of radius from the disc center); the storage of half track is 29 KB
--> 142 KB of data is the track lenght in the outern radius (58 mm); half track takes 71 KB
from xsl sheets.

Regards.

Edit(add)
I tried to calculate with using sheet ....
(1)in the inner radius:
INPUT User Data Size(MB) = 0.059 (=59KB)
if R1 = 24.8mm (I think R1 correcpond to area of files before smart gap.)
Nr of tracks corresponding to User Data Size =0
Angular remainder (in radiants) = 6.28 (I think 1 turn is pi x2).
(2)in the outer radius:
INPUT User Data Size(MB) = 0.142 (=142KB)
if R1 = 59.7mm (I think R1 correcpond to area of files before smart gap.)
Nr of tracks corresponding to User Data Size =0
Angular remainder (in radiants) = 6.28 (I think 1 turn is pi x2).

[jsoto]

The result is almost same as you say, but each seem to be short by 2KB. Where did I miscalculete?
2 KB is one pack. The error can be due a rounding or something like this. I'm not going to investigate it... it's only one pack

jsoto

[jsoto]

This means like below?
(3)VTS_13_0.IFO final size is 18 KB after the processing, and VTS_13_1.VOB = 8KB.
.....the optimum size of the gap is 60KB(this is my assumption) -18KB -8KB = 34KB.
.....no need to one turn to be larger than 32 KB.
----->created VTS_13_0.VOB = 34kB.

Exactly.

[Sir Didymus]

Hi Jinjin_jp

As Jsoto say, errors within the minimum allocation unit for DVD (which is 2K) are not meaningful; playing a little bit with the xls you can notice that 2K of data correspond to 5 mm...

The test I did so far show that smart gaps in VobBlanker are working OK...

If you want some specific clarifications on the function and usage of the xls, please PM me. There is no need to jeopardise this thread with a long discussion on a minor feature of VobBlanker.

Let me just add few notes since it seems the original discussion was not clear enough about the steps performed in the xls, that are as follow:

User Data Size (MB) <-- Input to the xls
User Data size (bit) <-- User Data Size (MB) * 1024 * 1024 * 8
Recording Size (bit) <-- User Data size (bit) * 1209 / 512
Linear Size (mm) <-- Recording Size (bit) * Channel bit lenght

Some constants are used in the calculations; e.g.
R1 --> minimum radius of the data area, 24 mm.
Track pitch --> 74 micrometers.
Channel bit length --> 0,1333 micrometers for SL discs

Since:
Linear Size = Teta * R1 + (Teta*Teta*Track Pitch / (4 * pi)), it is possible to calculate the value Teta (angular position) as a function of the linear Size.

In order to use the xls sheet, no values should be changed, other than the input one, in green, (User Data Size in MB).

It's really easier to use it than to explain...

By playing with the xls, you can see that filling in the value 0,0571 MB, the angular remainder (in radiants) is 6,2819 and the Nr of tracks corresponding to the User Data is 0;
You can see that filling in the value 0,0572 MB, the angular remainder (in radiants) is 0,0097 and the Nr of tracks corresponding to the User Data is now 1;

It means that at the inner radius, in order to complete a whole revolution, to pass from track #0 to track #1, you have to fill in 0,0572 MB of data, corresponding to 58,57 KB

At the outern radius,

You can see that filling in the value 4482,3784 MB, the angular remainder (in radiants) is 0,0021 and the Nr of tracks corresponding to the User Data is 45944;

You can see that filling in the value 4482,5164 MB, the angular remainder (in radiants) is 0,0015 and the Nr of tracks corresponding to the User Data is now 45945;

The difference 4482,5164 - 4482,3784 is 0,138 MB of data, corresponding to 141,31 KB

The position:
Recording Size (bit) <-- User Data size (bit) * 1209 / 512 takes into account both the 8/16 EFMPlus modulation and the error correction scheme, based on:

Sector size (user data) --> 2048 bytes
Logical Sector Size (data unit 1) --> 2064 bytes (2048 + 12 header + 4 EDC)
Recording Sector Size (data unit 2) --> 2366 bytes (2064 + 302 ECC)
Unmodulated physical sector (data unit 3) --> 2418 bytes (2366 + 52 synch)
Physical sector size --> 4836 bytes (2418 x 2 modulation)

I hope everything is clear...

The way to apply the algorithm to generate smart gaps is showed in the following picture:

http://img93.imageshack.us/img93/6711/explainationsmartgapkt8.th.gif (http://img93.imageshack.us/my.php?image=explainationsmartgapkt8.gif)

[jinjin_jp]

@jsoto
Thanks for the reply. I understood.(I will not worry about a trifling thing(2KB) according to your advice.)

@Sir Didymus
Thanks for the explanation.
I understood "how to calculate 59KB and 142KB".
And I can know the process of calculetion i.e, "Recording size(bit)" = "User Data Size(bit)" *1024/512, but it is difficult and understandable for me.
I'll use PM as you say when asking more question. Please help me if I ask.

Regards.

[Surf]

Senor Soto.

Two leetle requests:

1.) Can you make it optional that whenever I extract a cell it is in one file instead of being in two? Example, 1st is 1gig and the second is 300mb. I had to use Decrypter to circumvent the need. BTW it is a 1.3gig cell which represents a tv episode.

2.) I made a boo-boo once and the speaker was set out...all of a sudden VOBblanker bursted out with OOOH SSSH*T !!! The house went into a commotion...

[jsoto]

Two leetle requests:
1.) Can you make it optional that whenever I extract a cell it is in one file instead of being in two? Example, 1st is 1gig and the second is 300mb. I had to use Decrypter to circumvent the need. BTW it is a 1.3gig cell which represents a tv episodeIt is already an option. In Save file dialog you'll find an option at the bottom. It has been included in VobBlanker 2.1.2.

2.) I made a boo-boo once and the speaker was set out...all of a sudden VOBblanker bursted out with OOOH SSSH*T !!! The house went into a commotion...That's an easy one. Turn off your speaker :D
or rename/delete/substitute the wav file DoneKO.wav. Don't worry, if the file is not there, VobBlanker won't complain, it just won't play anything.

jsoto

[Robotik]

it's beta 6 (http://download.videohelp.com/jsoto/betas/VobBlanker_2130b6_exe.zip) already! did i miss something?

btw, know it's yesterday's news but i have just tried the multiple split feature. it works like a charm! i'm really impressed, thanks a lot for it!

for anyone else as offset as i am here's a copy of the changelog from the Readme file:

Vers 2.1.3.0 beta 2
BugFix: Changing Cell number in preview was not updating Time and GOP type
BugFix: Special case where GOP type was not detected (was being marked as unknown)
BugFix: PGC unit table was being created empty in smart GAPs

Vers 2.1.3.0 beta 3
Added: Absolute sector in preview
Changed: Elapsed and duration times: hours are represented in one digit
Changed: Info in preview uses normal fonts. Deleted non-valid fields.
Changed: Errors compacted when loading a DVD with multiple errors in menus
BugFix: Only 98 VTS were supported
BugFix: Negative (wrong) pointers in IFOs made VobBlanker crash
BugFix: chapters table wrong when splitting cells
BugFix: Settings in main dialog were lost opening more settings dialog
BugFix: 32K smart GAP default was not always the same value

Vers 2.1.3.0 beta 4
BugFix: TMAPTI internal pointer corrupted. Bug introduced in beta 3

Vers 2.1.3.0 beta 5
Added: New key in Registry to activate log details when fixing packs
BugFix: "Cut inside" splitting was broken

Vers 2.1.3.0 beta 6
Added: Check the maixmum size of the output (menus and titles)
BugFix: In the case of 9 files in a VTS, the fixing packs procedure hanged

[jsoto]

it's beta 6 (http://download.videohelp.com/jsoto/betas/VobBlanker_2130b6_exe.zip) already! did i miss something?
No, simply I had forgotten to announce it...
BTW, there is still a stupid bug in "cut inside" (Cut+Split) feature...VobBlanker stops with error if the cell is not the first one in the VOB file. Will be fixed in beta7.

jsoto

[jsoto]

VobBlanker_2130 beta7 (http://download.videohelp.com/jsoto/betas/)

BugFix: "Cut inside" splitting still was broken in some cases

jsoto

[blutach]

Thanks jsoto!

Regards

[outsiders71]

jsoto:

A feature request if possible...

I love the cut feature with vobblanker, I can easily edit out scenes I do not want in my re-authored DVD. However sometimes there are multiple scenes in one cell that I want to cut. This means I will have to cut and process that cell X times. Is it possible that you could allow each cell to be marked and cut at multiple points instead of just one?

Thanks

[jsoto]

It could be done..., but if you're doing more than one "cut inside" I recomend you the following procedure (in only two runs)
1st run: Split the cell in as many parts as you need, better splitting in the end or beginning of the parts you want to cut. You don't need to add programs/chapters
2nd run: Cut the parts you do not want. There should be only one part to cut per cell
In this way, you won't have any problems of audio/video synchronization

jsoto

[outsiders71]

It could be done..., but if you're doing more than one "cut inside" I recomend you the following procedure (in only two runs)
1st run: Split the cell in as many parts as you need, better splitting in the end or beginning of the parts you want to cut. You don't need to add programs/chapters
2nd run: Cut the parts you do not want. There should be only one part to cut per cell
In this way, you won't have any problems of audio/video synchronization

jsoto

This would work if you're cutting out a whole scene or section, but for example in saw 3 with the naked woman in the chiller, there was a lot of cutting to do.

[jsoto]

Hmm.
May be, in your case, the best option would be to blank video in the VOBU, and keep the audio as it is to avoid synch problems.
But blanking VOBUs is not supported....

Regards

[blutach]

in saw 3 with the naked woman in the chiller, there was a lot of cutting to do.This was not a pun, was it outsiders71? Cutting/sawing/slicing/dicing - I am sure there was lots!!!! :D

Regards

[DuyNghia.Net]

VobBlanker 2.1.3.0 Beta 8 has been released on March 4 2007

http://download.videohelp.com/jsoto/betas/VobBlanker_2130b8_exe.zip

[goonix]

Hi jsoto!

I use VobBlanker every day for cutting, splitting or replacing parts of a DVD with great success. But now I miss an important function.

If I want to replace a menu with a seamless muxed intro cell, I have to replace both cells at once.

In the title domain, VobBlanker can replace on PGC and on cell level.
In the menu domain VobBlanker can replace only at cell level.

For that reason, I have to replace the menu in two runs and the transition from one cell to the next cell isn't seamless. Even if I set the seamless flag with PgcEdit, I can see a short flickering and hear a short hiccup in sound. Some players get confused when setting the seamless flag on a non-seamless transition (e.g. playing in slowmotion up from now or something else).

So my feature request:

Is it possible to add a replace function in the menu domain on PGC level to replace 2 or more seamless cells at one time?

goonix

[r0lZ]

I second that request.
And is it possible to enable the Split cell function in the menu domains?

[jsoto]

In the menu domain VobBlanker can replace only at cell level.
For that reason, I have to replace the menu in two runs and the transition from one cell to the next cell isn't seamless. Even if I set the seamless flag with PgcEdit, I can see a short flickering and hear a short hiccup in sound.
That does not make sense to me... If you have a replacing PGC made with two cells seamless joined, you can extract the cells to two different VOB files (with VobBlanker , i.e.) and replace both cells in only one run. The result will be a seamless join, although the flags won't be correctly set. Changing them with pgcEdit should be enough and your new menu should be fully seamless..
Where is the problem you have? I cannot see it..

In any case, I can take a look...I'm very busy these days but I'm going to have some hollidays in the coming days.

jsoto

[jsoto]

I second that request.
And is it possible to enable the Split cell function in the menu domains?
It's possible, but it will take a lot of work....
And, in the case of several LUs, well, you should split the same cell on all of them to keep them aligned (although this can be an user resposibility)

One single split point should be enough?

jsoto

[r0lZ]

Argh! I haven't thought at the LU problem! I think also that there might be problems with the highlights of the menu buttons...

Of course, a single split point is sufficient in most cases, and "better than nothing".

[goonix]

Hi jsoto!
If you have a replacing PGC made with two cells seamless joined, you can extract the cells to two different VOB files (with VobBlanker , i.e.) and replace both cells in only one run.

Thanks for this information. I never thought about the possibility to extract all seamless cells with VobBlanker before.
I have muxed them separately up to now and this leads to a non-seamless joint of course.

But now it works perfectly!

Since only one additional step is necessary, you can set this feature request to low priority. ;)

Many thanks again for this great tool.

goonix

[Robotik]

hi jsoto,

if it's request season again, may i ask you to remove two annoying popup messages?
one of them is the message you get when you export a cell, and the 'Split output in multiple files' is checked. could you please remove the 'Filename has to be "*_1.VOB"...' message when the file is <= than 1GB? and when it isn't, could it return to the 'Select Output File' dialog with the filename i tried to use still in the filename bar, and selected? that would save us some retyping.
the other one is the 'Do you really want to quit?' popup. i mean it is really useful, if i worked a lot with setting up everything for processing, and accidentally clicked on Quit, but no point using it in cases when no alterations done (e.g. just exporting some cells).

thanks a lot,
robotik

(i hope you don't take it as nagging, i'm really satisfied with VobBlanker, and use it daily, and am really greatful for you to make it available to all of us! :)

[jsoto]

hi jsoto,
one of them is the message you get when you export a cell, and the 'Split output in multiple files' is checked. could you please remove the 'Filename has to be "*_1.VOB"...' message when the file is <= than 1GB? and when it isn't, could it return to the 'Select Output File' dialog with the filename i tried to use still in the filename bar, and selected? that would save us some retyping.
I'll take a look...



the other one is the 'Do you really want to quit?' popup. i mean it is really useful, if i worked a lot with setting up everything for processing, and accidentally clicked on Quit, but no point using it in cases when no alterations done (e.g. just exporting some cells).
When clicking on Quit button it does not ask for confirmation....It asks if you click on X button in right top angle of the window or in the case of ALT+F4...
I think I'm not going to change this...

jsoto

[Robotik]

When clicking on Quit button it does not ask for confirmation...
you're right, i meant File -> Quit

thanks for looking into the other request.

[poolshark2014]

I just downloaded 2.1.3.0. beta 8 and for some reason everytime I preview a part of the movie which I want to blank VobBlanker always freezes. Is there any way to fix this annoying problem?

I am currently using 2.1.2.0 and have never had any problems except for those Sony movies that add like 90+ files to a movie disc.That is when I fire up Beta 8 but it will always freeze when I preview a part of any file.

[jsoto]

I just downloaded 2.1.3.0. beta 8 and for some reason everytime I preview a part of the movie which I want to blank VobBlanker always freezes. Is there any way to fix this annoying problem?
I suposse you're loosing the cells dialog (it closes and it shouldn't because it is a modal one, so the main dialog is disabled). If this is your case, try the popup menu (right clicking in the mouse) instead of the buttons on the right part of the dialog. Please let me know if this is your problem and if the workaround also works for you.
I'm completely lost with this bug. It has no sense at all (FYI, the pop-up menus calls the button method) Seems related with mfc42.dll and/or something strange in preview code...

jsoto

[blutach]

I am glad it isn't just me Jesùs! :) But, I am not happy for you.

Regards

[poolshark2014]

Well JSOTO it worked the way you told me but is it always going to have to be like that for me or is there going to be a fix?

[jsoto]

Well JSOTO it worked the way you told me but is it always going to have to be like that for me or is there going to be a fix?
As I said, I'm completely lost in this bug. I'll try to fix it, but I do not know how to do any advance on it..
jsoto

[SamuriHL]

jsoto,

I have an unusual question and possible request, however, I know right off that it's probably extremely difficult and a real pain to implement. Therefore consider this a wishlist item at best...I simply wanted to throw it out there and see what you think.

My question and possible request is this...is it possible to analyze the titlesets on a DVD so that when the green "preview" frame is found that VobBlanker could label that particular titleset as a preview? I know, this is a pretty exotic request and I completely understand if you outright say no to it, but, if it could be done, it might be useful to a lot of people. Auto labelling, and possibly having an option to auto skip, the known previews would certainly save people time.

Anyway, I just thought I'd throw the idea out there and see if it gets any traction. :) I know you're a busy guy, so, I don't expect miracles on this. I'm just simply curious if you're interested in the idea. Thanks!!

[jsoto]

It's possible, but requires MPEG decoding and to analyze the result. It also will take many CPU time...
So the answer is no, I'm not going to work on that

What VobBlanker can actually do is to mark all the PGCs except the main movie to be blanked, based in a duration analysis

jsoto

[SamuriHL]

Thanks for the reply! I fully understand the reluctance to work on that. I had a feeling it was going to be a little more than you'd want to take on. Not a problem at all.

Hmmm, I wasn't aware it could do that. I'll have to look into that one. Thanks for the tip!

[blutach]

I think its called autoblanking SamuriHL :)

Regards

[SamuriHL]

I think its called autoblanking SamuriHL :)

Regards

Helps to look through the menus, doesn't it? :D Yea, I found it earlier after jsoto mentioned it. I felt like an idiot after that. :) VERY sweet option though!! The other thing you can do is if you want to keep just a few extras is automatically blank everything and then unblank the stuff you want to keep. Awesome! I love VobBlanker...by far one of my favorite utilities!

[Surf]

Senor Soto,

How about nagging Jeanl to "program" a new preview thingy with sound? Helps in cutting...

BTW, I removed the "ohh sh*t" wav file :D