VobBlanker 2.0.0.2 released

[jm1647]

Originally Posted by jsoto

@jm1647
Which problem do you have?

A) Buttons disappearing?. (not the ones at the bottom, the other ones) If yes, did the beta (working with a shared dll) work for you?
jsoto

Is there a different version of the beta floating around besides this one
VobBlanker_2002b9_exe.zip I see it has an earlier date than than the released 2.0.0.2 and was just wondering. If there is another give me a link and I'll try it. I found the link for VobBlanker_2002b9_exe.zip in the topic here @doom9.

Thanks

[jsoto]

Hi,
In this post you can find a beta of VB 2003, related with the "Buttons disappearing" issue.

But I'm going to release in a few days VB 201. Wait just one week.

jsoto

[jm1647]

@jsoto - Thanks for the headsup, I'll wait.

[CirTap]

@jsoto: have you had a chance to look at the "resize-window-problem"? I have v2.0.0.2
http://forum.doom9.org/showthread.ph...629#post676629
it happens for me, too, on 2 different machines, both XP/SP2 + ATI 9x cards -- in case it matters. oh, and I have the XP-yum-yum-look turned off, that is I use the "classic windows" theme/style/whatever.
display/screen resolution or whatever window-size I choose dosen't seem to have any affect, as well as if there's some content in the table or not (eg. program start or after loading the IFO). also, unlike in Sajan's example screenshot, the buttons here totally disappear as well as the rightmost column of the table. its left border is perfectly aligned to the second checkbox-row on both PCs.

editoops, how come I haven't seen your post above? :-)
anyway, I just downloaded 2003b3 and the buttons still jump off the window. btw. I have MFC42.dll v6.2.4131.0 in system32\ and (bizarre) v6.0.8665.0 in some "WinSxS\\x86_Microsoft.Tools.VisualCPlusPlus.Runtime-Libraries\...." folder as you ask for it in the other thread.

Have fun,
CirTap

[2COOL]

@jsoto

Just for confirmation...what's the process for doing a "mock strip" in VobBlanker. I've read it being mentioned but not thoroughly explained. Can there be an option to automate it?

[jsoto]

@CirTap,
Sorry, I do not have any clue for your problem... I cannot imagine why it does not work. Sure it is related with the initial coordinates I keep in memory, which seems to be wrong.
Just to confirm, could you check the menu dialog or cell lists dialog? (hit menu button in a VTS or Cells button in a PGC) Do they show the same problem? These dialogs are also resizeable, but the way how I coded it is slightly different to the main pane...

@2COOL

Process to mock strip in VB:
Select the VTS and the PGC to be mock stripped. Currently you cannot do a multiple selection.
Hit strip and keep all the streams.
Hit process!!.

Up to now, it is not easy to automate. You need a project file like this (you can write more VTS or more PGCs than the actual ones in the DVD, but if you put less than the ones in the DVD, the rest will be defaulted as KEEP):

[General]
InputPath=F:\TEST
OutputPath=E:\OUTPUT
[VTS01]
ActionVTS=PROCESS
ActionT01_01=STRIP
ActionT01_02=STRIP
ActionT01_03=STRIP
ActionT01_04=STRIP
....
[VTS02]
ActionVTS=PROCESS
ActionT02_01=STRIP
ActionT02_02=STRIP
ActionT02_03=STRIP
ActionT02_04=STRIP
....

But , the first thing I have to do is to support stripping in menu domain, currently not supported.

jsoto

[2COOL]

Originally Posted by jsoto

But , the first thing I have to do is to support stripping in menu domain, currently not supported.

Thanks jsoto! But couldn't I just process the whole DVD with the option to check/uncheck "remove PUOPs" options? By default, all streams are kept anyway. Basically, load IFOs and process. I'm more concerned about the Title domains than the menu domains for now.

[EDIT]I think I answered my question by just doing a VobBlanker test right now. It's about time I get my first cup of coffee for the day. :P

[jsoto]

Originally Posted by 2COOL

Thanks jsoto! But couldn't I just process the whole DVD with the option to check/uncheck "remove PUOPs" options? By default, all streams are kept anyway. Basically, load IFOs and process. I'm more concerned about the Title domains than the menu domains for now.

Not sure if I understand...
Do you mean an additional option to do a mock strip (pointer adjustments) when keeping? Seems easy... In this case it will be very easy to automate...
jsoto

[2COOL]

We all know that mock stripping in IfoEdit can be done but there is a bug with it on disappearing cell commands. Since Derrow is not around to fix it, I was hoping for an alternative and VobBlanker is my first option.

[jsoto]

@CirTap
Please check your PM.

@2COOL
Well, it is my intention to support "mock strip" in VB, (but not "in place"). I think the best way is to add an option which means to fix the pointers in keep mode.

To support mock strip "in place" (completely different concept to the option "use the input folder") requires a modification in how VB works, so I'm not motivated to do it...

jsoto

[2COOL]

Originally Posted by jsoto

Well, it is my intention to support "mock strip" in VB, (but not "in place"). I think the best way is to add an option which means to fix the pointers in keep mode.

