PgcEdit v0.4

[lark]

how about checking the returned BMP?
if it's totally black, ask for next frame and so on...

regards
t :)

[r0lZ]

I can't do that in Tcl programming language. It will be extremely slow! And the first frame not totally black will likely be almost tatally black, as most of the time, the black frame comes from a fade-in.
Furthermore, I've seen cases where the buttons are appearing over a frame showing something, but not yet the buttons labels.

I repeat, the Preview button may be used to see the full cell...

[2COOL]

Originally posted by r0lZ
ButtonDump.exe searches all the cells in the VOBs for buttons, and, if some buttons are found, it reports the first LBA with a number of buttons > 0. If none are found, it reports the first LBA of the cell. This way, the frame displayed in the menubutton viewer is always the first one that is relevant.OK..since ButtonDump.exe outputs the first LBA, couldn't you come up with a search function in the VTSM_C_ADT table looking for this sector value? When there is a match, you can get the other neighboring values like VOB ID, Cell ID, and even the end sector. If this is unfeasible then I'll wait for jeanl's input to this matter. Sorry to drag this subject farther but without vision there is no opportunity.

[r0lZ]

Of course. I already know the VOB/Cell ID, and finding the last LBA is not difficult. But, as i explained, this is not enough with the current dvd2bmp program to ensure that the returned frame comes from the correct cell.

