about function of finding buttons

[jinjin_jp]

Hello. I joined in this forum from yesterday, and sorry not good at English.

I have a question about function of finding buttons.

DVD : LION KING 3, VTS_13_1 to 4.VOB has buttons for game.

Result of each soft
(1)MenuEditFree(2.3.1) :can't find
(2)PgcEdit(0.5.7 and 0.6.0beta3) :can't find
(3)DvdReMakePro(2.6.7 and 3.0.1) :can find

Feature of DVD
VTS_13,PGC_1(VMG title 40) is main movie.
VTS_13,PGC_2(VMG title 41) is movie for game which is same as main movie.
PGC_1 and 2 have common cells and multiangle.
PGC_1 is angle 1, and PGC_2 is angle 2.
Cells of angele 2 have buttons for game.

I suppose the reason of difficultty to find butons is that position and size of button is more than one in one cell.

Matrix 1 has resemble feature ,that has PGC of main movie and PGC of extra (appear white rabbit).
These two PGCs have common cells and not multiangle but interleave, but can find buttons.
I suppose the reason of possible to find butons is position and size of button is one in one cell.

Does anyone have information about this?

[r0lZ]

Have you tried the File -> Find BOVs function of PgcEdit?

The BOVs (Buttons Over Video, ie buttons in title domains) are scanned by default when the DVD is opened only if the option to scan them is ON. See Options -> Automatically launch BOVs finder when the DVD is opened.

[jinjin_jp]

Have you tried the File -> Find BOVs function of PgcEdit?

The BOVs (Buttons Over Video, ie buttons in title domains) are scanned by default when the DVD is opened only if the option to scan them is ON. See Options -> Automatically launch BOVs finder when the DVD is opened.

Thanks for the reply.
Yes, I have tried the function of PgcEdit, and I usually set this option on.
I have confirmed automattically scannig, the result indicate 'not found'.

[r0lZ]

Even if you scan 1 VOBY every 1 VOBU, and you set the Check for multiple Set of BOVs in the same cell option on?

Could you search for a nav pack with buttons in VobEdit, and report here the highlight status and number of buttons and groups in that nav pack?

[jinjin_jp]

Thaks very much.
The problem has been solved by scanning 1 VOBU every 1 VOBU.(20 buttons was found)
I also tested to scan 1 VOBU every 2 VOBUs, so buttons were not found.

And the result is same, if check or not for multiple Set of BOVs in the same cell option on.

Do you mean better to have the report about buttons, even if the problem was solved ?

[r0lZ]

Do you mean better to have the report about buttons, even if the problem was solved ?No, thanks. But I am curious. If you can isolate one small VOB cell that caused the problem, please send it to me ( pgcedit <at> tiscali <dot> be ). You may extract the cell with VobBlanker. Thanks in advance.

[jinjin_jp]

@r01Z:
I've prepared the file.
But its size is 15MB, in spite of selecting minimum size cell.
Which should I send you the file itself, or the one to have cut a part?
I am anxcious for change its charactaristics by cut, because it is composed of following,
<1.no button, 2.appear one button, 3.excahnge to another buttun at anothor location, 4.no button.>

[r0lZ]

Hum... 15MB is too much to be sent by mail.