Hmmm...I can accept this proposal. Would we also have a global option in keep mode to mock strip instead of just a single PGC?

[blutach]

You'd need to be able to mock strip the whole titleset not just a PGC - for example, what if a 2nd PGC had reused cells from the first?

Regards

[jsoto]

Originally Posted by blutach

You'd need to be able to mock strip the whole titleset not just a PGC - for example, what if a 2nd PGC had reused cells from the first?
Regards

Not really a problem. There are two different parts in a mock strip:
A) IFO pointers adjustments (VOBU pointers, sectors in ADT tables, etc)
B) VOB internal pointer adjustments (Nav packs)

Part A) is always done by VobBlanker. It always redo from scratch many tables in the IFO (Menus and Titles ADT & ADMAP and TMAPTI)

Part B) is done cell by cell. You could adjust only one cell and do not adjust the other ones (if you think they are correct). Up to now, VB automatically mark the cells to be adjusted if:
- They are the starting or ending ones in a title cut
- They have been stripped. (all the cells in the PGC are marked in this case)

But, I agree that, for practical purposes, it should be very interesting to have a "global option" to fix all the pointers (part B) in the case of KEEPing PGCs/Cells. In this way, the only thing you have to do is:
- Open the DVD with VB.
- Select the output folder
- Be sure the global option is turned on. Be sure the other global options like "Remove PUOPs" are preset with the value you want.
- Hit process. All the DVD will be mock stripped (well, currently, only titles domain).

jsoto

[CoNS]

Originally Posted by jsoto

Well, it is my intention to support "mock strip" in VB, (but not "in place"). I think the best way is to add an option which means to fix the pointers in keep mode.

To support mock strip "in place" (completely different concept to the option "use the input folder") requires a modification in how VB works, so I'm not motivated to do it...

But it IS possible to do a VobBlanker mock strip in the input folder, right? Like blutach and jeanl described in this thread (in the later replies). However, it seems like blutach is doing it a little differently than you described:

Originally Posted by blutach

just process in input folder. Select the VTS to mock strip (click on process for that one - or process all if you like) and then click on Process! No problems. You can actually strip and select all audio and cells, if you like but that takes longer.

So it's not necessary to click Strip and keep all the streams? Marking the VTS for "Process" is enough?

What is the difference between a mock strip "in place" and "in the input folder", then? The mock strip in place/in the input folder using IfoEdit (I'm using your instructions here) is really useful for both menus and titles, so it would be very nice to be able to do it in VobBlanker, too, and without the cell command bug in IfoEdit...

(just for future reference: jsoto has described the differences between mock strips in IfoEdit and VobBlanker respectively in this thread)

[jsoto]

Originally Posted by CoNS

But it IS possible to do a VobBlanker mock strip in the input folder, right?

Yes, but it is faster if you use two different physical drives for the input and output files.

Originally Posted by CoNS

So it's not necessary to click Strip and keep all the streams? Marking the VTS for "Process" is enough?

No, currently it is needed. Mock strip can be splitted in two parts:
A)IFO pointers adjustments
B)VOB internal pointer adjustments
Part A) is always done by VB (titles and menus), marking the VTS as process (processing titles and menus) is enough.
Part B) is done (currently) only if you mark the PGC as strip, (keeping all the sreams)

Originally Posted by CoNS

What is the difference between a mock strip "in place" and "in the input folder", then?

"in place":
Means to open the VOB, and modify directly in the input file. There is no backup. It is faster, because you only need to read/check/update some values in the nav packs. The rest of the packs are untouched (even more, you do not need to read them). As a drawback, you cannot recover the originals, because they are modified.
[EDIT] Well, actually you need to read all the packs, at least the first bytes, to classify the pack (video, audio,subs, stream number...). This info is needed to update the nav packs. [/EDIT]
"in the input folder"
This is related with VB. VB moves the original VOB to a backup folder, so to generate the new file all the packs have to be read and written. At the end of the process you will have two file sets, the originals (in backup folder) and the modified ones.

Originally Posted by CoNS

it would be very nice to be able to do it in VobBlanker, too

I'm going to add the feature.

jsoto

[CoNS]

Great, thanks! I bet it'll be widely appreciated!

[blutach]

@jsoto - for the final release is it possible to give a good rundown of what each option in the "More Options" screen does?

Many thanks.

Regards

[jsoto]

Originally Posted by blutach

@jsoto - for the final release is it possible to give a good rundown of what each option in the "More Options" screen does?

It is in the updated help file you should have. Is it not enough or not easy to understand? (My english is not too good)

@all,
I've found a major error in subs stripping feature, so I'll need some additional time to fix it before release the SW. So I'm not going to release it yet.

jsoto

[CoNS]

Originally Posted by jsoto

It is in the updated help file you should have. Is it not enough or not easy to understand?

Maybe you could extend the explanations in the mouseover toolstips? I have to admit that I'm one of those scoundrels that hardly ever open a help file for an app...

[jsoto]

I do not know how to code a multiline tooltip. Currently I'm limited to only one row in a tooltip.

jsoto