BTW, the problem of the menubuttons showing the wrong frame was reported by skynetman here (http://forum.doom9.org/showthread.php?s=&threadid=85329&perpage=20&pagenumber=3#post571758).

[2COOL]

Originally posted by r0lZ
Of course. I already know the VOB/Cell ID, and finding the last LBA is not difficult. But, as i explained, this is not enough with the current dvd2bmp program to ensure that the returned frame comes from the correct cell. I was just trying to satify your requirements on your two methods you were proposing.

Œ
In PgcEditPreview.exe, a method developed by jeanl (called AutoLocate) is used to avoid showing the bad frame. This method works fine, although relatively slow. To be used, I need to pass the end LBA to the PgcEditPreview.exe as well.


Another method is to pass the VOB and Cell IDs to the program, so that it can verify that the returned image comes from the requested cell.

I really didn't know the required inputs dvd2bmp needed.

[r0lZ]

Originally posted by 2COOL
I really didn't know the required inputs dvd2bmp needed. That's the problem. dvd2bmp doesn't have the AutoLocate, and doesn't verify the VOB/Cell IDs, for now.

[r0lZ]

0.4.4 beta 7 (http://www.videohelp.com/~r0lZ/pgcedit/beta/PgcEdit_winexe_0.4.4beta7.zip) is released.

@$$$
The bug you submitted here (http://forum.doom9.org/showthread.php?s=&threadid=85329&perpage=20&pagenumber=10) was easy to find and fix. :) Thanks!

@blutach
The bug you submitted here (http://forum.doom9.org/showthread.php?s=&threadid=85329&perpage=20&pagenumber=10#post576588) was not so easy to find and fix. :( Thanks anyway!
I think it works now, but I've never been able to reproduce the exact behavior of what you explained.
When blanking a cell with buttons, the buttons informations were not correctly updated, and the PGC Selector was not correctly refreshed, and therefore was still showing the original number of buttons.
Furthermore, the menubuttons viewer was unable to show the blanked cell.
All the above problems are now hopefully fixed.

However, you said that the FOLLOWING PGCs were also impossible to see in the menubutton viewer. I don't understand why, so I'm not sure that this problem is also fixed. Could you try the new beta, and keep me informed of the results? Thanks.

[$$$]

The bug you submitted was easy to find and fix.Glad to hear that, and I can confirm it as well :)

$

[jeanl]

Originally posted by r0lZ

In PgcEditPreview.exe, a method developed by jeanl (called AutoLocate) is used to avoid showing the bad frame. This method works fine, although relatively slow. To be used, I need to pass the end LBA to the PgcEditPreview.exe as well. But, for speed purposes when parsing the menu VOBs, ButtonDump.exe doesn't report the last LBA. Another method is to pass the VOB and Cell IDs to the program, so that it can verify that the returned image comes from the requested cell.

Conclusion: as I said elsewhere, it's up to Jeanl!
OK, I think it wouldn't be too hard to make it work, looking for the next images that are still in the same cell, as defined either by its end LBA or by its VOB/CELL ID (easier).
There's a question for you r0lZ: if dvd2bmp could support that, what would the UI look like? A slider? A couple buttons to go right/left in the cell?
And I agree with you that it wouldn't be easy to detect whether the frame is black. Bugs Life has a menu that's a slow fade-in from black, so you'd get many near-black (but not totally black) frames...

Also, a question for the rest of you guys: If we were to pick just one video frame, would picking the last frame in the (button) cell be a better option? In other words, have you guys seen menu cells with buttons where the end of the cell fades out (and I'm not talking about the menu "outro")? I don't think it's possible since typically the video will loop for a menu (or have a still time).
So if dvd2bmp could locate the last frame in a given cell, wouldn't that be a better candidate to display the menu?

Jean

[r0lZ]

@jeanl
The last frame of a menu should be a good candidate, but when PgcEdit will have BOV support, there will be many case where the buttons dissapear before the last frame.
So, the good frame to show is the last frame with menubuttons. This will require to verify the number of buttons in the previous Nav Pack.

I don't know if the best solution will be a slider or 2 buttons to jump from frame to frame. Why do you need to know that now?

[jeanl]

Originally posted by r0lZ
@jeanl
The last frame of a menu should be a good candidate, but when PgcEdit will have BOV support, there will be many case where the buttons dissapear before the last frame.
So, the good frame to show is the last frame with menubuttons. This will require to verify the number of buttons in the previous Nav Pack.
I'm not sure I understand: when you have BOV, typically the buttons are shown for an extended period of time. This requires either a large/infinite still time, or cell-looping, right? In that case, how could the buttons disappear before the last frame? I would imagine they disappear in the "next" cell that you link to when the user clicks on something.
In any case, DVD2AVI should be able to get to the button info. I know that it reads all the info in the headers, whether or not it uses them!

I don't know if the best solution will be a slider or 2 buttons to jump from frame to frame. Why do you need to know that now?
I don't! I was just wondering, from a user perspective, what the best solution might be...
Jeanl

[r0lZ]

I agree that in 'normal' menus (even as BOV in title domain), this will probably never happend. But think at the White rabbit in Matrix. It appear at the beginning of a cell, for a few seconds, then disappear before the end of the cell.
If you select it when it is on screen, you jump to a bonus. When the bonus has finished playing, a resume is issued to the start of the cell, to continue the main movie.

[jeanl]

@r0lZ, OK I get it!

@Others:
By the way, you can also launch PgcEditPreview in a standalone mode (it's located in the bin directory that PgcEdit creates). You can then drag/drop your vob files into it, and it behaves more or less like DVD2AVI (minus a lot of the functionalities, plus automatic DAR handling). It won't remember its settings (position etc) in standalone mode though.
Jean

[r0lZ]

0.4.4 beta 8 (http://www.videohelp.com/~r0lZ/pgcedit/beta/PgcEdit_winexe_0.4.4beta8.zip).

I have introduced a new bug when trying to fix the bug reported by blutach. This version should work better when blanking cells.

Also, a bug in the Paste Replace editor function is now fixed.

PgcEditPreview.exe is also replaced by the last version, send by jeanl, with some little improvments.

[jeanl]

Originally posted by r0lZ
0.4.4 beta 8 (http://www.videohelp.com/~r0lZ/pgcedit/beta/PgcEdit_winexe_0.4.4beta8.zip).
PgcEditPreview.exe is also replaced by the last version, send by jeanl, with some little improvments.
Little? What do you mean, little?!"
;)
Jeanl

[blutach]

@rolz

Not good news, I'm afraid.

Using v 4.4 Beta 8

Just have the IFOs and the menu VOB in my folder.

PgcEdit gets hung up when trying to read the buttons (lower left says Reading menu buttons informations VTSM1). Button_dump.exe just hangs the PC.

Again, with unaltered menu - works fine.

Thought you would like to know.

Regards

[r0lZ]

Could you send me the original IFOs, and the offending VOB?
If it is too large to be send by mail, you may try to blank out some unnecessary cells (using VobBlanker, of course! :))
Thanks.

[blutach]

Update:

Mock stripped menu. This enabled PgcEdit to load OK, but still same problem. Can view menu PGC1, but no others, even though there are buttons.

Note: The menu cells were blanked with VobBlanker. I wonder if this is a problem for jsoto?

I will try to cut the menu down to size and email.

Regards

[blutach]

@rolz

Interesting thing I've just noticed:

Opened both VOBs in MenuEdit:

Original (untouched) - VOBIDs are consecutive (1-18)

Blanked VOB has VOBID out of order as follows: 1, 2, (this is the 5 button root menu and can be viewed in PgcEdit)
16, 17, (this is the subtitle menu - 13 buttons in VOBID 16 with VOBID 17 being blanked - unviewable in PgcEdit menu)
18 (audio menu - 5 buttons - untouched and unviewable)
5, 6, 7, ...14 (chapter menu - 10 cells, 56 buttons, untouched and unviewable)
3, 4 (blanked - these were features menus)Note: VOBID 15 is missing (it was unused and I guess VobBlanker stripped it).

Note: The PGCs were still associated with the correct VOBIDs. The only problem was that the Menuedit reported the VOBIDs out of sequence!

This is strange. I suspect that it is an issue for VOBBlanker, too.

Could this be a problem for PgcEdit?

EDIT and Further Update: Using cell replace in Menuedit did not get the VOBIDs out of sequence and enabled PgcEdit to function properly!!


Regards

[r0lZ]

I know PgcEdit is able to parse a VOB with IDs not in ascending order. I really don't know much more, since ButtonDump.exe uses libdvdread, this can be an issue of the library as well.

I wonder if having a gap in the VOB numbers (the missing VOB 15) is legal. This may be the cause of the problem in PgcEdit. Could you verify if the menus PgcEdit cannot display are located in VOB IDs above 15?

[blutach]

See above.

While it can't display VOBIDs 16, 17 and 18 it also doesn't display 5-14.

Clearly, VobBlanker has gotten these out of order and omitted the unused VOBID, while using the Replace function of menuedit has kept the menu's structure intact.

Hope this helps.

Regards

[blutach]

Just done an IfoEdit strip (not mock) of the original menu. The unused VOBID 15 was deleted and renumbering takes place from 15 on. That is, VOBID 16 becomes 15 etc. And, naturally enough, there is no VOBID 18 anymore.

No problems in any PgcEdit functions.

This has clearly been introduced by VobBlanker making a somewhat non-compliant menu.

But, the DVD menu works! Strange, n'est pas?

The question is now, can PgcEdit be made to read the menu buttons in their out of order and VOBID missing form?

Regards

[r0lZ]

Well. I'll try... tomorrow. ;)
Thanks for your investigations!

[2COOL]

Originally posted by r0lZ
I don't know if the best solution will be a slider or 2 buttons to jump from frame to frame. A slider is a lot more quicker since you just click, hold, and slide as opposed to click, click, click.

BTW, what changes have been done to PgcEditPreview.exe? Excuse for not reading throughly but I didn't see any difference besides autoplay and info window displaying when clicking on menu button toolbar.

[jeanl]

Originally posted by 2COOL

BTW, what changes have been done to PgcEditPreview.exe? Excuse for not reading throughly but I didn't see any difference besides autoplay and info window displaying when clicking on menu button toolbar.
We've added buttons at the bottom, one of which allows you to stop the preview and stop the trace as well (which was close to impossible in trace mode with the previous versions). Nothing really major other than that. Is there anything you're missing terribly in the previewer?
Jeanl

[2COOL]

Originally posted by jeanl
Is there anything you're missing terribly in the previewer?yes...sounds! U :p

[jeanl]

Originally posted by 2COOL
yes...sounds! U :p
Man, that's funny!
Well, it's not impossible because DVD2AVI already has all the AC3 decoding code in it, but it certainly will be a significant effort. Why do you think it would be that useful? I don't know many previews with sound but I'm not familiar with a lot of the commercial products... Does shrink's have sound? I think Vobedit preview does...
Jeanl

[2COOL]

Originally posted by jeanl
We've added buttons at the bottom, one of which allows you to stop the preview and stop the trace as well (which was close to impossible in trace mode with the previous versions). I only see buttons at the top. I'm using 0.4.4 beta 8

[blutach]

Originally posted by 2COOL
yes...sounds! U :p darn greedy!

[jeanl]

Originally posted by 2COOL
I only see buttons at the top. I'm using 0.4.4 beta 8
mmm that's strange? I just downloaded it and the preview has the two buttons at the bottom (only 1 if you're not in Trace mode).
Jeanl

[2COOL]

Originally posted by jeanl
mmm that's strange? I just downloaded it and the preview has the two buttons at the bottom (only 1 if you're not in Trace mode).
Jeanl OK...I see them now. It's only in trace mode. None if not though.

[jeanl]

Originally posted by 2COOL
OK...I see them now. It's only in trace mode. None if not though.
yes, if you're not in trace mode you just need the stop button. If you don't see it at the bottom in preview mode, then something's awry. If you launch preview "standalone" (outside of pgcedit) then there's no button.
Jeanl

[2COOL]

Sigh...I tried again and now I see them as you call it. I definitely need some sleep... à

[blutach]

@rolz

Looks fine now - even the hidden buttons show as hidden :) :) :)

