VobBlanker 2.1.3.0 released (6th-May-2007) - Page 4

jsoto · 16th February 2007, 22:30

Here is a complete description of the algorithm
http://forum.doom9.org/showthread.ph...262#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 · 17th February 2007, 02:40

Quote:

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. It isn't possible to see any longer?

Quote:

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.

Quote:

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?

Quote:

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 · 17th February 2007, 16:31

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 · 18th February 2007, 03:04

@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

Quote:

--> 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 · 19th February 2007, 00:35

Quote:

Originally Posted by jinjin_jp

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 · 19th February 2007, 00:38

Quote:

Originally Posted by jinjin_jp

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 · 19th February 2007, 09:27

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:

jinjin_jp · 19th February 2007, 15:50

@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 · 20th February 2007, 20:09

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 · 21st February 2007, 00:39

Quote:

Originally Posted by Surf

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

It 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.

Quote:

Originally Posted by Surf

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

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 · 21st February 2007, 23:44

it's beta 6 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 · 22nd February 2007, 00:23

Quote:

Originally Posted by Robotik

it's beta 6 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 · 26th February 2007, 00:23

VobBlanker_2130 beta7

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

jsoto

blutach · 26th February 2007, 02:17

Thanks jsoto!

Regards

outsiders71 · 3rd March 2007, 22:06

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 · 3rd March 2007, 23:14

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 · 4th March 2007, 01:04

Quote:

Originally Posted by 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

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 · 4th March 2007, 10:37

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 · 5th March 2007, 14:50

Quote:

Originally Posted by outsiders71

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!!!!

Regards

DuyNghia.Net · 12th March 2007, 07:58

VobBlanker 2.1.3.0 Beta 8 has been released on March 4 2007

Code:

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

16th February 2007, 22:30	#61 \| Link
jsoto Just a Member Join Date: Nov 2002 Location: Spain Posts: 2,067	Here is a complete description of the algorithm http://forum.doom9.org/showthread.ph...262#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 __________________ Web sites with my tools http://download.videohelp.com/jsoto http://jsoto.posunplugged.com/

19th February 2007, 09:27	#67 \| Link
Sir Didymus Registered User Join Date: Mar 2004 Location: Italy Posts: 948	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 + (TetaTetaTrack 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: Last edited by Sir Didymus; 19th February 2007 at 12:26.

21st February 2007, 23:44	#71 \| Link
Robotik da kid Join Date: Jan 2006 Location: Hungary Posts: 141	it's beta 6 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 Last edited by Robotik; 22nd February 2007 at 00:03.

26th February 2007, 00:23	#73 \| Link
jsoto Just a Member Join Date: Nov 2002 Location: Spain Posts: 2,067	VobBlanker_2130 beta7 BugFix: "Cut inside" splitting still was broken in some cases jsoto __________________ Web sites with my tools http://download.videohelp.com/jsoto http://jsoto.posunplugged.com/

26th February 2007, 02:17	#74 \| Link
blutach Country Member Join Date: Sep 2004 Location: is everything! Posts: 6,499	Thanks jsoto! Regards __________________ Les Only use genuine Verbatim or Taiyo Yuden media.

17th February 2007, 16:31	#63 \| Link
Sir Didymus Registered User Join Date: Mar 2004 Location: Italy Posts: 948	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

19th February 2007, 15:50	#68 \| Link
jinjin_jp Registered User Join Date: Jun 2005 Location: JAPAN Posts: 435	@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.

20th February 2007, 20:09	#69 \| Link
Surf Senior Kindergarten Join Date: Sep 2004 Location: here & there Posts: 417	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...

3rd March 2007, 22:06	#75 \| Link
outsiders71 Registered User Join Date: Oct 2005 Posts: 75	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

3rd March 2007, 23:14	#76 \| Link
jsoto Just a Member Join Date: Nov 2002 Location: Spain Posts: 2,067	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 __________________ Web sites with my tools http://download.videohelp.com/jsoto http://jsoto.posunplugged.com/

4th March 2007, 10:37	#78 \| Link
jsoto Just a Member Join Date: Nov 2002 Location: Spain Posts: 2,067	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 __________________ Web sites with my tools http://download.videohelp.com/jsoto http://jsoto.posunplugged.com/

12th March 2007, 07:58	#80 \| Link
DuyNghia.Net Registered User Join Date: Mar 2007 Posts: 11	VobBlanker 2.1.3.0 Beta 8 has been released on March 4 2007 Code: http://download.videohelp.com/jsoto/betas/VobBlanker_2130b8_exe.zip