View Full Version : PgcEdit v9.0 released (24 Dec 2008) and v9.1 (3 Jan 2009)
vwpassion
5th January 2009, 18:29
Noticed a weird behaviour when using the "Jump to PGC upon DVD insert" function.
Once I trace to my target pgc (which is the menu in this case) the menu viewer pops up, and then I select the pre commands of the pgc, and then call the "Jump to PGC upon DVD insert" function. Pgcedit is then modifying the navigation properly, just the way its supposed to. However, when its done and resetting the trace mode, the "Modifying Navigation... Please wait..." box doesnt close automatically. It just stays there, until I close it down manually. I was able to reproduce this behaviour with other dvds as well.
blutach
5th January 2009, 20:36
You need to put a stop on the PGC with the menu containing the video (Ctrl-Shift-T). The trace will stop before the precommands of that PGC are even executed. Then call the Jump2PGC function.
Did you not get this error?
9220
After that it will offer to put a breakpoint on. Say yes and restart the trace (press the "load/eject" button). When it stops then call the function.
What is happening now is the function is actually incorrect because it has executed already the precommands in the menu PGC.
Regards
vwpassion
5th January 2009, 22:23
If, before you call the function, you click on the precommands of your target pgc (so that it is selected), it doesnt prompt you to set a breakpoint and retrace to the target. Maybe this should be prevented. But you're spot on, I've just compared the gprms that are set once the target is reached, against the gprms that are set on the original dvd once it reaches the menu, and there were differences. Those could probably mess up many other things in a worst case scenario. Thanks for the insight blutach!
blutach
6th January 2009, 11:57
There is a guide on the PgcEdit site (written by a total idiot, but you should read it anyway) :)
http://www.digital-digest.com/~blutach/Jump2PGC/Jump2PGC_guide.html
Regards
r0lZ
6th January 2009, 12:46
I agree that PgcEdit *should* verify if the user has traced to the target point and has not changed the position of the cursor manually, but it's almost impossible. I can't record every manual action, just in case Jump2PGC will be called. Furthermore, it's again the same problem than with the possibility to edit the DVD in trace mode. That should normally be impossible, but I think that in some case, that can be very useful, so I've not disabled that possibility. Normally, when you are tracing a DVD, you should use only the DVD remote (the "player" part of the trace panel) and nothing else. Each time you edit the DVD or you change the position of the navigation cursor, you should restart the trace from the beginning, unless you want to test the behaviour of the navigation when you change something, and you know what you are doing.
In the case of the Jump2PGC function, PgcEdit verifies some basic things, such as the position of the navigation pointer (that should be on the first pre-command) and if the current PGC is the last PGC reached by the trace. I've added now a check to verify if the menu viewer is closed, but I cannot verify if you have stopped the trace somewhere in the middle of the PGC and then clicked on the first pre-command. Don't do that! As you have noticed, doing so can be harmful, as the GPRMs may have changed.
The strange behaviour of the "Please wait..." window is probably due to the fact that you have applied the Jump2PGC macro when the trace was running. Remember that when the trace opens the menu viewer, it is in the middle of a step, playing a cell and waiting for the user action. The macro disrupts the trace, and it cannot continue normally. You had to close the window yourself because the macro has never reached its end. I'm not going to try to fix that, as it's caused by a user error, and it is even a good thing that something strange happened. (Otherwise, you wouldn't have posted your remark here, right?)
selyb
7th January 2009, 09:15
I too always run with trace mode on and asked r0lZ about this some time back and he said it was necessary. Not sure about the technical reasons but it's only 1 click to get it back on.
Regards
Using the v8.6 source, I believe I successfully converted Trace Mode to a remembered toggle option (just like trace mode 'watch' options)
PgcEdit_main.tcl
Removed#Open Trace mode if requested by user
if {$::config(open_trace_mode) && [info exists ::dvddir]} {
after 10 {::tr::dvd_trace}
}
from end of file
lib\main.tcl
Added # Open Trace mode if requested by user
if {$::config(open_trace_mode)} {
after 10 {::tr::dvd_trace}
}
to the end of Read_New_DVD and ReRead_DVD functions just before the return statement
lib\utils.tcl and lib\srptinfo.tcl
Added # Open Trace mode if requested by user
if {$::config(open_trace_mode)} {
after 10 {::tr::dvd_trace}
}
to the end of every function that called ::tr::kill_trace
just before the return statement
lib\trace.tcl
modified if {! [info exists ::dvddir]} {
set ::tr::tracemode 0
bell
return
}
to
if {! [info exists ::dvddir]} {
set ::tr::tracemode 0
set ::config(open_trace_mode) false
bell
return
}
and set ::tr::tracemode 1
# disable unwanted parts of the interface
to
set ::tr::tracemode 1
set ::config(open_trace_mode) true
# disable unwanted parts of the interface
now, pgcedit always goes back to whichever state I was in after I use any of the functions that close it or even after I close and re-open PgcEdit
of course, this isn't needed anymore
menus.tcl $menuname add checkbutton -label "Start in Trace mode (when a DVD is opened at startup)?" \
-variable ::config(open_trace_mode) -onvalue true -offvalue false
r0lZ
7th January 2009, 13:17
Good finding, selyb, but the code has changed in v9.
In theory, you are right. Obviously, is sufficient to reopen the trace at the end of each function that killed it. But the trace mode is a bit special. In fact, it is constantly watching the buttons in the trace panel, to be able to continue the trace when the user requests so. You can consider it as an independent program running inside PgcEdit, although it's not another process. That's the source of the problems and bugs, and it's why I don't like to start it automatically. It's also why I had to introduce a delay when killing the trace, to be sure that the last step of the trace has finished before closing the trace GUI.
Also, the code you propose to add in lib\main.tcl is erroneous. It should check that a DVD has been loaded before opening the trace, as using trace mode without something to trace will certainly fail. Therefore, your idea to remember the state of the trace to restart it automatically when PgcEdit is opened cannot work. If no DVD is loaded, I can't restart the trace, and the trace state will be turned off.
I agree that it should be possible to use a similar method, if each time the trace is killed, a new global variable is initialized, and that variable is tested at the end of the function that need to kill the trace. But there is another difficulty. Several functions that need to kill the trace can be called by a more general function. For example, Remove Useless Stuff calls Delete Uncalled PGCs, that calls repetitively Remap PGCs and Remap Titlesets. If after each iteration, I have to re-open the trace and kill it again some seconds later, this will produce an unpleasant flickering effect, slow down the function considerably (remember that I need to wait when killing the trace), and, for technical reasons too long to explain, the kill and open procedures launched too early can completely confuse PgcEdit. You could, for example, have two instance of the trace running at the same time! I've experienced that when debugging, and believe me, it's not recommended!
However, since I've added in v9 the "Please wait" yellow window, and that window is opened at the start of the function and closed when it finishes, even if another function is called that should also open and close that window but don't do it if it is already opened, I could perhaps modify the code to restore the trace state when the window is closed. I will see if that's possible easily, but don't expect it!
selyb
7th January 2009, 17:50
Therefore, your idea to remember the state of the trace to restart it automatically when PgcEdit is opened cannot work. If no DVD is loaded, I can't restart the trace, and the trace state will be turned off.
Because of the placement, Trace mode was only started after a DVD was opened. I did not try to open some erroneous IFOs so if a DVD failed to load then it would probably break then. I purposely removed the dvd open check, but now I realize the need for it there.
I really like that yellow box addition.
I will see if that's possible easily, but don't expect it!
Thank you. If/when you release the source, if you haven't done it already then I will make it work and post what I did.
blutach
8th January 2009, 00:55
It's unlikely the sources will ever be released as this will almost ensure that donations stop.
Regards
r0lZ
8th January 2009, 01:09
Well, I may release them later, but certainly with a big lapse of time between the releases of the exe and the sources. For example, I might release the sources of v9.0 when v9.5 or v10.0 will be available, in 6 months or one year. And anyway, the code that builds the registration codes will never be released.
selyb
8th January 2009, 02:51
I know I've been annoying lately, but I have another low priority request.
Store command accelerators in a cfg file.
I don't expect you to implement it soon if at all since this would be a significant amount of work to please a small number of users, but I wanted to put it on you're mind anyway.
blutach
8th January 2009, 03:34
If by command accelerators, you mean personal hotkeys, they are stored in hotkeys.tcl in your plugins directory. If you associate tcl with wordpad or the like, they are easily accessed.
Regards
selyb
8th January 2009, 05:48
If by command accelerators, you mean personal hotkeys, they are stored in hotkeys.tcl in your plugins directory. If you associate tcl with wordpad or the like, they are easily accessed.
Regards
man, I tried and I can't find any reference to that file in the code or on google.
I don't have it and it isn't created automagically.
Another request: When I use the command 'Go to calling command', if the target is uncalled, could you go ahead and label it that way?
e.g. When I hit Ctrl+G on VTSM3 RootMenu I get the message 'Normally callable with remote... But since no titles...' then we know the VTS is uncalled so that means everything in the VTS could be labelled uncalled
BTW, 'Go to calling command' should probably be called 'Find calling commands'
Added:
I http://home.comcast.net/~selyb/beating_heart.gif the conversions when copying and pasting between menus and titles!
http://home.comcast.net/~selyb/smiley_thumbs_up.gif
I'm not kidding when I tell you I get chills when I copy 'CallSS' and it pastes as 'JumpSS' !!
I also just noticed that when I hit Ctrl+K that handling of the commands is different.
Until now, I would remove the useless NOP that was created and delete the Post commands that were copied to the Pre commands. Now all this is done already. :)
blutach
8th January 2009, 08:47
No, it's not created automatically - you need to create it and set your own hotkeys with a .bind statement. Note your hotkeys are case sensitive. I'm not sure what happens when you cnflict with a real key assignment.
Here's just one hotkey I have (Ctrl_Shift-F):
bind . <Control-F> ::utils::find_all_uncalled
If you pop that in a file called hotkeys.tcl in plugins, then whenever you hit that key combo, it will execute the Info --> Find All Uncalled PGCs code. Of course, you ned to adapt this to your own requirements and now the sources are not published, this will be harder to do (especially with the new functions).
Regards
r0lZ
8th January 2009, 13:14
All files with a .tcl extension in the plugins directory are executed at PgcEdit startup, in alphabetical order, after the DVD has been loaded (if it was specified in the command line or opened with the option to "Launch Open DVD dialog at startup"). That means that you can define your own hotkeys, as blu explained, but also call any function you want to apply on all DVDs anyway. The plugins are tcl functions that add themselves to the plugin menu.
I had already the intention to add a GUI to define your own hotkeys, but it's not simple, especially because I have to modify the accelerator field of the menu items, and that the correspondence between the menu title and the function name is not obvious. Also, the accelerators used by the Edit menu are a bit special, as they are active only when the commands pane is active. I'll think about it...
Another request: When I use the command 'Go to calling command', if the target is uncalled, could you go ahead and label it that way?That should be possible, and it's a good idea.
However, I'm not sure I may label as uncalled an entry menu that is callable with the remote. Unless you use the global "Find Uncalled PGCs", I have no way to know that the VTS is globally uncalled, and therefore the menu can theoretically be called with the remote.
Go To Calling Command is named that way because it has the Control+G hotkey ;) and the GUI can be used to jump to any calling command. Not sure I will change that.
Thanks for your appreciation on the new Paste Commands and Kill PGC behaviours.
AlienX69
8th January 2009, 15:42
There is a guide on the PgcEdit site (written by a total idiot, but you should read it anyway) :)
http://www.digital-digest.com/~blutach/Jump2PGC/Jump2PGC_guide.html
Regards
LOL !!! ..... :devil:
Great guide !!!
AX
AlienX69
8th January 2009, 15:49
r0lZ,
Just an FYI ~~~
I received an email that the PgcEdit Home page had a change. After investigating I saw that 9.1 was released.
So I opened 9.0, went to "Check for new version" ...... it said I'm current and had the latest version.
I did download 9.1 and installed it manually.
Regards,
AX
r0lZ
8th January 2009, 16:28
Oops, I forgot to update the version number on the site. Fixed. Thanks!
selyb
9th January 2009, 08:56
I had already the intention to add a GUI to define your own hotkeys, but it's not simple, especially because I have to modify the accelerator field of the menu items, and that the correspondence between the menu title and the function name is not obvious. Also, the accelerators used by the Edit menu are a bit special, as they are active only when the commands pane is active. I'll think about it...
I have done something similar so I know what is involved with doing this and I really don't think you should make a gui for it. I believe that would be too much work to please very few people. I simply was hoping you could modify the code to read the hotkeys (maybe even the whole menu) from a config file. If the end user messes it up then he/she could delete it and PgcEdit would recreate the default. I believe that would be much easier than creating a gui and would be just fine for power users (like myself).
On the other hand, I suppose I could write a plugin to destroy and remake the current menu with different hotkeys and accomplish the same thing.
That should be possible, and it's a good idea.
However, I'm not sure I may label as uncalled an entry menu that is callable with the remote. Unless you use the global "Find Uncalled PGCs", I have no way to know that the VTS is globally uncalled, and therefore the menu can theoretically be called with the remote.
Understood. That makes perfect sense.
M_Knox
10th January 2009, 23:20
I've just came across a small bug in PgcEdit 9.1. It is related to "Go to calling command" function. Best way to describe it is to give steps to reproduce:
1. Select any PGC
2. Issue "Go to calling command" - a dialog pops up with a few references
3. Without closing the dialog, select another PGC
4. Issue "Go to calling command" again - do not press "New target" button on the dialog, just press Ctrl+G. The references in the dialog are updated
5. Press the "Refresh" button on the dialog - it will display references to the PGC selected in step 1. Furthermore, closing the dialog will result in an error bad window path name ".xrefs.f.c.f1"
r0lZ
10th January 2009, 23:31
Hum, yes, the command to refresh the PGC is built when the window is opened, and probably not modified if the window is reused without being closed first. I'll have a look. Thanks.
[EDIT] Bug fixed... by M_Knox!
Mike89
12th January 2009, 06:17
Gladly donated for this stellar program. :)
r0lZ
12th January 2009, 10:33
Thanks!
mikenadia
13th January 2009, 16:58
I made a backup of PGCEdit,DVD shrink and VObblanker folders and it seems that the file containing the "Tools configuration" information (Vobblanker called from within PGCedit with F1 Key...) is not in those folders.
What should I do to have everything ( besides registration or else) configured with a " copy" restore?
Thanks in advance.
r0lZ
13th January 2009, 17:38
The config files of PgcEdit (and of many programs, including VobBlanker, MenuShrink...) is in your application data folder. Normally, that folder is located here: "C:\Documents and Settings\<your_login>\Application Data\". The PgcEdit config files is in the PgcEdit sub-folder.
Note that "Application Data" is normally an hidden folder, so you have to modify your folder options in control panel to be able to see it in Explorer.
M_Knox
13th January 2009, 19:44
Normally, that folder is located here: "C:\Documents and Settings\<your_login>\Application Data\". The PgcEdit config files is in the PgcEdit sub-folder.
Note that "Application Data" is normally an hidden folder, so you have to modify your folder options in control panel to be able to see it in Explorer.
Just use %APPDATA% in the Run dialog (Start -> Run...), does not matter if the folder is hidden :)
r0lZ
13th January 2009, 19:56
That's right, and it's a good trick!
david42
15th January 2009, 00:00
PgcEdit V9.1 - Checking Preview Window's 'Blank this Cell' box halts Trace
When running in trace mode and the preview window shows something I want to delete (ie. Movie Rating Screen) the bottom of the preview window has a check box for 'Blank this Cell'.
After I check that box then click on the 'Close Preview' button, then go through a couple of windows to confirm how to kill the cell and backup the vob, the trace ends up stopped (Run button available).
This is not how it worked in v8.6 and I would prefer if the trace continues to run. Seems like an undesired 'feature' showed up in v.9X that gets the 'Close Preview' and 'Close & Break Trace' buttons confused.
Please advise.
r0lZ
15th January 2009, 14:37
It's intentional. Since now all cells of a PGC are played one after each other without closing the preview window, it is possible to click the Blank This Cell button when the next cell has started, and that's dangerous. I think therefore that it is safer to stop the trace so that you can verify if you have blanker the right cell before continuing the trace.
Anyway, you have just one additional button to click to continue.
mikenadia
15th January 2009, 17:18
Got this code after "Killing a Title PGC playback" (straight from the rip).
********** pre commands:
[61 00 00 00 00 06 00 00] 1 Set gprm(0) =(mov) gprm(6)
[71 00 00 06 00 00 00 00] 2 Set gprm(6) =(mov) 0
[71 00 00 01 00 00 00 00] 3 Set gprm(1) =(mov) 0
[71 00 00 02 00 00 00 00] 4 Set gprm(2) =(mov) 0
[00 A1 00 00 00 01 00 06] 5 if ( gprm(0) == 1 ) then { Goto line 6 }
[00 00 00 00 00 00 00 00] 6 NOP
[30 08 00 0B 01 C0 00 00] 7 (CallSS) Call the VMGM PGC 11, resume cell 1
[00 00 00 00 00 00 00 00] 8 NOP
[20 04 00 00 00 00 00 02] 9 LinkPGCN PGC 2
********** post commands:
[30 08 00 0B 01 C0 00 00] 1 (CallSS) Call the VMGM PGC 11, resume cell 1
********** cell commands:
The LinkPGCN PGC 2 (#9) is highlighted and it is a "Jump to Nowhere".It was not a "pre-post or cell" command before "Killing PGC Playback" and there was only one "post command" before (the same as shown in the code section).
Thanks in advance.
M_Knox
15th January 2009, 20:53
Perhaps there was a "Next PGCN link" in the PGC you killed the playback of.
mikenadia
15th January 2009, 21:34
Before doing "Killing PGC Playback"
[61 00 00 00 00 06 00 00] 1 Set gprm(0) =(mov) gprm(6)
[71 00 00 06 00 00 00 00] 2 Set gprm(6) =(mov) 0
[71 00 00 01 00 00 00 00] 3 Set gprm(1) =(mov) 0
[71 00 00 02 00 00 00 00] 4 Set gprm(2) =(mov) 0
[00 A2 00 00 00 01 00 00] 5 if ( gprm(0) == 1 ) then { Break }
********** post commands:
[30 08 00 0B 01 C0 00 00] 1 (CallSS) Call the VMGM PGC 11, resume cell 1
********** cell commands:
I guess #5 is the one causing it. Should I just "Blank the cell" or could I delete # 9 from post #130.
Thanks a lot M_Knox.
Edit: Got it: They were a "Next PGCN link" . Thanks a lot again.
M_Knox
15th January 2009, 22:59
Double click the PGC before doing "Kill PGC Playback" and see if there's the link I mentioned (it's not a command, it's like an attribute of the PGC). Anyway, as there's a post command, I wouldn't bother and just delete the #9 command.
blutach
16th January 2009, 00:44
I'm sure M_Knox is on the right track but it can't possibly matter since it can't ever be executed (the CallSS gets executed before it). It's just the way PgcEdit takes care of all jumps and links in its Kill Playback routines.
I you wish, you can delete lines 5, 6, 8 and 9.
Regards
mikenadia
18th January 2009, 13:21
Thanks M_Knox and blutack for your answers on my previous questions.
I got a DVD with multiples sets of BOVs in the same cell. If I do not do what is unsafe (as per warnings), " Jump to PGC upon insert" should be ok?
What about Menushrink and VOBblanker (cutting frames in non-menu cells...)?
Thanks in advance.
r0lZ
18th January 2009, 14:21
Jump2PGC should be OK, yes, but without guarantee. However, Jump2PGC is a function that should not be affected by the presence of multiple sets of buttons, except in some very unusual cases.
As a general rule, to be sure that you can use some of the PgcEdit functions in presence of multiple sets, have a look at the new function Info -> Multiple Sets Of Buttons/BOVs. It will display all sets of buttons. If there is no new or modified command in the additional sets, you can safely ignore the warning, for ALL PgcEdit functions. However, if a new button is created in an additional set, or if the command of a button changes, and if the new command is a jump, call or link, you should take care, especially with the commands that modify the DVD structure deeply, such as most of the remapping functions. Don't worry too much. PgcEdit will warn you again if you try to use those functions.
You can cut cells with VobBlanker, but take care at MenuShrink (or at VB if you use it to convert a menu to still.) Of course, if a menu cell containing multiple sets of buttons is converted to still, only the current set will remain, and you may lose the additional command or button, and, for example, be unable to access an easter egg or hidden feature.
dashali
20th January 2009, 00:00
Very Thanks r0lZ! for new version of PgcEdit -the best software for dvd editing.
I have 1 suggestion & 1 question about PgcEdit:
suggestion:
That is Adding a option for Associating PgcEdit with DVD Movie "Right-Click" & "AutoPlay"; in this form:
Option -> Install -> Associate PgcEdit with DVD Movie "Right-Click" & "AutoPlay"?
http://forum.doom9.org/attachment.php?attachmentid=9298&stc=1&d=1232405671
Please look at another file that I attached. This is a reg file.
question:
For adding a new dummy pgc, I use "New dummy pgc" and for adding a new un-dummy pgc, I use "Clone pgc".
But in both, new pgc added in "end" of VTS.
Is there any way to add this new pgc in "before" or "after" a pgc?
r0lZ
20th January 2009, 01:17
Thanks for your kind words!
When you associate the IFOs (or BUPs) with PgcEdit, it adds an "Open DVD with PgcEdit" option to the right click menu. Additionally, it offers to make PgcEdit the default (double-click) application for that file type.
Currently, there is no way to install PgcEdit in the AutoPlay handler, but imo, since the DVDs are read-only and PgcEdit is an editor and not a ripper, that makes little sense. Anyway, there are many free applications to associate it yourself if you wish. (I use M$ TweakUI.) Be sure to associate the VIDEO_TS folder or VIDEO_TS.IFO, as associating PgcEdit with the drive letter doesn't work well.
A new PGC is always created at the end of the VTST or LU, because inserting it in the middle would require fixing the commands jumping to all subsequent PGCs. You can then move the new PGC with Domain -> Remap PGCs of Domain. That function takes care of the jumps to the moved PGCs.
dashali
22nd January 2009, 11:28
OK, you are right, PgcEdit is a wonerful editor also a wonerful viewer. sometimes, I use it for viewing.
In additon, when anyone want to edit a DVD-Movie, needs to refer to original navigation commands and parameters.
I don't use M$ TweakUI for this, I use the my reg file which I wrote and currenly attached.
Anyway, in my opinion, this option can be useful and it's function work well with any DVD-Movie in real or virtual DVD-ROM and it is independent of drive letter.
Thanks for Help.
I dont had worked with "Remap PGCs of Domain" so far.
Thanks for everything.
dialysis1
22nd January 2009, 19:43
How can someone who lives in the U.S. and does not have any online accounts like paypal donate?
r0lZ
23rd January 2009, 00:10
Well, you are not the first who ask me this question. Honestly, I don't know if it is possible to donate without an account somewhere. If someone has an idea, please let me know!
selyb
23rd January 2009, 04:24
I could be a middle man. I will donate the amount he requests. Then he could send me a check or deposit to my bank account.
r0lZ
23rd January 2009, 04:54
Nice proposition, selyb! But I would prefer a solution that works for everybody. Someone suggested me to create a wishlist at eBay or something like that, but I have no idea of how it works.
vwpassion
23rd January 2009, 14:25
Hi there,
I encountered something very odd with a PAL version of Disney's Wall-E. It is a multi angle title with 2 angles. One angle is the English angle and the other is the foreign angle (it is used to show e.g. newspaper articles etc in the foreign language instead of english).
Now right to the problem: When I run the trace I get the following error on the first cell that contains angles:
******* Start playback VTST 3 , 1 TTN 1 (1:33:24) Title 1...
******* Playing Program 1, Cell 9 (0:43.00) (Chapter 1)
-> sprm(7:Chapter number (or PGN)) = 1 (0x0001)
####### ERROR: Cannot find angle 2 in angle block! Playing cell 10 (angle 1) instead!
******* Playing Program 1, Cell 10 (0:14.24) (Chapter 1)
-> sprm(7:Chapter number (or PGN)) = 1 (0x0001)
******* Playing Program 1, Cell 12 (2:17.00) (Chapter 1)
-> sprm(7:Chapter number (or PGN)) = 1 (0x0001)
####### ERROR: Cannot find angle 2 in angle block! Playing cell 13 (angle 1) instead!
******* Playing Program 1, Cell 13 (0:12.13) (Chapter 1)
-> sprm(7:Chapter number (or PGN)) = 1 (0x0001)
Now, this goes on and on with every cell that contains angles. However, when I play the english version (angle 1; being called from a pre-selection-menu on the dvd where you can chose your language and which then directs to either english/foreign menu and therefor angle) all is well, and PGCEdit doesnt spit out any errors (it uses Angle1 on the angle blocks, with no problems whatsoever).
******* Start playback VTST 3 , 1 TTN 1 (1:33:24) Title 1...
******* Playing Program 1, Cell 9 (0:43.00) (Chapter 1)
-> sprm(7:Chapter number (or PGN)) = 1 (0x0001)
******* Playing Program 1, Cell 10 (0:14.24) (Chapter 1), Angle 1
-> sprm(7:Chapter number (or PGN)) = 1 (0x0001)
******* Playing Program 1, Cell 12 (2:17.00) (Chapter 1)
-> sprm(7:Chapter number (or PGN)) = 1 (0x0001)
******* Playing Program 1, Cell 13 (0:12.13) (Chapter 1), Angle 1
-> sprm(7:Chapter number (or PGN)) = 1 (0x0001)
Doing the same thing with PGCEdit 8.6 works fine! So i figured this might be a bug in the current version?
******* Start playback VTST 3 , 1 TTN 1 (1:33:24) Title 1...
******* Playing Program 1, Cell 9 (0:43.00) (Chapter 1)
-> sprm(7:Chapter number (or PGN)) = 1 (0x0001)
******* Playing Program 1, Cell 11 (0:14.24) (Chapter 1), Angle 2
-> sprm(7:Chapter number (or PGN)) = 1 (0x0001)
******* Playing Program 1, Cell 12 (2:17.00) (Chapter 1)
-> sprm(7:Chapter number (or PGN)) = 1 (0x0001)
******* Playing Program 1, Cell 14 (0:12.13) (Chapter 1), Angle 2
-> sprm(7:Chapter number (or PGN)) = 1 (0x0001)
Oh, just to avoid any confusion: the dvd itself plays perfectly fine in soft- and hardware players, so it has to be related to PGCEdit I believe. In case this might be of importance: the dvd has been ripped with the newest beta of DVDFAB.
r0lZ
23rd January 2009, 15:26
It is true that the angle selection in trace mode has been modified for v9, as now the preview can show a specific angle correctly. There might be a bug here, but of course, the beta testers and myself, we have verified that carefully, and never came across this problem. It might be as well caused by an error in the cell table of the movie. Could you post it here? (Select the main movie PGC, and use Info -> PGC.)
According to the error message, angle 1 is correct, but angle 2 is missing or not correctly defined. This is why the problem does not happen when angle 1 must be played. Do you have removed an angle, or modified the cells table in any way?
Another question: when angle 1 is played, do you see the movie normally, or the multi-angle parts are shown interleaved (like with v8.6)? Can you also try to preview the PGC directly, and not from the trace? PgcEdit should display a little dialog where you can select the angle you want to display. Does it work?
Unfortunately Wall-E is not yet available here, so I can't test it myself.
r0lZ
23rd January 2009, 16:01
Forget my previous post, vwpassion! There is indeed a bug in PgcEdit. I've found and fixed it.
Thanks for your bug report!
vwpassion
23rd January 2009, 16:01
It might be as well caused by an error in the cell table of the movie. Could you post it here? (Select the main movie PGC, and use Info -> PGC.)
Here is part 1 of the cell table (see following post for part 2):
BOVs Chap. Prog. Cell Type Seam- Ang VOBU Cell Cell Playback End Entry First Last Last VOB Cell
(PTT) Flags less Still Still Cmd. Time Time VOBU ILVU VOBU VOBU ID ID
Joint Time # sector End Start End
0 1 1 1 2 no - no 0 1 00:00:00.10 00:00:00.10 7 0 7 22 2 1
0 2 2 no - no 0 2 00:00:00.10 00:00:00.20 23 0 23 38 3 1
0 3 2 no - no 0 3 00:00:00.10 00:00:01.05 0 0 0 6 1 1
0 4 2 no - no 0 4 00:00:00.10 00:00:01.15 0 0 0 6 1 1
0 5 2 no - no 0 5 00:00:00.10 00:00:02.00 0 0 0 6 1 1
0 6 2 no - no 0 0 00:00:00.10 00:00:02.10 0 0 0 6 1 1
0 7 2 no - no 0 0 00:00:00.10 00:00:02.20 0 0 0 6 1 1
0 8 2 no - no 0 0 00:00:00.10 00:00:03.05 0 0 0 6 1 1
0 9 2 no - no 0 0 00:00:43.00 00:00:46.05 39 0 19052 19164 4 1
0 10 94 yes 1 no 0 0 00:00:14.24 00:01:01.04 19165 19724 30411 30627 5 1
0 11 222 yes 2 no 0 0 00:00:14.24 00:01:01.04 19725 20282 31492 31710 6 1
0 12 10 yes - no 0 0 00:02:17.00 00:03:18.04 31711 0 94247 94496 7 1
0 13 94 yes 1 no 0 0 00:00:12.13 00:03:30.17 94497 95756 104457 104714 8 1
0 14 222 yes 2 no 0 0 00:00:12.13 00:03:30.17 95757 97016 105666 105923 9 1
0 2 2 15 10 yes - no 0 0 00:00:24.17 00:03:55.09 105924 0 117228 117480 10 1
0 16 94 yes 1 no 0 0 00:00:07.09 00:04:02.18 117481 118581 122867 123089 11 1
0 17 222 yes 2 no 0 0 00:00:07.09 00:04:02.18 118582 119682 123979 124201 12 1
0 18 10 yes - no 0 0 00:01:35.22 00:05:38.15 124202 0 171437 171629 13 1
0 3 3 19 8 yes - no 0 0 00:03:20.13 00:08:59.03 171630 0 262510 262694 13 2
0 4 4 20 94 yes 1 no 0 0 00:00:05.24 00:09:05.02 262695 263999 266395 266599 14 1
0 21 222 yes 2 no 0 0 00:00:05.24 00:09:05.02 264000 265303 267691 267895 15 1
0 22 10 yes - no 0 0 00:02:31.24 00:11:37.01 267896 0 335090 335383 16 1
0 5 5 23 8 yes - no 0 0 00:01:18.10 00:12:55.11 335384 0 371204 371381 16 2
0 24 8 yes - no 0 0 00:04:20.04 00:17:15.15 371382 0 487280 487459 16 3
0 6 6 25 8 yes - no 0 0 00:01:32.24 00:18:48.14 487460 0 528698 528972 16 4
0 7 7 26 8 yes - no 0 0 00:01:32.20 00:20:21.09 528973 0 570459 570649 16 5
0 8 8 27 8 yes - no 0 0 00:00:08.19 00:20:30.03 570650 0 574556 574875 16 6
0 28 8 yes - no 0 0 00:02:21.12 00:22:51.15 574876 0 639670 639903 16 7
0 9 9 29 8 yes - no 0 0 00:00:31.17 00:23:23.07 639904 0 653181 653571 16 8
0 30 8 yes - no 0 0 00:04:45.24 00:28:09.06 653572 0 784504 784650 16 9
0 10 10 31 8 yes - no 0 0 00:00:02.00 00:28:11.06 784651 0 785481 785671 16 10
0 32 8 yes - no 0 0 00:01:59.22 00:30:11.03 785672 0 842143 842304 16 11
0 11 11 33 8 yes - no 0 0 00:01:57.16 00:32:08.19 842305 0 895304 895501 16 12
0 12 12 34 8 yes - no 0 0 00:00:40.17 00:32:49.11 895502 0 914288 914494 16 13
0 35 94 yes 1 no 0 0 00:00:09.22 00:32:59.08 914495 915748 922010 922232 17 1
0 36 222 yes 2 no 0 0 00:00:09.22 00:32:59.08 915749 917002 923292 923514 18 1
0 37 10 yes - no 0 0 00:00:57.05 00:33:56.13 923515 0 950309 950555 19 1
0 13 13 38 8 yes - no 0 0 00:01:25.08 00:35:21.21 950556 0 988603 988897 19 2
0 39 94 yes 1 no 0 0 00:00:03.19 00:35:25.15 988898 990579 990373 990579 20 1
0 40 222 yes 2 no 0 0 00:00:03.19 00:35:25.15 990580 992262 992056 992262 21 1
0 41 10 yes - no 0 0 00:00:15.23 00:35:41.13 992263 0 999139 999390 22 1
0 42 94 yes 1 no 0 0 00:00:05.15 00:35:47.03 999391 1000546 1002866 1003057 23 1
0 43 222 yes 2 no 0 0 00:00:05.15 00:35:47.03 1000547 1001703 1004220 1004411 24 1
0 44 10 yes - no 0 0 00:01:07.10 00:36:54.13 1004412 0 1034387 1034580 25 1
0 45 94 yes 1 no 0 0 00:00:04.09 00:36:58.22 1034581 1035507 1037148 1037403 26 1
0 46 222 yes 2 no 0 0 00:00:04.09 00:36:58.22 1035508 1036434 1038119 1038376 27 1
0 47 10 yes - no 0 0 00:00:18.12 00:37:17.09 1038377 0 1044956 1045152 28 1
0 14 14 48 8 yes - no 0 0 00:03:54.00 00:41:11.09 1045153 0 1155559 1155785 28 2
0 15 15 49 8 yes - no 0 0 00:00:36.14 00:41:47.23 1155786 0 1169509 1169648 28 3
0 16 16 50 8 yes - no 0 0 00:02:32.08 00:44:20.06 1169649 0 1237491 1237719 28 4
0 51 94 yes 1 no 0 0 00:00:06.17 00:44:26.23 1237720 1238758 1242447 1242704 29 1
0 52 222 yes 2 no 0 0 00:00:06.17 00:44:26.23 1238759 1239797 1243572 1243829 30 1
0 53 10 yes - no 0 0 00:00:08.04 00:44:35.02 1243830 0 1247160 1247500 31 1
0 54 94 yes 1 no 0 0 00:00:13.11 00:44:48.13 1247501 1248540 1258399 1258669 32 1
0 55 222 yes 2 no 0 0 00:00:13.11 00:44:48.13 1248541 1249580 1259540 1259810 33 1
0 56 10 yes - no 0 0 00:01:00.03 00:45:48.16 1259811 0 1287128 1287317 34 1
0 57 94 yes 1 no 0 0 00:00:07.20 00:45:56.11 1287318 1288598 1292876 1293223 35 1
0 58 222 yes 2 no 0 0 00:00:07.20 00:45:56.11 1288599 1289879 1294073 1294420 36 1
0 59 10 yes - no 0 0 00:00:06.03 00:46:02.14 1294421 0 1296977 1297170 37 1
0 60 94 yes 1 no 0 0 00:00:11.06 00:46:13.20 1297171 1298212 1306067 1306242 38 1
0 61 222 yes 2 no 0 0 00:00:11.06 00:46:13.20 1298213 1299254 1307233 1307408 39 1
0 62 10 yes - no 0 0 00:00:17.05 00:46:31.00 1307409 0 1314955 1315124 40 1
0 63 94 yes 1 no 0 0 00:00:11.23 00:46:42.23 1315125 1316163 1324311 1324666 41 1
0 64 222 yes 2 no 0 0 00:00:11.23 00:46:42.23 1316164 1317202 1325637 1325992 42 1
0 65 10 yes - no 0 0 00:00:38.02 00:47:21.00 1325993 0 1342789 1343056 43 1
0 66 94 yes 1 no 0 0 00:00:04.09 00:47:25.09 1343057 1343925 1345624 1345899 44 1
0 67 222 yes 2 no 0 0 00:00:04.09 00:47:25.09 1343926 1344794 1346729 1347004 45 1
0 68 10 yes - no 0 0 00:00:31.14 00:47:56.23 1347005 0 1360669 1361069 46 1
0 69 94 yes 1 no 0 0 00:00:08.11 00:48:05.09 1361070 1362316 1366891 1367290 47 1
0 70 222 yes 2 no 0 0 00:00:08.11 00:48:05.09 1362317 1363563 1368398 1368798 48 1
0 71 10 yes - no 0 0 00:00:16.04 00:48:21.13 1368799 0 1375770 1376059 49 1
0 72 94 yes 1 no 0 0 00:00:16.01 00:48:37.14 1376060 1377093 1389144 1389532 50 1
0 73 222 yes 2 no 0 0 00:00:16.01 00:48:37.14 1377094 1378128 1390384 1390772 51 1
0 74 10 yes - no 0 0 00:00:24.10 00:49:01.24 1390773 0 1401442 1401706 52 1
0 75 94 yes 1 no 0 0 00:00:04.13 00:49:06.12 1401707 1402732 1404416 1404780 53 1
0 76 222 yes 2 no 0 0 00:00:04.13 00:49:06.12 1402733 1403755 1405443 1405807 54 1
According to the error message, angle 1 is correct, but angle 2 is missing or not correctly defined. This is why the problem does not happen when angle 1 must be played. Do you have removed an angle, or modified the cells table in any way?
No, I havent removed any angles or modified anything. Well, actually I have, but in these tests its the untouched output from DVDFAB.
Another question: when angle 1 is played, do you see the movie normally, or the multi-angle parts are shown interleaved (like with v8.6)?
When angle 1 is played, i see the movie normally and only angle 1 is shown (not interleaved like with v8.6).
Can you also try to preview the PGC directly, and not from the trace? PgcEdit should display a little dialog where you can select the angle you want to display. Does it work?
The preview works fine with I select angle 2. It then only shows the desired angle (unless i seek with the slider real fast, then it shows both angles interleaved. Seeking with the cursors (arrows) works fine as well and only shows the desired angle.
PS: I had to split the post because the cell table was so incredibly long and exceeded the character limitation per post.
vwpassion
23rd January 2009, 16:02
Here is part 2 of the cell table (see previous post for part 1):
0 17 17 77 10 yes - no 0 0 00:00:16.07 00:49:22.19 1405808 0 1412899 1413126 55 1
0 78 94 yes 1 no 0 0 00:00:08.24 00:49:31.18 1413127 1414034 1419714 1420070 56 1
0 79 222 yes 2 no 0 0 00:00:08.24 00:49:31.18 1414035 1414942 1420930 1421286 57 1
0 80 10 yes - no 0 0 00:00:03.22 00:49:35.15 1421287 0 1422754 1423037 58 1
0 81 94 yes 1 no 0 0 00:00:03.15 00:49:39.05 1423038 1424671 1424287 1424671 59 1
0 82 222 yes 2 no 0 0 00:00:03.15 00:49:39.05 1424672 1426306 1425922 1426306 60 1
0 83 10 yes - no 0 0 00:00:23.13 00:50:02.18 1426307 0 1436812 1437148 61 1
0 18 18 84 94 yes 1 no 0 0 00:00:04.12 00:50:07.05 1437149 1438072 1439801 1440053 62 1
0 85 222 yes 2 no 0 0 00:00:04.12 00:50:07.05 1438073 1438996 1440858 1441111 63 1
0 86 10 yes - no 0 0 00:00:05.06 00:50:12.11 1441112 0 1443289 1443459 64 1
0 87 94 yes 1 no 0 0 00:00:09.03 00:50:21.14 1443460 1444502 1450116 1450520 65 1
0 88 222 yes 2 no 0 0 00:00:09.03 00:50:21.14 1444503 1445545 1451388 1451792 66 1
0 89 10 yes - no 0 0 00:00:17.12 00:50:39.01 1451793 0 1459301 1459642 67 1
0 90 94 yes 1 no 0 0 00:00:44.15 00:51:23.16 1459643 1460689 1499131 1499342 68 1
0 91 222 yes 2 no 0 0 00:00:44.15 00:51:23.16 1460690 1461735 1500218 1500429 69 1
0 92 10 yes - no 0 0 00:00:07.20 00:51:31.11 1500430 0 1503692 1503929 70 1
0 93 94 yes 1 no 0 0 00:00:03.10 00:51:34.21 1503930 1505423 1505218 1505423 71 1
0 94 222 yes 2 no 0 0 00:00:03.10 00:51:34.21 1505424 1506914 1506709 1506914 72 1
0 95 10 yes - no 0 0 00:00:05.20 00:51:40.16 1506915 0 1509333 1509514 73 1
0 96 94 yes 1 no 0 0 00:00:03.23 00:51:44.14 1509515 1511221 1510858 1511221 74 1
0 97 222 yes 2 no 0 0 00:00:03.23 00:51:44.14 1511222 1512926 1512563 1512926 75 1
0 98 10 yes - no 0 0 00:00:04.11 00:51:49.00 1512927 0 1514641 1514922 76 1
0 99 94 yes 1 no 0 0 00:00:20.24 00:52:09.24 1514923 1516207 1532607 1532930 77 1
0 100 222 yes 2 no 0 0 00:00:20.24 00:52:09.24 1516208 1517493 1533765 1534088 78 1
0 101 10 yes - no 0 0 00:00:14.21 00:52:24.20 1534089 0 1540555 1540756 79 1
0 102 94 yes 1 no 0 0 00:00:05.18 00:52:30.13 1540757 1542018 1544366 1544614 80 1
0 103 222 yes 2 no 0 0 00:00:05.18 00:52:30.13 1542019 1543280 1545700 1545948 81 1
0 104 10 yes - no 0 0 00:00:05.13 00:52:36.01 1545949 0 1548536 1548687 82 1
0 19 19 105 8 yes - no 0 0 00:01:15.03 00:53:51.04 1548688 0 1582036 1582272 82 2
0 20 20 106 8 yes - no 0 0 00:01:47.16 00:55:38.20 1582273 0 1629134 1629276 82 3
0 21 21 107 8 yes - no 0 0 00:00:41.10 00:56:20.05 1629277 0 1648590 1648747 82 4
0 22 22 108 8 yes - no 0 0 00:00:48.24 00:57:09.04 1648748 0 1670794 1670975 82 5
0 109 94 yes 1 no 0 0 00:00:03.06 00:57:12.10 1670976 1672392 1671998 1672392 83 1
0 110 222 yes 2 no 0 0 00:00:03.06 00:57:12.10 1672393 1673809 1673414 1673809 84 1
0 111 10 yes - no 0 0 00:02:32.19 00:59:45.04 1673810 0 1743419 1743639 85 1
0 23 23 112 8 yes - no 0 0 00:00:33.02 01:00:18.06 1743640 0 1758169 1758513 85 2
0 113 94 yes 1 no 0 0 00:00:08.16 01:00:26.22 1758514 1759517 1765347 1765572 86 1
0 114 222 yes 2 no 0 0 00:00:08.16 01:00:26.22 1759518 1760522 1766150 1766375 87 1
0 115 10 yes - no 0 0 00:00:21.18 01:00:48.15 1766376 0 1775503 1775659 88 1
0 24 24 116 8 yes - no 0 0 00:01:59.11 01:02:48.01 1775660 0 1830948 1831203 88 2
0 117 94 yes 1 no 0 0 00:00:06.05 01:02:54.06 1831204 1832696 1835266 1835484 89 1
0 118 222 yes 2 no 0 0 00:00:06.05 01:02:54.06 1832697 1834188 1836562 1836780 90 1
0 119 10 yes - no 0 0 00:00:16.23 01:03:11.04 1836781 0 1845077 1845411 91 1
0 25 25 120 8 yes - no 0 0 00:00:41.11 01:03:52.15 1845412 0 1862756 1862953 91 2
0 121 94 yes 1 no 0 0 00:00:03.01 01:03:55.16 1862954 1864253 1864082 1864253 92 1
0 122 222 yes 2 no 0 0 00:00:03.01 01:03:55.16 1864254 1865553 1865382 1865553 93 1
0 123 10 yes - no 0 0 00:01:17.10 01:05:13.01 1865554 0 1899870 1900225 94 1
0 124 94 yes 1 no 0 0 00:00:20.04 01:05:33.05 1900226 1901257 1917392 1917622 95 1
0 125 222 yes 2 no 0 0 00:00:20.04 01:05:33.05 1901258 1902289 1918509 1918739 96 1
0 126 10 yes - no 0 0 00:03:02.07 01:08:35.12 1918740 0 2000303 2000542 97 1
0 127 8 yes - no 0 0 00:00:14.15 01:08:50.02 2000543 0 2006881 2006999 97 2
0 128 10 yes - no 0 0 00:00:01.18 01:08:51.20 2007000 0 2007045 2007165 98 1
0 26 26 129 94 yes 1 no 0 0 00:00:10.10 01:09:02.05 2007166 2008307 2014606 2014810 99 1
0 130 222 yes 2 no 0 0 00:00:10.10 01:09:02.05 2008308 2009451 2015907 2016111 100 1
0 131 10 yes - no 0 0 00:01:07.11 01:10:09.16 2016112 0 2045977 2046328 101 1
0 132 94 yes 1 no 0 0 00:00:03.04 01:10:12.20 2046329 2047723 2047455 2047723 102 1
0 133 222 yes 2 no 0 0 00:00:03.04 01:10:12.20 2047724 2049118 2048850 2049118 103 1
0 134 10 yes - no 0 0 00:01:02.22 01:11:15.17 2049119 0 2077342 2077663 104 1
0 135 94 yes 1 no 0 0 00:00:03.00 01:11:18.17 2077664 2078972 2078712 2078972 105 1
0 136 222 yes 2 no 0 0 00:00:03.00 01:11:18.17 2078973 2080281 2080021 2080281 106 1
0 137 10 yes - no 0 0 00:00:31.02 01:11:49.19 2080282 0 2095103 2095380 107 1
0 138 94 yes 1 no 0 0 00:00:03.00 01:11:52.19 2095381 2096727 2096371 2096727 108 1
0 139 222 yes 2 no 0 0 00:00:03.00 01:11:52.19 2096728 2098074 2097718 2098074 109 1
0 140 10 yes - no 0 0 00:00:58.04 01:12:50.23 2098075 0 2122375 2122674 110 1
0 27 27 141 8 yes - no 0 0 00:01:30.07 01:14:21.05 2122675 0 2164200 2164552 110 2
0 142 94 yes 1 no 0 0 00:00:03.00 01:14:24.05 2164553 2165902 2165675 2165902 111 1
0 143 222 yes 2 no 0 0 00:00:03.00 01:14:24.05 2165903 2167253 2167026 2167253 112 1
0 144 10 yes - no 0 0 00:01:46.19 01:16:10.24 2167254 0 2216317 2216486 113 1
0 28 28 145 8 yes - no 0 0 00:00:02.18 01:16:13.17 2216487 0 2217345 2217740 113 2
0 146 8 yes - no 0 0 00:00:47.01 01:17:00.18 2217741 0 2239494 2239664 113 3
0 29 29 147 8 yes - no 0 0 00:02:29.11 01:19:30.04 2239665 0 2306808 2307068 113 4
0 148 94 yes 1 no 0 0 00:00:04.03 01:19:34.07 2307069 2308915 2308721 2308915 114 1
0 149 222 yes 2 no 0 0 00:00:04.03 01:19:34.07 2308916 2310763 2310569 2310763 115 1
0 150 10 yes - no 0 0 00:00:19.13 01:19:53.20 2310764 0 2319111 2319484 116 1
0 151 94 yes 1 no 0 0 00:00:03.16 01:19:57.11 2319485 2321089 2320819 2321089 117 1
0 152 222 yes 2 no 0 0 00:00:03.16 01:19:57.11 2321090 2322695 2322425 2322695 118 1
0 153 10 yes - no 0 0 00:00:52.22 01:20:50.08 2322696 0 2347621 2347794 119 1
0 30 30 154 8 yes - no 0 0 00:01:27.23 01:22:18.06 2347795 0 2385328 2385635 119 2
0 31 31 155 8 yes - no 0 0 00:00:45.21 01:23:04.02 2385636 0 2405813 2406161 119 3
0 156 94 yes 1 no 0 0 00:00:05.06 01:23:09.08 2406162 2407267 2409208 2409459 120 1
0 157 222 yes 2 no 0 0 00:00:05.06 01:23:09.08 2407268 2408373 2410293 2410544 121 1
0 158 10 yes - no 0 0 00:00:57.19 01:24:07.02 2410545 0 2435922 2436335 122 1
0 159 8 yes - no 0 0 00:02:31.16 01:26:38.18 2436336 0 2503965 2504152 122 2
0 32 32 160 8 yes - no 0 6 00:06:45.03 01:33:23.21 2504153 0 2684880 2684990 122 3
0 33 33 161 2 no - no 0 0 00:00:00.12 01:33:24.08 2726820 0 2726820 2726825 126 1
Edit: Oh crap, you've posted at the same time I have. Never mind then. Thanks for looking into it anyway. Waiting for the new version! :)
r0lZ
23rd January 2009, 16:08
I was sure the cell table was correct, as I had no difficulty to reproduce the problem with the little "test angle DVD" I have permanently on my hard disc. I don't understand why we haven't found this problem sooner. Thanks again, and sorry for the unnecessary double post!
I will probably release v9.2 soon...
mikenadia
24th January 2009, 16:19
From r0lZ:However, if a new button is created in an additional set, or if the command of a button changes, and if the new command is a jump, call or link, you should take care, especially with the commands that modify the DVD structure deeply, such as most of the remapping functions.
If I have only multiple sets of BOVs in only one VOB (even with call or link new commands), am I safe by deleting uncalled PGCs in the VMGM and other VOBs?
In my case, the "remove useless stuff" deleted all uncalled PGCs in the VMGM (does not seems to have created nav issues) . I did not have the possibility not to do " Delete uncalled PGCs" (as it was the case for " Delete uncalled Titleset or Clear useless Set GPRM commands") once I started this procedure (with every procedure checked).
Thanks in advance.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.