Many many thanks

Regards

[r0lZ]

beta 9 (http://www.videohelp.com/~r0lZ/pgcedit/beta/PgcEdit_winexe_0.4.4beta9.zip) available.
Fixes the bug with unordered and/or missing VOB IDs left after a VobBlanker processing, and reported by blutach.
However, I still need to check if a similar bug could be caused by missing or unordered Cell IDs...

[jsoto]

Hi all,
Seems VobBlanker VID/CID reordering has caused some troubles...

The problem is how VobBlanker works, let say, it's internal logic. I have to change completely the main code if I want to keep the Cell order in the VOB, so this is something I do not like...

When processing, VobBlanker loops on PGCs, and outputs the cells in the order they are in the PGC. If a cell is already processed, it is ignored. So the final VOB can have VOB gaps and/or CellID gaps, but what is true is that (at least in the first PGC) the next cell is physically closed to the current one, so the laser will find it immediately.

In any case, you can use VIDChanger to renumber the cells, avoiding any gap between them. I know it is a lot of time (VOB is rewritten again) but, from now, I do not have other idea...

jsoto

[r0lZ]

@jsoto

Thanks for your answer. As you can see in my previous post, PgcEdit is now able to load unordered VOBs created by VobBlanker. However, I wonder if it is legal to have unordered VOB/Cell IDs, or gaps between them.

BTW, why do you need to rewrite the VOBs with VidChanger? It should be easy to change the IDs in place, on the original VOBs, no?

[2COOL]

Originally posted by r0lZ
BTW, why do you need to rewrite the VOBs with VidChanger? It should be easy to change the IDs in place, on the original VOBs, no? r0lZ

jsoto mentioned in the past that he didn't want to integrate VidChanger into VobBlanker even though it makes sense to add it in.

[r0lZ]

That's not what I mean. I wondered why, when using VidChanger, the VOBs must be copied when processed. IMHO, it's possible to patch them in place.

[jeanl]

Originally posted by r0lZ
That's not what I mean. I wondered why, when using VidChanger, the VOBs must be copied when processed. IMHO, it's possible to patch them in place.
in C:
fopen(filename,"bw+") will let you do that...
OOPS, EDIT: make that fopen(filename,"r+b")...
Jeanl

[jsoto]

In fact, VIDChanger does it in single cell mode, but it is unsafe
The main problem is how to recover in the case of a crash in the middle of the process. Well, you can rely on the IFO and do not take into account VID/CID in the VOB...

jsoto

[2COOL]

Current version cannot add a new dummy PGC. Tried it on 3 DVDs. :(

http://img99.exs.cx/img99/9783/image0036ka.gif

Update 1: Also for New "Play All" Title macro. Another discrepancy is that in my initial dialog, it wants to create a new Title 7, even though my DVD has only 4 Titles. It should've been new Title 5.

http://img18.exs.cx/img18/7384/image0045pw.gif

Update 2: I was using 0.4.4 beta 8 at the time and beta 9, not posted on your website yet, now works with adding a new "Play All" Title. The Add New Dummy PGC error still exists though. :(

[2COOL]

OK, so I have created a new "Play All" PGC with sharing IDs from my source PGC. Can you come up with an implementation to alter the new PGC's program map? Say I want to remove certain cells. PgcEdit uses all the unique VOB and Cell Ids but I really don't need "ALL" of them, just selected ones.

[r0lZ]

@2COOL

OK. The first bug you submitted, with New Dummy PGC in title domain, is fixed.

I don't understand the problem with the title number being too high when creating a new 'Play All' title. The actual number of titles is read directly from the VMG_TT_SRPT table, when the macro is executed.
Are you sure the table of titles of your original DVD is correct?
You said that the problem is not present in beta9. Seems strange, since nothing has changed in this macro between beta8 and 9.

Adding and removing cells in the cell table is on my TODO list for a while, but it's not easy to do. And, as you know, I want now to work on the menu buttons editor, and on BOV support. So, sorry, but you will have to wait some time...

[jsoto]

I want now to work on the menu buttons editor, and on BOV support Yuujuuu! (Spanish, translating to English: Woohooo!).
jsoto

[r0lZ]

PgcEdit 0.4.4 released.

Additions:
PgcEditPreview version 1.3 (See bottom of this text for Preview history.)
Added Preview full Domain VOB(s) utility. (Windows only)
Menu buttons viewer: arrows to select the image to show in the background.
Trace: Added a checkbutton to enable or disable the automatic preview.
Trace: Added highlights of the played PGCs (and a menu to clear them in Trace/State, and a popup menu when clicking on a blank line in the PGC Selector).
Info/Calls Cross References highlights the unreferenced PGCs in pink.
Preview: The Info window of DVD2AVI strikes again. (Modified by Jeanl, now includes the number of buttons.)
Enhancements:
Clicking or right-clicking on the current PGC line in the PGC selector do not change the current selected command in the main listbox anymore.
Handy to use the PGC Selector popup menu, and continue the trace.
Kill Playback and Blank Out functions now reset the PGC Still Time to 0.
Commands Editor: CallSS command has now the Resume Cell 1 by default.
Trace watch Input: Reset button replaced by the usage count of the current GPRM or SPRM.
Trace: it is now possible to break the Run mode from within the Preview window. Thanks to Jeanl.
Added a Preview menu, and moved the preview actions and options menu items there.
dvd2bmp.exe is now integrated in PgcEditPreview.exe, and is not included in the Windows distribution anymore.
Menu buttons viewer: Middle-clicking or Control-Left-clicking on a menu button when not in Trace mode will now jump to the target of the button.
Bug fixes: Bug fixed in PTT_SRPTI table when the chapters are not in ascending order.
Trace: Bugs with Title without TTN assignments fixed.
Trace: RSM was jumping to the first cell instead of the last visited cell.
Fixed bugs when parsing the VOBs to find menu buttons when the VOB IDs were not sorted in ascending order, or when some VOB IDs were missing.
Bug when creating a new dummy PGC in title domain fixed.
Preview 1.2 and 1.3: optimisation and bug fixes. (by Jeanl)
Fixed problem with focus not returning to the main window after a Preview.
Trace watch Input: Language code and Button number are displayed only when the current GPRM or SPRM value is a legal language code or button number.
Some more small Tcl/Tk library bug fixes.

[CoNS]

Originally posted by r0lZ
beta 9 (http://www.videohelp.com/~r0lZ/pgcedit/beta/PgcEdit_winexe_0.4.4beta9.zip) available.
Fixes the bug with unordered and/or missing VOB IDs left after a VobBlanker processing, and reported by blutach.
However, I still need to check if a similar bug could be caused by missing or unordered Cell IDs... By "fixes the bug", do you mean repair the files or just being able to load them in PgcEdit without an error?

[r0lZ]

No. PgcEdit doesn't repair anything. I mean PgcEdit is able to load and process the menubutton informations extracted from such VOBs.

BTW, the same problem with unordered Cell IDs or gaps in Cell IDs is also fixed in v0.4.4 final.

I'm still wondering if such VOBs are DVD compliant... I have never found any original VOBs with this organisation. However, all players are apparently able to play DVDs with VOBs produced by VobBlanker.

[2COOL]

http://img93.exs.cx/img93/2350/image0016iw.gif

"two or more" to be useful? It can be useful with having one PGC to start with and not just because to create a backup.

[jeanl]

r0lZ,
I'm having a problem with "Bridget Jones" (zone 1). Specifically, on VTSM2, LU1, 1, (Bonus material) I'm seeing two problems:

1) In trace mode, playback stops at the first cell of the PGC, which is actually a small intro to the real menu and attempts to display the menu buttons. Even though the cell is supposed to show 7 buttons, only one is drawn in the button menu display (all 7 buttons are actually superimposed at the top left corner, as a tiny square, clearly not for the user to click!). You'll notice that playback isn't supposed to stop at this cell.

2) A somewhat separate problem is that I'm unable to see the last background image at LBA 1799 using the > button in the menu display. I can see the next-to-last frame but not the last one. This seems to be a bug in pgcedit/preview which prevents pgcedit from displaying the last video frame in that cell. I can see it fine if I preview the cell outside of trace mode so I'm pretty sure it belongs to this cell (it shows the right V/C ID).

In my humble opinion, the trace should not stop at cell 1, since playback does not normally stop here (there's no still time, and there's no cell command so we go straight to cell 2). This suggests that your choice for where/when to show the menu layout might not be ideal.
How about displaying a menu when you encounter a cell that has buttons and where playback stops or loops either because of a loop, or because of a still time. This might not be as easy to implement as your current selection (first cell that has buttons I think), but it would solve the problem for this menu. It would skip through cell 1, go to cell 2, then notice the cell-command that loops back to the top PG.

I'm sending you a pruned version of the DVD so you can look at it. Here's the PGC info as given by PgcEdit.
Jeanl



VTSM 2 , LU 1 (en) , 1 (0:27) 14b. RootM - Chapters: n/a, Programs: 2, Cells: 2

********** pre commands:
[71 00 00 00 00 02 00 00] 1 Set gprm(0) =(mov) 2
[71 00 00 01 00 00 00 00] 2 Set gprm(1) =(mov) 0
[71 00 00 02 00 00 00 00] 3 Set gprm(2) =(mov) 0
[71 00 00 03 00 01 00 00] 4 Set gprm(3) =(mov) 1
[71 00 00 04 00 03 00 00] 5 Set gprm(4) =(mov) 3
[71 00 00 05 00 3B 00 00] 6 Set gprm(5) =(mov) 59
[71 00 00 06 00 02 00 00] 7 Set gprm(6) =(mov) 2
[71 00 00 07 00 01 00 00] 8 Set gprm(7) =(mov) 1
[71 00 00 0B 00 00 00 00] 9 Set gprm(11) =(mov) 0
[71 00 00 0C 00 00 00 00] 10 Set gprm(12) =(mov) 0
[71 00 00 0D 00 00 00 00] 11 Set gprm(13) =(mov) 0
[71 00 00 06 00 03 00 00] 12 Set gprm(6) =(mov) 3
[71 00 00 04 00 1F 00 00] 13 Set gprm(4) =(mov) 31
[30 26 00 04 00 C0 07 04] 14 if ( gprm(7) == gprm(4) ) then { (JumpSS) Jump to VMGM PGC 4 }
[20 A4 00 07 00 15 00 06] 15 if ( gprm(7) == 21 ) then { LinkPGCN PGC 6 }
[61 00 00 06 00 07 00 00] 16 Set gprm(6) =(mov) gprm(7)
[71 00 00 07 00 14 00 00] 17 Set gprm(7) =(mov) 20
[71 00 00 00 00 00 00 00] 18 Set gprm(0) =(mov) 0
[71 00 00 03 00 00 00 00] 19 Set gprm(3) =(mov) 0
[61 00 00 04 00 01 00 00] 20 Set gprm(4) =(mov) gprm(1)
[71 F0 04 04 00 01 00 01] 21 if ( gprm(4) < 1 ) then { Set gprm(4) =(mov) 1 }
[75 00 00 04 04 00 00 00] 22 Set gprm(4) *=(mul) 1024
[46 00 00 00 00 04 00 00] 23 (SetHL_BTN) Set Highlighted Button =(mov) gprm(4)
[20 B6 00 06 00 01 00 02] 24 if ( gprm(6) != 1 ) then { LinkPGN Program 2 }
********** post commands:
[61 00 00 05 00 04 00 00] 1 Set gprm(5) =(mov) gprm(4)
[20 A4 00 05 00 01 00 04] 2 if ( gprm(5) == 1 ) then { LinkPGCN PGC 4 }
[20 A4 00 05 00 05 00 05] 3 if ( gprm(5) == 5 ) then { LinkPGCN PGC 5 }
[20 A4 00 05 00 06 00 06] 4 if ( gprm(5) == 6 ) then { LinkPGCN PGC 6 }
[61 00 00 01 00 05 00 00] 5 Set gprm(1) =(mov) gprm(5)
[71 00 00 04 00 03 00 00] 6 Set gprm(4) =(mov) 3
[30 75 00 01 00 01 05 04] 7 if ( gprm(5) < gprm(4) ) then { (JumpVTS_PTT) Jump to TTN 1, Chapter 1 }
[71 00 00 06 00 04 00 00] 8 Set gprm(6) =(mov) 4
[30 26 00 04 00 C0 05 04] 9 if ( gprm(5) == gprm(4) ) then { (JumpSS) Jump to VMGM PGC 4 }
[71 00 00 04 00 04 00 00] 10 Set gprm(4) =(mov) 4
[30 25 00 01 00 02 05 04] 11 if ( gprm(5) == gprm(4) ) then { (JumpVTS_PTT) Jump to TTN 2, Chapter 1 }
[71 00 00 07 00 08 00 00] 12 Set gprm(7) =(mov) 8
[20 04 00 00 00 00 00 03] 13 LinkPGCN PGC 3
********** cell commands:
[20 01 00 00 00 00 00 05] 1 LinkTopPG

********** menu buttons commands:
VOB ID 1, Cell ID 1 (First NAV pack LBA=0)
2 Groups, Start button=0, Select button=0, Action button=0
button 1: [20 01 00 00 00 00 00 06] LinkNextPG
button 2: [20 01 00 00 00 00 00 06] LinkNextPG
button 3: [20 01 00 00 00 00 00 06] LinkNextPG
button 4: [20 01 00 00 00 00 00 06] LinkNextPG
button 5: [20 01 00 00 00 00 00 06] LinkNextPG
button 6: [20 01 00 00 00 00 00 06] LinkNextPG
button 7: [20 01 00 00 00 00 00 06] LinkNextPG
VOB ID 1, Cell ID 2 (First NAV pack LBA=1912)
2 Groups, Start button=0, Select button=0, Action button=0
button 1: [71 01 00 04 00 01 00 0D] Set gprm(4) =(mov) 1 ; LinkTailPGC
button 2: [71 01 00 04 00 02 00 0D] Set gprm(4) =(mov) 2 ; LinkTailPGC
button 3: [71 01 00 04 00 03 00 0D] Set gprm(4) =(mov) 3 ; LinkTailPGC
button 4: [71 01 00 04 00 04 00 0D] Set gprm(4) =(mov) 4 ; LinkTailPGC
button 5: [71 01 00 04 00 05 00 0D] Set gprm(4) =(mov) 5 ; LinkTailPGC
button 6: [71 01 00 04 00 06 00 0D] Set gprm(4) =(mov) 6 ; LinkTailPGC
button 7: [71 01 00 04 00 07 00 0D] Set gprm(4) =(mov) 7 ; LinkTailPGC


Playback time: 00:00:27.09 (at 30 fps)
PG Playback mode: sequential
PUOs: 33354720 (0x01FCF3E0)
- Time or PTT search (0x00000020)
- TopPG or PrevPG search (0x00000040)
- NextPG search (0x00000080)
- Forward scan (0x00000100)
- Backward scan (0x00000200)
- Menu call - Subpicture (0x00001000)
- Menu call - Audio (0x00002000)
- Menu call - Angle (0x00004000)
- Menu call - PTT (0x00008000)
- Still off (0x00040000)
- Pause on (0x00080000)
- Audio stream change (0x00100000)
- Subpicture stream change (0x00200000)
- Angle change (0x00400000)
- Karaoke audio mix change (0x00800000)
- Video presentation mode change (0x01000000)
NextPGCN: 0
PrevPGCN: 0
GoUpPGCN: 0
PGC Still Time: 0
Audio stream 1 status: 0x00008000 (stream=0)
Subpic stream 1 status: 0x80000001 (streams for 4:3=0, wide=0, letterbox=0, pan&scan=1)

But- Prog. Cell Type Layer Res- Still Cell Playback End Entry First Last Last VOB Cell
tons Flags Break tric- Time Cmd. Time Time VOBU ILVU VOBU VOBU ID ID
ted. sector End Start End

7 1 1 2 yes no 0 0 00:00:05.00 00:00:05.00 0 0 1609 1911 1 1
7 2 2 8 no no 0 1 00:00:22.09 00:00:27.09 1912 0 8828 9067 1 2