If you have a large band connection, you may send the cell with yousendit (http://www.yousendit.com/). If it's too large for you, don't worry. I don't need it absolutely. Thanks anyway.

[jinjin_jp]

@r01Z:
I've send the file. Please, receive.

[r0lZ]

Thanks!

[r0lZ]

OK, I've seen your cell. There are several sets of buttons in the same cell.
This means that the same button is redefined several times in the cell.

PgcEdit doesn't support multi-sets. Therefore, if you edit it, you will loose the redefinitions, and keep only the first definition. That may be a problem, especially if the command is redefined. But generally, multi-sets are used to move the button around, or to change the subpic to animate the button.
Of course, a multi-sets button is counted as 1 button in the final count of buttons.

When PgcEdit scans the VOBs for buttons, it searches the first VOBU, and then one VOBU from time to time, until it reach the end of the cell. The last VOBU of the cell is always checked. If one button was found, it scans backward until it finds the first cell with buttons.
You have to scan every VOBU because the button doesn't appear in the first VOBU of the cell, and is not present neither in the last one. Scanning every VOBU ensures that a button cannot be missed.

[jinjin_jp]

Thanks very much for your kind explanation.
I was tested by TraceMode of PgcEdit.
(1)After scan 1 VOBU every 1 VOBU, the warning as you said was indicated at corresponding part.
(2)After scan 1 VOBU every 4 VOBU, there was no button any part of this PGC.

[jinjin_jp]

Please help me about one more quistion.

Is it right or not?
This two are different feature,
(1)Buttons can't be found after scanning 1 VOBU every 4 VOBU (sometimes), when button is not neither in the first VOBU nor the last one.
(2)PgcEdit doesn't support multi-sets.

Because I tested about the file send you.
I created IFO from the file, and tested by PgcEdit.
The result,
(1)One button was found by scanning 1 VOBU every 4 VOBU.
(2)When use TraceMode, the process was interrupted with error.
Erroe Message : can't read "::buttons::butsinfo(pgc,1,22,1,numsets)": no such element in array

[r0lZ]

Most of the time, a button can be found even at 1 VOBU every 30 VOBUs. In fact, your example is the first one I hear about where it doesn't work. My method: start scanning at every 30 VOBUs. If at least one button is found, then rescan once at every 1 VOBU. If the total number of buttons found change, then the next time you open the DVD, use every 1 VOBU, else, you can safely use 30.

PgcEdit is able to scan for multi-sets, but don't process them. It just warn you in this case.

The error you reported has been fixed in v0.6.0 beta 6. V0.6.0 final will be released soon.

[jinjin_jp]

Thanks.
I understood to need distinguish 'not found buttons' and 'not support multi-sets'.

I'm looking forward to be released v0.6.0 beta 6, V0.6.0 final .

[jinjin_jp]

My method: start scanning at every 30 VOBUs. If at least one button is found, then rescan once at every 1 VOBU. If the total number of buttons found change, then the next time you open the DVD, use every 1 VOBU, else, you can safely use 30.
Additional information (sorry if already known)

DvdReMakePro has the similar function. It can find buttons of this example.
There is the option of setting 'shortest BOV duration for search mode',
and the unit is 'sec' different from PgcEdit'VOBU', and sellected from 0.5/1.5/3/9/15/no, and default is 3 sec.

[r0lZ]

I know DRM uses a different method. But I don't know exactly how it works.
My method is based on the IFO VOBU_ADMAP table, and is somewhat faster, but I cannot know for sure what will be the average elapsed time between the scanned Nav Packs.

[jinjin_jp]

Thanks. I've been using PgcEdit usefully and helpfully, whatever the method is.

[jinjin_jp]

I tryied with PgcEdit0.6.0beta6 about above demuxed cell.

-------------------------------------------------------------------------
From version history
F. Fixed some bugs in the Find All function: the line number (when the target
was a pre, post or cell command) and the cell number (when the target was
a button or BOV) were off by 1, and the button group was not always
correctly displayed.
-------------------------------------------------------------------------

I comfirmed to fix, the result was successful.
Thanks.

[blutach]

Yup - that's a fix for me, too.

Regards

[jinjin_jp]

Even if you scan 1 VOBY every 1 VOBU, and you set the Check for multiple Set of BOVs in the same cell option on?
@r01Z
I would like to know about the option "the Check for multiple Set of BOVs in the same cell option on".
Normally 'ON' or 'OFF' of this option dosen't change after setting either once.
But the case of SPIDERMAN is different.
Either 'ON' or 'OFF' of this option was, to see the screen of 'Find VOBs' before 'Open DVD', this option is alredy 'ON' and the letter is red colour.
I suppose the reason,
menu is scanned at first everytime, and menu of this DVD is multiple set of BOVs, so PgcEdit expects the possibility is high VTST is same and recommend to set this option 'ON'.
What is the actual feature and reason, please?

And about another information about this DVD,
PgcEdit recongnized this menu as multiple set of BOVs, but DvdReMakePro seems to do as not multiple one.
One of the number of multiple set PgcEdit scanned is over 57 but impossible to know accurate number because the warning screen is too large to fit out of the screen.

[r0lZ]

You're right. The menu buttons are always fully scanned. If PgcEdit finds multiple sets of buttons definitions in a menu cell, it turns ON the option to scan for multiple sets of BOVs automativcally, and highlight the option in red in the GUI.

I don't understand why the warning is so big. Have you selected a very large default font?
Anyway, I will verify that...

[jinjin_jp]

You're right. The menu buttons are always fully scanned. If PgcEdit finds multiple sets of buttons definitions in a menu cell, it turns ON the option to scan for multiple sets of BOVs automativcally, and highlight the option in red in the GUI.
Thanks. I understood.

I don't understand why the warning is so big. Have you selected a very large default font?
Anyway, I will verify that...
I think font isdefault.
I attatch the image file of the screenshot. Please see it.
So I can't click 'ok' button in the bottom of GUI.

[r0lZ]

Oh, yes, I understand. There are too many lines in the message box, right?

I have changed the message to display the number of sets in the first line, and the number of lines with the starting LBA for each set is now limited to 30.

[jinjin_jp]

Thanks.
I found this change of feature in 0.6.0.beta10.
(It isn't written in 'version history'.)

[r0lZ]

Hmm, I haven't announced beta 10 yet!
It's an internal release only. The main change is the first attempt to implement the burn function under Linux and Mac OSX.
Don't use it yet, because there are still many bugs in the Unix part.

But yes, I have fixed the problem of the big dialog.

[jinjin_jp]

I'm sorry. I'll take care not to try not-announced version.