Log in

View Full Version : VobBlanker 2.1.2.0 beta (now beta 13)


Pages : 1 2 3 4 [5]

Sir Didymus
27th December 2006, 12:38
...
And thanks to your last figure, I've learned also another thing: apparently, you cannot use a JumpSS from the VMGM to the VMGM, but you can do it from a VTSM to itself!
Why should it be simple when it can be complex?!

So, at the end it isn't complex... It's just totally wrong... :scared:

Apologise for posting the mistake...

And a big thanks to mpucoder and President for pointing it out...

Sigh.. after destroying some confidence we may have had on some sw verification tools, we are making now nice progresses, discovering bugs also in the old "reference" books...

Well, using "we", but I speak of myself, of course... :o

Cheers,
SD

Robotik
27th December 2006, 23:25
No! it is legal to use JumpSS from VMGM to other VMGM PGCs

goodie then! [relieved] thx!

So, at the end it isn't complex... It's just totally wrong... :scared:
Apologise for posting the mistake...


personally i'm rather happy that all my dvds are all right! moreover, we all learn from our (and each other's) mistakes.

also, it's good to see that my demi-gods are human after all :)

[Tobi]
27th December 2006, 23:36
@ jsoto

Is there already a new beta ?
I have not read everything and do not know what is changed or not. The beta 13 crashes, with a certain constellation which I have found on different DVDs.

The last what in the process log stands is the following:

WARNING: nuPGCs was different from the value stored VTS_TMAPTI 2. Fixed
Note: PGC 1 is too short. No entries in TMAPTI are created
Added 0 entries in TMAPTI of PGC 1


Then the VobBlanker crashes and quits itself.

jsoto
28th December 2006, 01:56
;922121']@ jsoto
Is there already a new beta ? No, I was just finishing the help file modifications to do a full release.
;922121']The beta 13 crashes, with a certain constellation which I have found on different DVDs.

The last what in the process log stands is the following:

WARNING: nuPGCs was different from the value stored VTS_TMAPTI 2. Fixed
Note: PGC 1 is too short. No entries in TMAPTI are created
Added 0 entries in TMAPTI of PGC 1 Could you send me the details? (IFOs before and project file.) Please specify which is the VTS that make VobBlanker crash

jsoto

SYL
28th December 2006, 20:09
I would like to congratulate you for this job, VobBlanker is very good, I’ve being using a lot version 2.1.1.0 and used beta 8 and 10 one or two times with out any problem, and thank you for it be totally free.

I would like to make some suggestions although being in the final phase of the update, in the “CELL in TITLE” and or in “PGCs in Selected TitleSet” modes you would show the final size and the initial size too, for the case we cut some part of the cell, like the credits, or strip some audio streams, for example.

In the “CELL PREVIEW/ CUT MODE” you would put the quantity of Mega Bytes as the slider is running, not only the Sector(lba).

In the initial and final size of the DVD it would be good to put the difference between the final size and the size of a DVD5, and this size would be edited by the user having a default value like 4464 MB in DVD Shrink.

I notice that we can’t strip streams and cut cells from a same PGC on the same process. Is it possible?

Thank you for the attention and this opportunity to interact with the users to improve this wonderful software. Keep going doing better with VobBlanker, we thank you a lot.
Have a great 2007.

jsoto
28th December 2006, 22:18
@[Tobi]
Thanks for the files. I've fixed the bug in the final release version

@SYL
Welcome to the forum.
I'm just releasing 2.1.2, but I'll keep in mind your suggestions.
But, no, it is not possible (and it will not be) to cut+strip in the same VobBlanker process.

jsoto

SYL
29th December 2006, 15:39
Thanks for the quick answer,

I have another doubt, when I begun to use VobBlanker I used to rip the DVDs just with DVD Decrypter and on some movies there were a delay to start the title menus and or the root menus, having the warnings, studios intros and some extras blanked, bigger than the original ones. When I passed to use RipIt4me it didn’t happen till now. Is it due to RipIt4me removes tiny cell, useless menu cells, etc?
Does the new function “Adjust Sectors” makes something like this?

Thank you.

jsoto
29th December 2006, 21:01
I have another doubt, when I begun to use VobBlanker I used to rip the DVDs just with DVD Decrypter and on some movies there were a delay to start the title menus and or the root menus, having the warnings, studios intros and some extras blanked, bigger than the original ones. When I passed to use RipIt4me it didn’t happen till now. Is it due to RipIt4me removes tiny cell, useless menu cells, etc?.I have very few experience with RipIt4me, but I can explain you how VobBlanker works:
- Blanking mode (Cells): VobBlanker does not delete the cells. They are replaced by a blanked one, and because it is non-seamless linked, the playback time (0.4 secs) is increased by the player to empty the buffers, and so on. This extra-time can be very different, depending on the player (a SW player, like PowerDVD is almost instantaneous)
- Blanking mode (PGCs): The cells are blanked, and the playback time is reduced to zero if the postcommands can be converted to precommands. If not (because there are cell commands, i.e) the complete PGC is played, all cells are blanked, but it can take some seconds...
- Deleting mode (PGCs): Only available in Menus domain. In this case the cells are really deleted, so the playback time is reduced to zero.

Other alternative is to use pgcEdit's "KillPlayback". The method is only a little bit more powerful in "automatic mode", but with user intervention (you can see the commands, the potential problems and decide what to do), sure you can bypass the playback of the PGC.

Does the new function “Adjust Sectors” makes something like this? Not at all. Adjust sectors is done as part of the normal VobBlanker processing, but in this new version two things have changed:
a) you can do it w/o processing the DVD
b) the new "Smart GAPs" creation feature, which put the files IFO & BUP in the optimum physical an d logical distance.

jsoto

EDIT:
Forgot to mention the amazing "Jump to PGC upon DVD insert" feature of pgcEdit: Absolutely recommended.
You can blank all the unwanted stuff, and finally, using this macro, the playback of the DVD will start exactly where you want, w/o any problems of blanked/bypassed cells.