PgcEdit v9.0 released (24 Dec 2008) and v9.1 (3 Jan 2009)

[r0lZ]

PgcEdit v9.0 finally released!

The changes are so numerous that I can't list them all here.
See What's new in PgcEdit v9 (http://download.videohelp.com/r0lZ/pgcedit/new_in_v9.html).

Please note that there are new versions of the Play All PGC and the VOBU plugins. Please download and install them if you need them, as the old versions may be incompatible with PgcEdit v9.

Also, the Time Maps and Language Unit (LU) plugins are now deprecated, as their functions have been integrated in PgcEdit itself.


Now, the bad news:

PgcEdit is no longer totally free! A nag screen is displayed during some seconds when PgcEdit starts, to boost the donations! Apart from that, no functionalities of PgcEdit are disabled. The source code is temporarily unavailable, of course.

The donors that have donated even a single $ in the past, will receive by email a code to disable the nag screen. If you haven't received your code in 2 or 3 days, please send me an email. (My email address is on the PgcEdit homepage, in the contact (http://download.videohelp.com/r0lZ/pgcedit/#contact) section.) Also, if you have helped me in the past, for example by writing some guides, you may receive a free code. Again, write me!
I wish to thank the peoples who have already donated. Unfortunately, they are not numerous, and therefore I had to introduce this little limitation. Sorry for the inconvenience.
The guys who have not donated yet will need to pay at least $15 or €10 to receive the code. Sorry, guys, you should have donated when PgcEdit was free!

[ron spencer]

cool!!!!

this program should have been a pay type thing long ago....superb!!!

[Hubbabub]

Very good.

I'm now a donor :)

Thank you for the super program

[Wombler]

Finally the momentous event arrives!! :cool:

Take note of the massive changelog guys.

This is the cut down version too!

In the end it took 92 betas and a years development to get to this stage and r0lZ has put an absolutely phenomenal amount of work into this release.

His program is by far the best of its type so where possible give some thought to supporting his efforts.

Thanks r0lZ!


Wombler

[blutach]

What a great XMAS present for the community! Thank you r0lZ - mille mercis!!!

And I couldn't agree more with ron spencer and Wombler.

Regards

[Sir Didymus]

Congratulation r0lZ!

I am sure the release of version 9 will be appreciated as a fantastic Christmas gift from a very large number of users!

Cheers,
SD

[r0lZ]

Thanks for the thanks!
And thanks to all beta testers! You have made a wonderful work!

Merry XMas to everybody!

[r0lZ]

Thanks to the beta team, I have just fixed a bug in v9.0.

When you select the menu "Preview -> Automatically start preview playback?", an error message is displayed.
Don't worry. This error has no consequence. Just cancel the error dialog.

Of course, this bug will be fixed in v9.1. Pity we haven't noticed it yesterday!

[kikatu]

Thanks r0lZ & testers for all the hard work. PgcEdit owns our DVD backups.

Enjoy the holidays or the days ahead guys.

[ron spencer]

race is on....9.1 before christmas LOL!!!!

[blutach]

LOL Ron. The bug is so small, it would be v9.001 :)

Regards

[President]

Thank's, r0lZ, for the release and wonderful XMAS gift!!!

[M_Knox]

When the last VTS is selected (in this case 2) and I do DVD->Delete last VTS in DVD, the VTS gets deleted but PgcEdit displays the message:

Error: can't read "::pgcs(2,1,cellpbt...

Message details are:
can't read "::pgcs(2,1,cellpbtable)": no such element in array
can't read "::pgcs(2,1,cellpbtable)": no such element in array
while executing
"set cellpbtable $::pgcs($vts,$pgc,cellpbtable)"
(procedure "refresh_listbox" line 18)
invoked from within
"refresh_listbox"
(procedure "scratchbook" line 46)
invoked from within
"scratchbook false"
(procedure "cmds_to_listbox" line 4)
invoked from within
"cmds_to_listbox pgc $vts,$pgcnum $label"
(procedure "::main::display_pgc" line 6)
invoked from within
"::main::display_pgc pgc 0 0"
(procedure "::utils::delete_last_vts" line 142)
invoked from within
"::utils::delete_last_vts"
(menu invoke)

Closing the message and clicking any other VTS or VMG results in the same message over and over again, until the application is restarted.

[r0lZ]

OK, thanks for the bug report. I'll fix this bug soon...

[r0lZ]

OK, bug fixed. I'll release v9.1 soon.
In the meantime, when you delete the last VTS, just select a PGC in another VTS before calling the function. That way, the bug doesn't happen.

[vwpassion]

Thank you r0lZ! Great update, and what a changelog... Am happy to donate because I can imagine how much time and effort you put into all these changes.

[vwpassion]

I noticed that when i check "State -> Mark played PGCs as played" in trace mode this setting is reset once i restart pgcedit. Is this a bug? Would be nice to have this feature enabled at all times.

[r0lZ]

Are you sure? IMO, this function is only useful if you use it only during short navigation sessions, for example when you go to one point of the DVD to another one, to analyze the PGCs that were played, and see, for example, if you can skip them. IMO it doesn't make sense to mark all PGCs as played every time.
Also, the yellow highlights are also there for this purpose. (But they are reset when you reset or quit the trace.)

[vwpassion]

Are you sure? IMO, this function is only useful if you use it only during short navigation sessions, for example when you go to one point of the DVD to another one, to analyze the PGCs that were played, and see, for example, if you can skip them. IMO it doesn't make sense to mark all PGCs as played every time.
Also, the yellow highlights are also there for this purpose. (But they are reset when you reset or quit the trace.)

I do you see your point, but when searching for uncalled pgcs or tracing through the whole structure I found it to be quite useful, even more than just the yellow markers. But I don't really mind, setting it manually isnt much of a big deal anyway. Just figured it might as well be a bug.

[selyb]

SWEET!!
I've been waiting for this release for... um... a while anyway :)
I haven't yet been able to check out all the new features/fixes yet but I did find this:

Bug: for me, the menu item 'Trace>Trace Mode' is grayed out even after I open a dvd
the hotkey works fine though

Bug: I have the toolbar turned off usually
If I use the menu 'View>Toobar' to show it, then I click on Trace Mode button, then go back to the 'View Menu', Toolbar is unchecked
When I click on it, the toolbar stays open and the checkmark appears next to the menu item, clicking on View>Toolbar again hides it again

[blutach]

It's working here selyb. Many items are greyed out if a DVD is not loaded, but you say you have opened a DVD. So that is strange.

As for the View Toolbar issue, I can't reproduce that one either.

Regards

[selyb]

It's working here selyb. Many items are greyed out if a DVD is not loaded, but you say you have opened a DVD. So that is strange.

As for the View Toolbar issue, I can't reproduce that one either.

Regards

Then, it probably depends on the options I have set :-/

[r0lZ]

Thanks for the report. But, like blu, I cannot reproduce the bugs. Could you send me your configuration files? (They are in "Documents and Settings\<you>\Application Data\PgcEdit".) Thanks in advance.

[Wombler]

I get the same thing here but didn't realise that it wasn't supposed to be that way.

The icon is greyed out but changes to colour when selected.

Is it supposed to change as soon as the DVD is loaded or just when trace mode is activated?


Wombler

[r0lZ]

The Trace icon is gray when trace mode is turned off, and turns blue when you enable it. So, Wombler, what you have noticed is normal.

Selyb has another problem: the Trace menu item (not the toolbar) stays disabled when a DVD has been loaded. (Is it right, selyb?) Obviously, that's abnormal.
He has also another problem when toggling the toolbar on or off.

[selyb]

that's correct

I couldn't get the toolbar thing to happen after I restarted pgcedit

Edit: Well, I reproduced both things

1. Opened F:\Programs\pgcedit\pgcedit.exe
2. Open dialog automatically shows last dvd I opened
3. Clicked ok
4. After dvd is opened, pgcedit is in trace mode, menu item is disabled and checked

I have yet to find a way to enable it
I even deleted my configuration and reconfigured from scratch

pgcedit config folder is C:\Users\x\Application Data\PgcEdit
system drive is C:
pgcedit is installed in F:\programs\pgcedit\

for the toolbar, I did reproduce it

1. Open pgcedit
2. opened DVD
3. Trace mode is enabled and toolbar is disabled (I have those options set)
4. Clicked menu View>Toolbar
5. clicked trace menu button on toolbar (to disable trace mode)
6. clicked menu View and Toolbar is unchecked

when I click on menu View>Toolbar, the toolbar flickers once but stays enabled

[mikenadia]

The following error occurred after doing "Jump to PGC upon insert" on a second level menu (Trace mode; go to first menu and then select). It does not occur if I do the same procedure at the first level menu.
After doing the "jump to PGC procedure I have an error message when trying to unclick "Trace mode" or running "Remove useless stuff" (cf log).
can't read "::pgcs(0,0,TTN)": no such element in array
can't read "::pgcs(0,0,TTN)": no such element in array
while executing
"set cur_ttn $::pgcs($cur_vts,$cur_pgc,TTN)"
(procedure "trace_disasm_link" line 21)
invoked from within
"trace_disasm_link $hex $k $ll $nexteditorline -200"
("7" arm line 43)
invoked from within
"switch $cmdtype {
0 {
# flow control commands
switch [::disasm::get_nibble $hex 1 1] {
0 {
# NOP
# TODO: What is the correct beh..."
(procedure "trace_disasm_button_cmd" line 8)
invoked from within
"trace_disasm_button_cmd $cmd"
(procedure "simulate_play" line 347)
invoked from within
"simulate_play"
(procedure "step" line 10)
invoked from within
"step"
(procedure "reset_trace" line 159)
invoked from within
"reset_trace"
(procedure "::tr::dvd_trace" line 399)
invoked from within
"::tr::dvd_trace"
One way to go around it.Run "remove useless menu VOBs", then untick "Trace mode", then "Remove useless stuff".
(there are 3 uncalled PGC due to the "Jump to PGC" procedure (2 +1).
If I do "Delete uncalled PGC" , I have an error message at the second loop.

I hope I am not too confusing (or confused).

[r0lZ]

1. Opened F:\Programs\pgcedit\pgcedit.exe
2. Open dialog automatically shows last dvd I opened
3. Clicked ok
4. After dvd is opened, pgcedit is in trace mode, menu item is disabled and checked
I did exactly the same thing, and no problem here. The Trace Mode menu item is enabled and checked, as it should.

for the toolbar, I did reproduce it

1. Open pgcedit
2. opened DVD
3. Trace mode is enabled and toolbar is disabled (I have those options set)
4. Clicked menu View>Toolbar
5. clicked trace menu button on toolbar (to disable trace mode)
6. clicked menu View and Toolbar is unchecked

when I click on menu View>Toolbar, the toolbar flickers once but stays enabled
That's right. I suspect a bug in Tcl/Tk, but I will investigate...

[r0lZ]

I hope I am not too confusing (or confused).Well, I've located and fixed the bug that has caused the first error (and the error message you posted), but I can't verify if the subsequent errors are fixed as well without the DVD or more info. However, cascaded bugs are usually a consequence of the first bug, so I suppose they have all been fixed.
Please keep your original IFOs in a safe place (with the menubuttons.but file located in the backup folder), and try to reproduce the bug when v9.1 will be available. Thanks!

[mikenadia]

Thank you. Will go back from the original with 9.1 and post results.
Also, in another DVD, I have two PGC for which I want to kill Playback and regain space in VOBblanker. In v 8.6, each of them allowed me to gain space in VOBblanker (by just clicking on "Process"). in v 9.0, only one (for the other one, I have to blank the cell). I do not know if it was intended or not.

Thanks and Happy New Year.

[r0lZ]

It's certainly not intended. But if the cell of the PGC are used by another PGC (in the same VMGM, VTSM or VTST domain), VobBlanker cannot remove them, or the other PGC will not work any more. Verify if the cells are reused elsewhere. (You can do that easily by looking at their VOB/Cell IDs in the cell tables, or with the preview.)

[r0lZ]

Selyb, I've fixed the second bug, but I still can't reproduce the first one.

BTW, do you know that you can close the trace window easily by clicking on the X button in the top right corner of the Trace panel? (But you still need to go to the menu or use the hotkey to re-enable it.) Anyway, the bug happens also when using this method.

[r0lZ]

I have now finished to send all codes to the old and new donors. You should have received them. However, some email addresses of old donors are not valid any more, and of course I have no way to contact them. Remember that you can receive a free license if you have donated in the past. Write me if you haven't received your code yet.

IMPORTANT:

Since I've sent many emails to the donors to give them their codes, and that mails were generated automatically by a program, they were all similar, and I have been blacklisted by some mail servers (notably by comcast.net) for SPAM!
:devil:

So, if you haven't received your code yet, please send me an email. Sorry for the inconvenience.

[Wombler]

Selyb, I've fixed the second bug, but I still can't reproduce the first one.


Can't reproduce it here either.

r0lZ could you approve the attachment in post 26 so we can have a look at it.


Wombler

[r0lZ]

r0lZ could you approve the attachment in post 26 so we can have a look at it.
I'm not mod here! :(

[ron spencer]

you can be a mod at dvdlab site though....you were asked to be:

http://www.mmbforums.com/ipb/index.php?showtopic=6182&st=60&start=60

[mikenadia]

ref to post #30.
Sorry. My mistake. Went to Vobblanker with PGCedit still open and the DVD changes were not saved.
Was doing that in v 8.6 but it was saved automatically by other procedures. Won't happen anymore
(configured VOBBlanker in tools). Sorry and thanks a lot.

[blutach]

selyb's attachment is approved! I was away yesterday.

Regards

[r0lZ]

Thanks, Ron. I've replied at MMB.
Thanks for the confirmation, mikenadia.
Thanks for the approval, Blu.

[CiXel]

Since moving to 9.0 under XP my watch window no longer launches upon entering trace mode. There is no option to re-enable it under Trace either. I never had it disappear before. Is this a Bug or a new RTFM ;)

[blutach]

Welcome to Doom9 CiXel.

In trace mode, check if anything is ticked under the Watch menu. Mine works OK (I have Input, GPRMS, SPRMS and SPRM Labels). Note - once you unwatch something, you need to re-enable it - this has always been the case.

Regards

[linx05]

Thank you very much for version 9.0! I am loving it. I did however find one thing that needs fixing.

Without loading a DVD and using the VOBU plugin (v1.5) - Plugins > VOBU > Check for missing.... This causes this error to appear:

can't read "::pgcs(numvts)": no such variable
can't read "::pgcs(numvts)": no such variable
while executing
"for {set vts 0} {$vts <= $::pgcs(numvts)} {incr vts} {
for {set vid 1} {$vid <= $::buttons::butsinfo(menu,$vts,numvobids)} {incr vid} {
if {$::bu..."
(procedure "::plugins::vobu::check_missing_ids" line 4)
invoked from within
"::plugins::vobu::check_missing_ids"
(menu invoke)

[blutach]

Of course it will have an error. Thre is no DVD loaded. It's telling you that.

Regards

[linx05]

Yes, but it shouldn't error out like that. A 'cleaner' way would be to state there is no DVD loaded.

I will keep playing around with it.

[r0lZ]

Since moving to 9.0 under XP my watch window no longer launches upon entering trace mode. There is no option to re-enable it under Trace either. I never had it disappear before. Is this a Bug or a new RTFM ;)Nothing changed here.

To reopen the watch window, go to trace mode, and select the options you want in the Watch menu of the trace panel.

The state and position of the watch window are recorded when you quit trace mode (or PgcEdit), and restored when you re-enter it. (That means that you should not close the watch window before quitting trace mode, or PgcEdit will record its absence.)

[EDIT] I did not notice the replies on this page. Blu had already explained what to do. Thanks blu!

[r0lZ]

Yes, but it shouldn't error out like that. A 'cleaner' way would be to state there is no DVD loaded.I agree, and I have fixed this (really little) bug.

[mikenadia]

I have 2 DVDs; DVD1 (that I probably corrupt but cannot replicate it :user mistake!) and DVD2(straight rip).
I am able to open DVD1, then DVD2 or DVD2, then DVD1.
If I open DVD1 and run "Remove Useless VOBs menu" (save DVD or not: seems irrelevant), I have no error message until I open DVD2 (straight rip).
I have no other issue with that DVD1 (all other steps of "remove useless stuff" do not produce similar behaviour).
I think that the error should be trapped when I am manipulating or saving DVD1 and not opening DVD2.
can't read "::menus(9,1,1,cellpbtable)": no such element in array
can't read "::menus(9,1,1,cellpbtable)": no such element in array
while executing
"set cellpbtable $::menus($vts,$lu,$pgc,cellpbtable)"
(procedure "refresh_listbox" line 23)
invoked from within
"refresh_listbox"
(procedure "scratchbook" line 46)
invoked from within
"scratchbook false"
(procedure "cmds_to_listbox" line 4)
invoked from within
"cmds_to_listbox pgc $vts,$pgcnum $label"
(procedure "display_pgc" line 6)
invoked from within
"display_pgc pgc 0 0"
(procedure "::main::Read_New_DVD" line 99)
invoked from within
"::main::Read_New_DVD"
(menu invoke)
Thanks.

Workaround:After working in DVD1 (including "remove useless VOBs menu"), either close PGCEdit (obvious) or goto VOBblanker (through tools), do not process and quit: then, you can load DVD2 without any error message.

Pure cosmetics:When you open a DVD, and "Jump to PGC upon insert" on VMG: First-Play PGC (stupid behaviour I agree), you get a warning message with only a OK button (no cancel or exit). If you do the same thing from a previously DVD in which you actually did a "Jump to PGC upon insert" (on a real menu), you get an error (if you do not want us to report pure cosmetics issues:no problem).

[linx05]

Thank you r0lZ. I just thought I would let you know.

Thanks again.

[r0lZ]

Thanks mikenadia. I think I've fixed the main bug, but I'm not totally sure, as I can't reproduce it. Please test when v9.1 will be available (normally soon.)
I have also added a check for the cosmetic bugs. Now, if you try to apply Jump2PGC to the FP-PGC, nothing happens.

Thanks linx05!

[blutach]

@mikenadia

In testing, I notice these things a bit too. I think they come from corrupt menubutton files (in your backup directory). See if saving the DVD, deleting these files and re-opening helps.

Regards

[mikenadia]

Thanks ,Les, for your advice.
What I did.
Open the corrupt file,DVD1,save,delete the backup folder (including menu*.*), pgcedit still open, "remove useless VOB menus".
a) if I do the workaround in post#47, I am able to open DVD2(clean file).
b) if I reload the DVD1 file (without rerunning "remove useless VOB menus, I am able to open DVD2(clean file).
c)If I load DVD2 file (same error as post #47).
in a) and b) the fix is temporary .
The file is corrupt so it is not very important but when opening a file while one is open, may be we should really close the first one completely so it does not ( with a corrupt file opened as the first file) prevent the second one (clean file ) from opening.
Thx for your advice.

New info: the file is not corrupted. The problem occured with specific duos of DVDs (straight from the rip) and doing the following.
DVD1 is SPARTANSUNRATED; DVD2 is T4XI. load DVD1, "remove useless VOB menus", load DVD2. The problem occurs with specific duos of DVD (that is why I give the DVD titles ;if I load another DVD than T4XI, it may not happen even if T4XI was not modified by PGCEdit). Also,doing DVD2 first and loading DVD1 does not yield to an error (same thing for loading DVD1 then another DVD3 and then DVD2) From my experience, the problem is rare but not unique .

Edit: Corrected in v 9.1

[r0lZ]

Theoretically, you're right, mikenadia. But loading a DVD can be really long, and PgcEdit needs sometimes to save and reload a DVD just to synchronize the data in memory and on disc. This is the case, for example, when the titlesets are remapped, as they have to be remapped on disc too. I've tried to avoid to have to reload everything (for example, it is usually not necessary to rescan all VOB files for menu buttons and BOVs), but that means that a DVD is never unloaded totally. It is replaced by itself, or by another DVD. When a DVD is corrupt, that can have some bad consequences. Sorry for that, but I'm not going to change this philosophy. What you want would require to save the whole DVD (including the VOBs) in another directory every time you save it. It's the philosophy of DRM, but not mine. Anyway, you can get what you want simply by closing PgcEdit and reopening it with the new DVD.
Of course, if I can fix the bugs related to that method, I'm happy to do so, and I thank you for your bug report. As I said, I hope the bug has been fixed.

[selyb]

figured it out

Bug: if menu tearoffs is disabled, first item on Trace and Preview menus stay disabled

I disabled menu tearoffs the very first time I used pgcedit

[r0lZ]

Right! Thanks.

BTW, why have you disabled this option? IMO, it is extremely useful when you have to repeat the same operation several times. For example, when you need to delete many PGCs in a domain, it is much more easy to detach the menu and click repetitively on the menu entry. Personally, I can't live without that option. And it is in the options menu only because it crashed under old versions of Tcl/Tk for Mac OSX.

But I'm glad you don't use it, as you have found the bug! ;)

[Wombler]

figured it out

Bug: if menu tearoffs is disabled, first item on Trace and Preview menus stay disabled

I disabled menu tearoffs the very first time I used pgcedit

Good find selyb!

I'd been working my way through the differences in your configuration files and mine but I hadn't tried that one yet.

Saved me a lot of effort.


Wombler

[AlienX69]

Hi r0lZ (and others),

Well I finally got around to using 9.0 (just installed).

First thing I noticed after doing the Automatic install and installing the key is that it runs considerably SLOWER in Trace Mode. Previously it would ZIP (very fast) through the PGC's. Now it's almost like I'm manually clicking the -> Step button repeatedly.

Every time I select the ->> Next PB I can watch it step through the PGC's. If I had to apply a number to it I would say about 10x slower or more than 8.x !!

Well I don't know if "Speed" was on the older versions, if it was I don't remember (once set I never changed).

After setting to "Fastest" it returned to my normal tracing speed.

Just thought I would post in case someone else runs across this issue !!

PS: Haven't checked all the NEW features, but what I do see I like the improvements !!

Regards,
AX

[r0lZ]

The Speed setup is new. Previously, the same setup was used to control the speed of the trace itself and the minimum duration of the preview, but that was confusing, and it was impossible to trace the nav at slow speed with a short playback, or vice-versa. Therefore, I've split the setup in two independent controls.

[selyb]

Right! Thanks.

BTW, why have you disabled this option? ...

I don't like my desktop cluttered with different windows, esp. from the same app. If I had it my way, the watch window would be a small section just above the status bar.

I almost never remove pgcs manually. I edit the commands to remove references to pgcs then I use the menu item to remove unreferenced titlesets then uncalled pgcs.

For very repetitive motions, I prefer the keyboard over any mouse clicking which is why (several years ago) I had requested a keyboard shortcut for trace step. when I am moving commands around, I keep one hand on the keyboard to do shortcuts like Ctrl+C, Ctrl+X, Ctrl+G, Ctrl+V, Ctrl+Shift+V, Ctrl+A

[blutach]

Good find selyb!

I'd been working my way through the differences in your configuration files and mine but I hadn't tried that one yet.

Saved me a lot of effort.


WomblerYes, a good find!

@Wombler - use winmerge to discover differences between text files - it's a breeze.

Regards

[Wombler]

It wasn't actually finding the differences that was time consuming bit, it was changing each of the non-matching configuration settings individually to see if I could replicate the circumstances causing the bug that was a bit tedious.

PgcEdit also had to be closed and restarted on each occasion.

Good call with winmerge though. Nice addition to my toolkit. :)


Wombler

[Big Barn]

Can someone tell me where is that setting to speed up
the trace mode.

Thank You

[mikenadia]

I read Blutach manual in http://www.digital-digest.com/~blutach/pgcedit_guide/remapping/PgcEdit_Advanced_Functions.htm
and it says that it can restore to an earlier state .
It seems (and may be it is wrong) that I am able to go back to the initial stage (straight from the rip) by copying back all the files from the Backup sub-folder (without the menu*.* and comment*.*).
The problem occurs when, after some procedures and doing "remove useless stuff ", the file VIDEO_TS (DVD movie not the IFO file) is deleted rightfully from the VIDEO_TS folder , a backup is made with a timestamp that includes the deleted file, but no trace of the deleted file in the Backup subfolder (therefore the "restore backup" do not bring me to the initial state (until I bring back the deleted file from that specific timestamped backup) and without doing incremental restore, I do not know that I am missing the deleted file.

Thanks for your advice on how to go back to the initial state (without reripping).

And, more important, Happy New Year to all, specially dev(s).

[blutach]

You don't need to copy. Just Ctrl-Alt-N (Restore Incremental backups) all the way back. It also tells you when to (manually) restore the FixVTS, MenuShrink and VobBlanker backups.

Regards

[mikenadia]

Thank you, Blutach.
N.B. Pure cosmetics : when doing a restore in Trace mode , it keeps the breakpoint (but it may be a different file). May be should have the same behaviour as loading a recent file (goto VMG-FP and clear breakpoints). And some "comments" (do not know about SPRM) left when there is no more incremental backup left ( "Jump2PGC_control " left in the "info,GPRM" window))
Thx.

[blutach]

Yes, I've noticed that sometimes some comments are left - I suspect this is because there will have been comments in your 1st incremental backup. They are easy to delete from the File --> Comments and GPRM Labels function. And, of course, the trace is easily re-initialised.

Regards

[r0lZ]

The backups have to be restored in the correct order. As blu said, use Undo Last Incremental Backup.

Also, to be on the safe side, you should always accept to copy the modified VOBs in the backup folder when prompted to do so. (It's an option, as this could be time consuming or require too much disc space, and some users prefer to take the risk of IFOs-only backups.)

Can someone tell me where is that setting to speed up the trace mode.
In the trace panel, menu "speed". Easy, no? ;)

[mikenadia]

Great program RolZ. Because I was not backing up the modified VOB (a must) as a consequence of my laziness not risk-taking , my restores were usually not working and that is why I asked those questions. Because it is a chain of incremental backup ( as strong as the weakest link), my advice to " more newbies than me" is do not open a backup folder (yes I did that and will not do it again) as it may affect the chain ( I did not test it).
Thanks a lot.

[blutach]

Opeing the folder is not the issue - certainly, saving the VOBs is a must; otherwise, it is impossible to restore the backup if you have done anything to them (including deleting uncalled PGCs, which will remap the menu button commands and running FixVTS which will delete actual cells from the VOB).

In a restore, it is necessary to manually restore some backups ("alien" backups - eg FixVTS_backup and VobBlanker_backup).

Regards

[mikenadia]

last question on this subject.I have some incremental backups from PGCEdit , and later on, one made by VOBBlanker (having only cut some frames in some cells before processing).
If I am processing them with DVD-RB and decide to keep everything in the VIDEO_TS folder (including backups from PGCEdit but not the one from VOBblanker), will it be meaningful to use those PGCEdit backups or should I delete them because I did not keep the last backup (made by VOBblanker).
Or may be I should cut the frames first in VOBblanker and then go to PGCEdit ?
Thx for your advice.

[r0lZ]

A missing backup when restoring things to an earlier stage can have disastrous consequences, but can also be harmless. Usually, if the VOB files are modified, or if the order or the number of titlesets has changed, it is necessary to have the backup. So, if you have deleted a VB backup, you can probably delete all previously made PgcEdit backups, as they are useless.

[stereo]

Hi r0lZ,

When I launch Firefox (my standard browser) through Help -> Homepage, PgcEdit tells me that Firefox isn't my standard browser. I guess this is a bug, though a small one.

Again, thanks for the new version, glad I donated!

[r0lZ]

Hum, PgcEdit doesn't check your standard browser, and doesn't issue any warning about your browser. Try to reconfigure it via Options -> Input/Output -> Select Web Browser.

[stereo]

That helped, thanks! I must have configured v8.6 without remembering it...

[r0lZ]

PgcEdit v9.1 released!

This is a bugfix release. Please download and install it as soon as possible, as I have fixed two bugs that can have consequences on the navigation of the DVD!

F. DVD -> Clear Useless Set GPRM Commands and Info -> Find Useless Set GPRM Commands were sometimes erroneously considering a GPRM as useless. Clear Useless Set GPRM Commands and DVD -> Remove Useless Stuff were therefore dangerous to use, as they sometimes cleared a useful command.
F. DVD -> Delete Last VTS produced an error when a PGC of the last VTS was selected when calling this function. The VTS was not properly deleted from disc.
F. Preview -> Automatically Start Preview Playback produced an error. The menu worked as expected though, and the bug had no consequence.
F. With the option "Allow tearoff menus" disabled, some entries in the main PgcEdit menu were not enabled when a DVD was loaded.
F. Fixed the incorrect View -> Toolbar checkmark.
E. Title -> Title Play Map Table: The headers of the columns no longer scroll when using the scroll bar.
F. A JumpSS from a VTSM to a menu in another VTS was not flagged as illegal.
F. PUO Editor: PgcEdit was frozen after having pasted a value in the Input Value dialog.
F. Trace: The trace was stopped and impossible to continue when the preview was enabled and the VOB files were missing.
F. Domain Stream Attributes: The new Film/Camera flag was not disabled in read-only mode.
F. Since the sources of PgcEdit are no longer publicly available, I've removed all references to the GPL license from the program.
F. Fixed several small bugs.


New plugin:
Hex Bit Operands by Morris/Elysium (aka M_Knox):
- Allows display of bit operations values in hex
- Allows display descriptive bit operands
Note that you need PgcEdit v9.1 to use this plugin!

This excellent plugin modifies the way the commands containing bitwise operators are displayed by PgcEdit. There is an option to display the operand in hexadecimal instead of the standard decimal value, and an option to add a description of the affected bits.

For example, the command:
Set gprm(0) &=(and) 10
can be displayed as:
Set gprm(0) &=(and) 0x000A (preserve bits 1, 3)
Really useful! Thanks M_Knox!

[mikenadia]

Thanks a lot, R0lZ. No more error messages for me (I had no clue of the bug so cannot say it is fixed:) ) but everything is perfect on my side.
Also , tried to delete a sub-menu (straight from the rip) and got an error message (cf log: the DVD has ILVU: probably irrelevant).
The error message invites me to fix it with IFOEdit (I'd rather not delete the sub-menu) but should I still go to IFOEdit even without deleting the sub-menu (bad rip or whatever).
MsgBox "PgcEdit: Kill PGC Playback" -> yes

ERROR! get_int: Attempt to read 2 bytes at offset 0 (0x0) after end of table!
Variable: cellpostable, length of table: 0
MsgBox "PgcEdit fatal error" -> no
*** Dialog title: "PgcEdit fatal error"
*** Dialog type: error
*** Dialog message:
Fatal error!
PgcEdit is trying to read data after the
end of a table.
This means that a Length Of Table value
is probably wrong. (See log.)
Please try to fix the problem with IfoEdit.
The missing value may be fixed to 0, but
this could lead to strange results.
Do you want to fix the value and continue
anyway? (NOT RECOMMENDED!)
*** Dialog buttons: [Yes] [No]
If I click on No,I have an error message :error attempt reading... I can ignore it?
Thanks for your advice.

[r0lZ]

Hum, difficult to understand what's happening. According to the error message, the PGC you've tried to kill is a dummy.
Please read your PMs.

[vwpassion]

Is there any reason why you can't chose SPRM 0 from the trace mode -> breakpoints -> "SPRM write breakpoints" menu?

[r0lZ]

No! I can select it here. Could you give more info? Why can't you chose it? Is it disabled?

Could you also try to enable the breakpoint via Info -> GPRMs (click on the GPRM number) and via the trace Watch window (again, click on the GPRM number)?

[vwpassion]

No! I can select it here. Could you give more info? Why can't you chose it? Is it disabled?

Could you also try to enable the breakpoint via Info -> GPRMs (click on the GPRM number) and via the trace Watch window (again, click on the GPRM number)?

It just doesn't appear in the menu.

http://i.lulz.at/m5Zq468.jpg

Click here (http://i.lulz.at/o5Ny658.jpg) for another screenshot.

[r0lZ]

Hoops, sorry, I haven't read your message carefully enough. I thought you were speaking of GPRM 0.

SPRM 0 (the preferred menu language) is not available, simply because it cannot be written by a VM command. The only way to modify its value is by using the player configuration menu. Therefore, it doesn't make sense to watch it. (Same thing for SPRMs 12, 13 and 15 to 23.)

However, note that you can actually enable the watch function for those read-only SPRMs by clicking on the SPRM number in the Watch or Info->SPRMs windows, but of course, it's useless.

[vwpassion]

I see. Sometimes I modify sprm(0) commands, especially on Sony Region 2 dvds, when I remove foreign menus. Sony usually masters their dvds to call the player's preferred menu language and thus I modify these commands and set them to something like this:

Original: Set gprm(0) =(mov) sprm(0:Preferred menu language)

Modified: Set gprm(0) =(mov) 25966 ("en")

This way it doesnt matter anymore which menu language is set within the player. So for me, it'd be quite useful. But I'll stick to Info -> SPRMs instead.

[ron spencer]

thanks for V9.1....great job

[spare]

Could Someone cook up an icon for the PgcEdit homepage ??
It would make it easier to spot on my bookmarks :)

Thank You.

[Wombler]

Actually that's not a bad idea.

r0lZ, how about it?


Wombler

9203

[blutach]

Thanks r0lZ and also big thanks to M_Knox. It is soooooo easy to understand those bitwise operations now.

Regards

[blutach]

I see. Sometimes I modify sprm(0) commands, especially on Sony Region 2 dvds, when I remove foreign menus. Sony usually masters their dvds to call the player's preferred menu language and thus I modify these commands and set them to something like this:

Original: Set gprm(0) =(mov) sprm(0:Preferred menu language)

Modified: Set gprm(0) =(mov) 25966 ("en")

This way it doesnt matter anymore which menu language is set within the player. So for me, it'd be quite useful. But I'll stick to Info -> SPRMs instead.Do a search for the word preferred in the search box. That way you will hit all the required registers (0, 16, 18). Then use the search and replace plugin. It is very easy. See attached for changing eveything to English. This goes in your search_replace_presets folder in %appdata%/PgcEdit

Regards

[vwpassion]

Do a search for the word preferred in the search box. That way you will hit all the required registers (0, 16, 18). Then use the search and replace plugin. It is very easy. See attached for changing eveything to English. This goes in your search_replace_presets folder in %appdata%/PgcEdit

Regards

Oh, didnt know about presets. Thanks. :)

[r0lZ]

Could Someone cook up an icon for the PgcEdit homepage ??
It would make it easier to spot on my bookmarks :)The mirror in belgium (http://home.tele2allin.be/vt6328799/pgcedit/index.html) has an icon. The main homepage at VideoHelp (http://download.videohelp.com/r0lZ/pgcedit/index.html) doesn't display it, I don't know why. I will have a look...

[Wombler]

Ahh... I didn't realise that.

I've always used the main page and had noticed the lack of an icon before spare mentioned it.

But if there's some insurmountable technical problem then the simple answer for spare would be to use the Belgian mirror.


Wombler

[r0lZ]

The icon file was simply missing! The technical problem was therefore not totally insurmountable! ;)

[Wombler]

Excellent!

If only everything else was that easy. :)


Wombler

[r0lZ]

Also , tried to delete a sub-menu (straight from the rip) and got an error message (cf log: the DVD has ILVU: probably irrelevant).
The error message invites me to fix it with IFOEdit (I'd rather not delete the sub-menu) but should I still go to IFOEdit even without deleting the sub-menu (bad rip or whatever).
MsgBox "PgcEdit: Kill PGC Playback" -> yes

ERROR! get_int: Attempt to read 2 bytes at offset 0 (0x0) after end of table!
Variable: cellpostable, length of table: 0
MsgBox "PgcEdit fatal error" -> no
*** Dialog title: "PgcEdit fatal error"
*** Dialog type: error
*** Dialog message:
Fatal error!
PgcEdit is trying to read data after the
end of a table.
This means that a Length Of Table value
is probably wrong. (See log.)
Please try to fix the problem with IfoEdit.
The missing value may be fixed to 0, but
this could lead to strange results.
Do you want to fix the value and continue
anyway? (NOT RECOMMENDED!)
*** Dialog buttons: [Yes] [No]
If I click on No,I have an error message :error attempt reading... I can ignore it?
Thanks for your advice.

I wanted to delete the sub-menu (with subtitles) of the version with alternate ending.

Trace;Run;Click on Button2;Select;Click on "Kill PGC Playback";
Click on the button "Kill Playback" with the button "English " selected.
{71 01 00 08 00 01 00 0D}

I did the same thing on a non-ILVU DVD and got a similar error.
Hope I did not screw the IFO and menubuttons.
The first one is after loading, and the second is after saving after the error message.

I see! After some tries, I've finally been able to reproduce the bug.

It is caused by the fact that you Kill Playback of the menu when the menu viewer (automatically opened by the trace) is still open. If you close it (for example by selecting Close And Break Trace), and then you kill the menu, the problem does not occur.

In fact, it should be impossible to modify the DVD when trace mode is active. It doesn't make sense to trace something that is constantly modified. However, I have not disabled the main GUI when the trace mode is active, because in some cases, it is possible to modify some commands while the DVD is tracing. That's useful, for example, to test what happens when a command is modified to jump elsewhere or change a GPRM value without having to restart the trace from the beginning. However, there are things that cannot be made in trace mode, as if the structure of the current PGC or domain is modified, the trace will not be able to continue.

In this particular case, you trace to the menu you want to kill, and PgcEdit displays it in the menu viewer, and waits for your selection. At that time, you kill the menu. This has the effect of automatically closing the original menu viewer window and opening another menu viewer to let you select the button to use for the kill. Then, you do the kill... and the trace tries to continue. Of course, it cannot find the buttons any more, since they have just been deleted, and the error occurs.

Of course, this case should be trapped. I should either refuse to apply Kill PGC Playback when the menu viewer is already opened, or stop the trace when Kill PGC Playback is applied. I will see what I can do. In the meantime, do not use Kill PGC Playback when the menu viewer is opened, and everything will be perfect.

Since I don't have your DVD, I can't verify if the error has caused some problems in your IFOs, but I don't think so. IMO, Kill PGC Playback has made its job well. The error was produced when the trace has continued. Since the trace doesn't modify the DVD (except if you use Blank This Cell/PGC from the preview in trace mode), the error should be harmless.

[r0lZ]

OK, now, if you try to kill playback of a PGC when the menu viewer is opened and trace mode is enabled, a warning is displayed, and you have to close the viewer and relaunch the function.

Note that I have added the same security check as well on several other functions, such as Blank OutAll PGCs Of Domain or Remove LU.

Anyway, remember that it is never safe to modify the structure of the DVD when trace mode is running. (When the menu viewer has been opened automatically by the trace, and even if you are currently in "Step" mode, the trace is running, as it waits for your input, and will at least continue by executing a button command.)

[mikenadia]

Anyway, remember that it is never safe to modify the structure of the DVD when trace mode is running.
Does this mean that during the Standard " Jump to PGC upon insert" procedure, I should get out of Trace mode just before clicking on "Jump to PGC upon insert".
And If I do that, when I get out of trace mode, I am sometimes going at the first post-command of the PGC (even if there are pre-commands ) instead of staying at the first pre-command (seems to happen when the "PGC upon insert" is a second level menu). I should manually go back to the first pre-command and then click on "Jump to PGC upon insert. Right ?

Thank you very much.

[r0lZ]

No! I said "when trace mode is running". When you are in trace mode but you have stopped it, no problem! (In some cases, even that is not safe, but PgcEdit closes the trace mode automatically for you. It's the case, for example, if you try to remap the titlesets.)

But as I have tried to explain above, when the trace has opened the menu viewer and you haven't replied to it yet, then trace mode is currently running, even if you are in step by step mode. In fact, the trace is in the middle of a step, and waits. You should therefore avoid to call a function before having replied to the menu viewer and stopped the trace.

[selyb]

I keep PGCEdit in Trace Mode always I wish trace mode wouldn't turn off when I delete unreferenced pgcs.

Maybe I'm a little ignorant on this but I think the end user should expect problems when he/she edits commands while trace mode is running

[blutach]

I wish trace mode wouldn't turn off when I delete unreferenced pgcs.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

[r0lZ]

As I said above, the trace mode should normally be closed before doing any modification to the DVD (including simple command edits) but I have left this possibility open for the power users that know what they are doing. However, I have to reset completely the trace mode when the structure of the DVD changes in such a way that trying to continue the trace or restart it from a snapshot is not possible. (This was a cause of several bugs in the previous versions.) I have to clear all trace data, and for me, it is easier to close the trace. When it is re-opened, it is reinitialized from scratch, and everything should work fine.

[blutach]

@r0lZ - just an idea ....

Is there a way to keep trace open and "automatically" press the open/close tray button instead?

Regards

[r0lZ]

No, sorry but I have had many difficulties with the option to open the trace automatically at startup. This is more complex that it sounds, and has been the source of several bugs. I should have removed this option! Anyway, I'm not going to change that again, to make it even more complex. Click on the button, or use the hotkey. It's not that difficult.

[vwpassion]

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]

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]

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]

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]

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]

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]

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]

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]

It's unlikely the sources will ever be released as this will almost ensure that donations stop.

Regards

[r0lZ]

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]

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]

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]

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]

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]

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]

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]

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]

Oops, I forgot to update the version number on the site. Fixed. Thanks!

[selyb]

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]

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]

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]

Gladly donated for this stellar program. :)

[r0lZ]

Thanks!

[mikenadia]

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]

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]

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]

That's right, and it's a good trick!

[david42]

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]

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]

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]

Perhaps there was a "Next PGCN link" in the PGC you killed the playback of.

[mikenadia]

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]

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]

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]

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]

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]

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]

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]

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]

How can someone who lives in the U.S. and does not have any online accounts like paypal donate?

[r0lZ]

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]

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]

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]

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]

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]

Forget my previous post, vwpassion! There is indeed a bug in PgcEdit. I've found and fixed it.
Thanks for your bug report!

[vwpassion]

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]

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]

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]

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.

[r0lZ]

No, it is not safe to delete the uncalled PGCs in the VMGM or in the VTS containing the multiple button sets (MBS), because if a command in a MBS calls a PGC in the VMGM, it cannot of course be deleted. For the same reason, the subsequent PGCs cannot be renumbered neither. So, even if you are sure that a PGC is really uncalled, it is not safe to delete it manually (unless it is at the end of the LU.)

However, when PgcEdit scans the VOB files for the menu buttons (and if the "check for multiple sets of BOVs" option is ticked), it verifies if some new commands are created in the new button sets, and when it's not the case, it can sometimes remove the uncalled VMGM PGCs. However, the PGCs that are called from the MBS cannot be renumbered, as currently PgcEdit cannot save the button commands without overwriting the MBS. That means that only the PGCs following the PGCs pointed to by the commands in the MBS can be removed.

Anyway, it is better to leave PgcEdit remove the uncalled PGCs, and if some of them cannot be automatically removed, you can blank them manually.

[mikenadia]

Thank you for your explanation.
I have a MBS. If I do "delete uncalled PGCs", I have a warning that it is unsafe and I can cancel. If I run " remove useless stuff", they are deleted automatically (without ability to cancel) and there is a message at the bottom-left " Waiting to delete unsafely uncalled PGCs" and a lot of them are deleted in the VMGM.
Just wanted to know if I should untick or not " Delete uncalled PGCs" in the " remove useless stuff" procedure when there is a MBS because " remove useless stuff" assumes that I know what I am doing and that I want to delete "unsafely" those PGCs.

Thanks.

[blutach]

Check Info --> Multiple Sets of Buttons/BOVs to see what new commands are added. If none are added in VMGM, then it's safe to delete these.

By looking at this, you might find a new PGC referenced, which seemingly was uncalled before. If you want to run Delete Uncalleds or the like and ignore the warnings safely, use a little trick to reference them in the first place.

1. Find the new PGCs that the multiple button sets reference.

2. In a PGC in that domain somewhere, add new commands such as Link PGCN xxx. Make sure these new commands can never be executed! That is, place them after an unconditional link in a PGC somewhere, so they can not ever be executed.

For example - an MBS links to a (previously unvisited) PGC 25. In the root menu, there is a call to VMG. Add a few NOPs and then add Link PGCN 25. Then run the Delete Uncalled PGCs/Remove Useless function (now PGC 25 is referenced and will not be deleted). Afterwards, if you really want, you can delete your new commands.

Regards

[fordman]

I have found two bugs, at least on my system, which PGCEdit 8.6 did not have, as follows:

1. I use PGCEdit to investiage possible layer break points. I noticed that the functionality and buttom labeling has changed somewhat in the 9.X versions. However, the issue is that when I choose to view a cell that I have highlighted, the viewer pops up and starts playing the previous cell. I must press the next cell button to get the correct cell to play.

2. The "Jump to PGC upon insert" function is broken for me now. As I did in 8.6 and earlier versions, I set the "pre/post breakpoint" and then choose this function from the menu, and my system simply "beeps" and does nothing. Meanwhile, if I open 8.6 from the directory where I saved it before installing 9.1, it works just fine. So for now, my workaround is to do most of my work in 9.1, but if I want to use this function I exit and reopen in 8.6.

Well those are the things I have found with PGCEdit 9.1...

fordman

[blutach]

Hi fordman and welcome.

As to the first issue, it actually previews both the cell before the selected cell and the selected cell. The first cell is played for a few seconds and then it goes to the 2nd one (with a little pause to indicate the break) - this to enable you to see the transition better. However, you might like to use ImgBurn directly, as this function is built into ImgBurn and I know that r0lZ is no longer updating the burn function in PgcEdit.

I can't say much about your 2nd issue - perhaps you need to delete your configs and try again as there may be some conflict between v8.6 and v9 config files.

Regards

[fordman]

Hi fordman and welcome.

As to the first issue, it actually previews both the cell before the selected cell and the selected cell. The first cell is played for a few seconds and then it goes to the 2nd one (with a little pause to indicate the break) - this to enable you to see the transition better. However, you might like to use ImgBurn directly, as this function is built into ImgBurn and I know that r0lZ is no longer updating the burn function in PgcEdit.

Hi. Thanks for the quick response! I assume you are saying that this is the intended behavior, which is different than it was in 8.6. In 8.6 it played (for me anyway) immediately after the layer break position. I must admit that I used to back it up to see the transition, so perhaps it was decided that this should be the default action?

I do in fact use ImgBurn to burn and make the final selection for the layer break. However, since I use PGCEdit to clean up the structure before using ImgBurn, I always preview and set the layer break (non-seamless) flag it it first. USUALLY the two progams agree on the sector number where it will occur.

I can't say much about your 2nd issue - perhaps you need to delete your configs and try again as there may be some conflict between v8.6 and v9 config files.


This would be strange if there was a conflict, as I've always done a simple upgrade in the past by simply installing the new executable over the old one, and then it makes new versions of the support programs, if appropriate, in the bin directory. Did something change with version 9.X with the upgrade procedure?

In the chance there is a conflict, where are the configurations kept? I assume in the registry, as I don't see any .ini files in the PGCEdit directory. I looked in the usual registry locations and didn't see anything under PGCEdit, r0lZ or anything similar...

Regards,
fordman

[blutach]

No, not in the registry. In your %appdata%/PgcEdit folder. They are .cfg files

For your LB issues, just tick the seamless joint flag in PgcEdit and then proceed in ImgBurn. And yes, it is intended behaviour. It's a feature!

Regards

[r0lZ]

Hi fordman.

I confirm that the new "Preview LB" button in the Burn DVD dialog shows you the final part of the previous cell, a pause, and then the current cell, with the audio. That way, you can really see and hear what you will get on a real player when the layer break is not seamless.

I cannot reproduce the problem with Jump2PGC. Usually, a function beeps when there is no DVD loaded in PgcEdit, or if you have selected a PGC that cannot be used by that function. Can you describe what you are doing with more precision? What type of PGC do you select (menu or title, VMGM or VTSM, dummy or not...)? How do you trace to it? Does the problem occurs always, or only in some specific cases?

Anyway, try to download PgcEdit again. Sometimes, a bad download can lead to bizarre bugs like this one.
Renaming your %appdata%\PgcEdit folder and trying again with a fresh configuration might be useful too, as blutach suggested.

[fordman]

Hi fordman.

I confirm that the new "Preview LB" button in the Burn DVD dialog shows you the final part of the previous cell, a pause, and then the current cell, with the audio. That way, you can really see and hear what you will get on a real player when the layer break is not seamless.

OK, good to know. It will take a bit to get used to, but I see the utility given that I used to "rewind" manually to do the same thing.

I cannot reproduce the problem with Jump2PGC. Usually, a function beeps when there is no DVD loaded in PgcEdit, or if you have selected a PGC that cannot be used by that function. Can you describe what you are doing with more precision? What type of PGC do you select (menu or title, VMGM or VTSM, dummy or not...)? How do you trace to it? Does the problem occurs always, or only in some specific cases?

I've been using the Jump2PGC function ever since you added it to PGCEdit, or at least when I discovered it....more than a year at least.

1. I right click on the Root menu (VTSM 1), for example and choose "Toggle PGC Pre/Post breakpoint," and it highlights it in red.

2. I move the selection to VMG, First-Play PGC (probably not necessary) and then select "Jump to PGC upon DVD insert" from the PGC menu. My computer beeps and does nothing. It used to trigger trace mode and I would press the run button and when the breakpoint was reached, I would choose the Jump2PGC function again, and PGCEdit would do its magic.

As I said, I know it's not anything I'm doing wrong or different, as version 8.6 works fine, and that is how I ended up doing this. I also re-installed 9.0 and it works, and I see that you've added more options and warnings to the Jump2PGC function! I even tried running it as an admin and that made no difference with 9.1. With the previous versions, I could run in user mode just fine, anyway.

In summary, 9.0 and earlier work fine for me, but 9.1 broke the Jump2PGC function. If you have any debugging you'd like me to do, let me know. I'm using Windows Vista basic on an Acer laptop with a Core2Duo T7100 processor and 2 GB of RAM. I normally run in user-only mode and only use my admin account for installing/upgrading programs.

Anyway, try to download PgcEdit again. Sometimes, a bad download can lead to bizarre bugs like this one.
Renaming your %appdata%\PgcEdit folder and trying again with a fresh configuration might be useful too, as blutach suggested.

I did both of these things (re-download and re-install 9.1 and allowed a new config folder to be made), and the results were the same - BEEP then nothing when using Jump2PGC function. Ideas?

Thanks,
Fordman

[blutach]

2. I move the selection to VMG, First-Play PGC (probably not necessary) and then select "Jump to PGC upon DVD insert" from the PGC menu
In step 2, you are not running the trace. Every DVD already jumps to FP-PGC on insert.

Step 2 should be: Click on load/eject and run trace. It will stop on your breakpoint, where you should call the function. Please see the guide (http://www.digital-digest.com/~blutach/Jump2PGC/Jump2PGC_guide.html) on the PgcEdit site.

Regards

[fordman]

In step 2, you are not running the trace. Every DVD already jumps to FP-PGC on insert.

Step 2 should be: Click on load/eject and run trace. It will stop on your breakpoint, where you should call the function. Please see the guide (http://www.digital-digest.com/~blutach/Jump2PGC/Jump2PGC_guide.html) on the PgcEdit site.

Regards

I think I clouded the issue. I realize the trace is not running yet when I position the selection bar on the FP-PGC, and I realize that there is no reason to set a break point there (I set it at the root menu). I simply have gotten in a habit of doing that before invoking Jump2PGC for the first time. It has never been necessary for me to manually enter the trace mode before first invoking the Jump2PGC function as long as I know where I want to place the breakpoint. PGCEdit automatically launches trace mode. Your tutorial shows entering the trace mode first so you can help determine where to place the break point. I already knew where to place it and therefore didn't need to trace first. However, before I even first reported the issue, I DID try entering trace mode first, and it still just beeped... Performing the exact same steps with 9.0 or 8.6 works as expected.

Thanks for the suggestion. I'll probably drop back to 8.6 or wait until 9.2 comes out.

fordman

[blutach]

I realise that you knew which PC you wanted to go to and put a pre-post breakpoint on it. Step 1 is all fine.

All you should need to do now is start trace (Ctrl-T), press run, wait till it stops on your breakpoint and call the function. Does that not work?

Regards

[r0lZ]

Yes, blu is right. It doesn't make sense to launch the Jump2PGC function on the FP-PGC. You have to trace to your breakpoint before launching it.

I agree that something has changed in v9.1, but Jump2PGC is not broken. I've modified it, because it was possible to launch and execute the function when the trace was waiting for the user input in the menu viewer, and that was a big problem. At the same time, I've added some basic checks on the validity of the current PGC. The check for the FP-PGC is made immediately when the function starts, and that's the change you've noticed. Due to this new check, PgcEdit does not offer to go to trace mode anymore (when it's not the case already), and doesn't display the explanation on how to use the function, but just ring the bell. Maybe I have to change that again, but if you know the function, you should understand that it is useless to apply it to the FP-PGC.

[EDIT] OK, I've moved the check for the FP-PGC later in the function, and now, if you launch Jump2PGC with the FP-PGC selected, PgcEdit displays the explanation on how to use the function, with a new red warning "It doesn't make sense to jump to the FP-PGC!", then it starts the trace mode for you.

It is still not possible to launch the function when no DVD has been loaded, or when PgcEdit is in scratchbook mode.

[fordman]

Yes, blu is right. It doesn't make sense to launch the Jump2PGC function on the FP-PGC. You have to trace to your breakpoint before launching it.

I agree that something has changed in v9.1, but Jump2PGC is not broken. I've modified it, because it was possible to launch and execute the function when the trace was waiting for the user input in the menu viewer, and that was a big problem. At the same time, I've added some basic checks on the validity of the current PGC. The check for the FP-PGC is made immediately when the function starts, and that's the change you've noticed. Due to this new check, PgcEdit does not offer to go to trace mode anymore (when it's not the case already), and doesn't display the explanation on how to use the function, but just ring the bell. Maybe I have to change that again, but if you know the function, you should understand that it is useless to apply it to the FP-PGC.

[EDIT] OK, I've moved the check for the FP-PGC later in the function, and now, if you launch Jump2PGC with the FP-PGC selected, PgcEdit displays the explanation on how to use the function, with a new red warning "It doesn't make sense to jump to the FP-PGC!", then it starts the trace mode for you.

It is still not possible to launch the function when no DVD has been loaded, or when PgcEdit is in scratchbook mode.

r0lZ, thanks for confirming that there was indeed a change made in 9.1 that affected the functionality of Jump2PGC. For awhile there I thought something else had broken on my computer! Yes, as I told blutach, I realize there is not sense jumping to FP-PGC as it is done first already. However, my habit if just re-positioning the cursor there before running the function and my reliance on PGCEdit to throw me into trace mode after the tutorial dialog came undone with your changes to the function in 9.1. As I told blutach, I had tried entering trace mode manually before invoking the Jump2PGC function, but I still had the cursor positioned on the FP-PGC out of habit. I had assumed the position of the cursor didn't matter, at least in prior versions because PGCEdit resets the registers and navigates to the pre/post breakpoint that I had already set. Those versions didn't require that I also highlight that same menu/title where the breakpoint was. I guess you could say that it was "idiot proof," which was great for idiots like me! :D

Thanks for restoring some of the idiot proof logic!

fordman

[fordman]

I realise that you knew which PC you wanted to go to and put a pre-post breakpoint on it. Step 1 is all fine.

All you should need to do now is start trace (Ctrl-T), press run, wait till it stops on your breakpoint and call the function. Does that not work?

Regards

Hi blutach,

Apparently it would, now that I understand from r0lZ's later message what changes were made in 9.1. I'm not at home to try it, but from his explanation, I see that as of 9.1 I cannot rely on PGCEdit to display the tutorial dialog and start trace mode for me. Then there was the problem that it was changed in 9.1 to just beep if FP-PGC was highlighted. Now that I understand, I can modify my habits to make it work.

Thanks again,
fordman

[r0lZ]

You don't need to modify your habits, as I'll release v9.2 soon...

[Wombler]

Thanks for restoring some of the idiot proof logic!


This stuff can be complicated enough as it is, so it's important that 'idiot proof logic' features throughout the program and r0lZ pursues this whenever possible.

It's key to making PgcEdit easier to use and IMHO is the reason that users have such faith in this excellent program.


Wombler

[mikenadia]

Straight from the rip, I have two uncalled PGCs(see image).

[img=http://img510.imageshack.us/img510/2317/uncalledlr2.th.jpg] (http://img510.imageshack.us/my.php?image=uncalledlr2.jpg)

If I do "Delete uncalled PGCs" then " Jump to PGC upon insert" and then " Delete uncalled PGCs", everything is fine.
If I do " Jump to PGC upon insert" and then " Delete uncalled PGCs", I have too many (some that are blanking some wanted PGCs).
May be due to the fact that one of the uncalled PGC (straight from the rip) is a RootM.

Thanks in advance.

[blutach]

Do a Ctrl-G (Go to calling command) on the root menu and find out what it says (it may say "NOT callable with the remote due to PUOps and the fact that no title is called"). Check out PUOs on the menu PGCs. They may all have a Menu call - Root menu (UOp 11) set. If this is the case, the root menu is never called!

Regards

[r0lZ]

I have not enough information. What are those "too many"?

Of course, when you use Jump2PGC, it can happen that some PGCs become uncalled. This can be the case if the FP-PGC is never called (except, of course, when inserting the DVD.) In that case, Jump2PGC removes completely the original jump command from the FP-PGC, as it is useless, and the PGC that were called from that original jump can become uncalled.

[mikenadia]

blu, you are right. The Root menu is never called .

rOlZ, when I say "too many" it is because I am deleting two additional TTN with duration of 3mn each in the 2nd procedure and in both procedures, I am doing "Jump to PGC upon insert" (that is why I assumed "wrongfully" that the two procedures should end up with identical results).

Thanks.

Edit: When two PGCs use the same video blocks, should " Killing Playback" of one " kill playback" of the other one?
In the "ID Provider" window, I cannot use the "Edit-Copy" (is there a conceptual reason from preventing it?).
Thx.

[zyzyx]

I have a possible new feature for you. Although I don't know exactly what is happening to cause my problem. I am creating an instructional DVD and have multiple chapters with BOV's in each. PGCEdit does not see a problem with anything that I have done. (created w/scenarist) But when I play the dvd on any player, one of the chapters executes the pre comands then the resident 10 sec. video but then hangs. The cell command never gets reached. I don't know what is causing this but it sure is anoying!! You have done such great work with this program, I thought this might give you an idea for a new authoring error featureto help dummies like myself.

[r0lZ]

Unfortunately, I can't help you. PgcEdit is an IFO editor, not a verifier, and especially not a VOB verifier. The problem is probably related to the original video or audio stream, or to the muxing. PgcEdit doesn't know what happens when a cell is playing. It can modify (and, in some cases, verify) what happens before and after its playback, but that's all. Sorry.

Try to describe your problem in the Advanced Authoring forum, where, I hope, someone will be able to help you.

[blutach]

If the cell has a BOV, maybe it is showing (check cell still time). And if you can't see the BOV highlight, check the subpics are there and show correctly with DVD Sub Edit. You might also check the colour schemes are what you want - you may have set the highlights to invisible somehow.

Regards

[Cela]

I have read that Vista is silly, and I can confirm that. But, unfortunately, my new multimedia PC comes with Vista. Now I have troubles with "Preview current PGC" in PgcEdit 8.6:
The Preview Window launches, but remains black. When I press "play" the screen remains black but the Absolute Sector value starts running up. If I press "BMP" the black screen changes to the current frame.
Same problem with new "nag" Version 9.2. Here I can switch on sound preview and I can hear the sound to the black screen!
In both versions preview shows the expected contents if it is a still frame. It does not like moving pictures. :(

Thus, I guess there is some trouble with displaying the video. My PC uses a NVIDIA GeForce 9500 GS, and all players including MplayerC, PowerDVD, Nero Show Time, DVBViewer, etc, play the same VIDEO_TS nicely.

Please help.

Regards,

Cela

[r0lZ]

Have you tried the Preview -> Disable DirectDraw Overlays option?

[mikenadia]

Thanks for the update.
Cosmetics. in 1 rip out of 3, if I click with the mouse on " Trace-Trace mode" (top menu bar), then run the "Jump to PGC upon insert" procedure and then click with the mouse on " Trace-Trace mode" to stop trace mode, I have an error message such as:
can't read "::buttons::butsinfo(menu,1,1,1,1,1,command)": no such element in array
If I do the same procedure but going into Trace mode by clicking on the icon "Toggle Trace mode" , rightfully or not, I never have any error message.
Thanks.

[Cela]

Have you tried the Preview -> Disable DirectDraw Overlays option?That makes the difference!
Thank you very much! :)

I apologize for accusing Vista. ;)

Regards

Cela

[r0lZ]

Cela, Vista might be the culprit! It uses different DirectDraw video modes than XP. When the option is set, the preview skips a big part of the DirectDraw processing, and does the resize of the image with its own code. The result is not so clean (especially with interlaced video), but at least you can see the image!

[r0lZ]

Cosmetics. in 1 rip out of 3, if I click with the mouse on " Trace-Trace mode" (top menu bar), then run the "Jump to PGC upon insert" procedure and then click with the mouse on " Trace-Trace mode" to stop trace mode, I have an error message such as:
can't read "::buttons::butsinfo(menu,1,1,1,1,1,command)": no such element in array
If I do the same procedure but going into Trace mode by clicking on the icon "Toggle Trace mode" , rightfully or not, I never have any error message.I can't reproduce the bug. Can you post the whole error message? (click the Details button to see it.)
Also, please explain what you are doing exactly. After the Jump2PGC function has finished its work, do you launch the trace again? Or do you close trace mode immediately, when the current PGC is the FP-PGC?

Note that the fact that the error message is not shown when the trace is started from the toolbar is normal. For an unknown reason, the internal error messages are not shown when the toolbar is used to launch a function producing a bug. But, unfortunately, that doesn't mean that the bug doesn't happen!

[mikenadia]

can't read "::buttons::butsinfo(menu,1,1,1,1,1,command)": no such element in array
can't read "::buttons::butsinfo(menu,1,1,1,1,1,command)": no such element in array
while executing
"set cmd $::buttons::butsinfo(menu,$cur_vts,$cur_vobid,$cur_cellid,$::buttons::groupnum,$but,command)"
(procedure "simulate_play" line 341)
invoked from within
"simulate_play"
(procedure "step" line 10)
invoked from within
"step"
(procedure "reset_trace" line 159)
invoked from within
"reset_trace"
(procedure "::tr::dvd_trace" line 400)
invoked from within
"::tr::dvd_trace"
(menu invoke)

What I am doing (it happens on 1 DVD out of 3, not always).
1) with the mouse, click on " Trace-Tracemode" (File-Edit-Trace...).
2) the Trace window opens (bottom-left portion of the screen), I click on the button Run.
3) when I reach the first menu, I click (always using the mouse) on " Breakpoints- Toggle pre-post breakpoints in the Trace window.
4) I click on the Load-Eject button in the trace window.
5) I click on the button Run in the Trace windows.
6) When the Trace reaches the PGC that I want upon insert, I click on "PGC-Jump to PGC upon insert " (File- Edit-Trace....PGC...: menu list on top of the screen).
7) When the "Jump to PGC upon insert" is finished, with the mouse, click on " Trace-Tracemode" (File-Edit-Trace...) to stop the Trace ( I have the same error message if I stop the trace by closing the Trace window (bottom-left of the screen).
after step 7, I am getting sometimes the above-mentionned message.

After the Jump2PGC function has finished its work, I do not launch the trace again.I close trace mode immediately, when the current PGC is the FP-PGC.

P.S. If I just change step 1 and start the Trace mode by clicking on the icon " Toogle Trace mode", I do not get any error message.

Thanks in advance.

[r0lZ]

Are you sure you use v9.2? I've fixed recently a similar problem.

And, during step 4, is the menu viewer window opened, or do you close it manually before step 3 or 4?

[mikenadia]

v 9.2
The menu viewer is still opened ( I do not close it manually).
I am not doing anything but those 7 steps (may be I should!)
Thanks in advance.

Edit: for v 9.2 questions, do you want us to keep on in this thread or in the "sticky".

[r0lZ]

Well, initially, I've added the "v9.2 released" message in this thread, but a moderator (blutach, I guess) has split it, so, yes, it is better to post in the new sticky. However, since this bug is not specific to v9.2, we can continue this precise discussion here.

The menu viewer is still opened ( I do not close it manually).That's certainly the cause of the problem, but I don't understand why it happens again. I've fixed it! :devil:

[mikenadia]

Thank you very much.
Can I still use the 7-step procedure or should I add " Close Menu viewer" and if yes after which step?

Another issue ( happens in v 9.1 and 9.2)
in one DVD, using the same 7-step procedure, I am not going back to the PGC upon insert that I want (step 2 and 5 do not bring me to the same PGC).
I have a " if statement" based on the value of gprm(6).

step 2:
DVD inserted: Resetting all GPRMs to 0.
DVD inserted: Initializing the SPRMs to default/setup values.
------> Entering VMG , First-Play PGC
-- pre 1 : Set gprm(6) %=(mod) 2
-> gprm(6) = 0 (0x0000)
-- pre 2 : Set gprm(6) ?=(rnd) 2
-> gprm(6) = 1 (0x0001)

step 5:DVD inserted: Resetting all GPRMs to 0.
DVD inserted: Initializing the SPRMs to default/setup values.
------> Entering VMG , First-Play PGC
-- pre 1 : Set gprm(6) %=(mod) 2
-> gprm(6) = 0 (0x0000)
-- pre 2 : Set gprm(6) ?=(rnd) 2
-> gprm(6) = 2 (0x0002)

gprm(6) has two different values. I think they should be identical.
The issue (if there is one) is caused by clicking on " Breakpoints- Toggle PGC pre-post breakpoint" in the Trace window (bottom-left on the screen). May be it changes the way gprm(6) is defined (integer...). No clue why it leads to 2 different results in pre 2: (all GPRMs are reset to 0 in both steps).

Thanks in advance.

[r0lZ]

Set gprm(6) ?=(rnd) 2 sets a random value between 0 and 2 in GPRM 6, so, it is perfectly normal that the content of the GPRM differs when that command is executed by the trace. Of course, if you Jump2PGC and that command is bypassed, you will always have the same value in GPRM 6.
You can perhaps change the command that is pasted by PgcEdit to initialize GPRM 6 to the random value again. If that value is used after your target point, that should work.
Also, if you want to be sure to always go to the same PGC, you should replace the original command by Set gprm(6) =(mov) 0 (or 1 or 2).

[blutach]

And what's the use of precommand 1, if immediately afterwards, pre 2 resets the register? You can eliminate it.

Regards

[mikenadia]

Those two commands were part of the original FP-PGC and because of the random ( not round) command did not allow me to use (only randomly) the " Jump to PGC " macro.
I just deleted the random command, run the "Jump to PGC " macro and put back the random command and the correponding "if statement".
Navigations seems to work, so...(still looking if that " randomness" has a purpose or not).

I think those "non-determinstic" commands are rare, but may be worth an optional warning in " Jump to PGC" macro ( I know I can use the "Search " function: BTW, any other non-deterministic functions I should be aware of ?).
Thanks to both of you.

[Dgn-Master]

Hello, i think your program is awesome; that could be why i bought it.

I would like to see one addition added to the burn dialog box if possible in the future.

Under the volume label Imgburn has the ability to make upper, lower, and capitalize case as options for name creation (i know this is very minor). But as there is also no ability to just paste a name into the field i would appreciate it if you could see yourself clear to adding this.

Thanks

[r0lZ]

Welcome to the forum, Dgn-Master!

Well, PgcEdit uses mkisofs to build the ISO, and afaik mkisofs supports only the ISO9660 label, that must be in upper case. I can't change that.

But note that you can launch ImgBurn directly from the Tools menu of PgcEdit, without having to create the ISO with PgcEdit's burn function first. ImgBurn can build the VIDEO_TS folder directly to disc.

You can pass the label to ImgBurn if you wish, but it's not really necessary, as ImgBurn uses a similar method to compute a default label.

Here is my configuration of the Tools menu entry for ImgBurn:

Label: Build with ImgBurn
Application: C:\Program files\ImgBurn\ImgBurn.exe
Arguments: /MODE ISOBUILD /BUILDMODE DEVICE /FILESYSTEM "ISO9660 + UDF" /SRC "%d" /VOLUMELABEL "%l"
Working folder: %d
Save DVD and Run in background are ticked.

Note the /VOLUMELABEL "%l" argument. %l (lower case L) is used to pass the label computed by PgcEdit to ImgBurn. You can also use %L (upper case L) to pass the ISO label used by PgcEdit's burn function, but it's what you don't like! ;)

You can also add /IBG "C:\%l.ibg" to the arguments if you have DVDInfo, to automatically generate the IBG file.

You can use that tool to burn with ImgBurn. I do not update the PgcEdit Burn function any more, as imo it is now outdated. I still use it from time to time to see the disc space information from within PgcEdit, or to check the layer break position, but I haven't used it to create an ISO since ages!

[blutach]

To add to that - ImgBurn (www.imgburn.com) does not require you to make an ISO. It can burn from the project files directly.

Regards

[Dgn-Master]

Thanks for the very quick responses

Although i have tried just burning with imgburn directly from the files that pgcedit creates (with 32k space selected), i am unable to get a solid dual layer burn without a spike at the layer break (yes i do use DVDInfo pro to check the burn).

I am using Verbatim 8x and when i use mkisofs to create the image for burning i see no spike whatsoever.

I realize that imgburn uses a similar detect for a good layer break position however i still cannot get it to create as good an image as is done with mkisofs.

If i have overlooked something please let me know as i will have to continue to use mkisofs if i will continue to get spikes in my burns.

I also realize i am quite picky about my burns, but i want them to last a lifetime and although verbatims are the best, a bad burn may just mean the difference between 5 and 10 years.

[r0lZ]

It might be better to burn an ISO than the DVD-Video files, as the program doesn't have to jump to the beginning of the new files during the burn process. But the result should be identical if you create an ISO with ImgBurn first. There might be some differences in the way the DVD-Video files are processed by ImgBurn and by mkisofs, but that cannot explain a difference in the quality of the burn itself.

In my experience, I have always good burns when the files are on my D: drive, and less good ones when they are on C: (probably because my burner is on the same IDE interface than C: and because my D: SATA drive is faster.) Therefore, when I burn files from my C: drive, I do an ISO (with ImgBurn) on D:, and burn the ISO.

Anyway, if you like the PgcEdit method, you can of course continue to use it! :)
But you will have to live with the upper case labels. :(


BTW, the arguments I use to create an ISO with ImgBurn from the Tools menu are:/MODE BUILD /BUILDMODE IMAGEFILE /DEST "D:\%l.iso" /FILESYSTEM "ISO9660 + UDF" /SRC "%d" /VOLUMELABEL "%l" /CLOSESUCCESS

[blutach]

You are using MKM-003s (8x). ONLY use Verbatim, +R, 2.4x, MKM-001-00, Made in Singapore. The 001s are superior in quality as are the Singaporean discs (compared to ones made in India).

And in every DL disk, you will get increased PIEs on layer 1. It is par for the course. So, don't get paranoid about that.

Regards

[Dgn-Master]

Thanks again for all the replies, it seems that if i pass the arguments along to imgburn as you have suggested my layer break is now working.

First however i check to see where pcgedit would place the LB then use the same position in imgburn.

As far as only using Verbatims go i have found little difference in the quality between 2.4 and the 8X with my samsung SH203B (burnt at 10X), however, i learned my lesson long ago with some memorexes i bought at rock bottom prices.

Suffice it to say i would have had a better burn had i used the bottom of said rock.

And again :thanks:

[blutach]

First however i check to see where pcgedit would place the LB then use the same position in imgburn.
No, don't do this. ImgBurn has its own routines which may differ by a few sectors. If you are in build mode, don't try and 2nd guess ImgBurn. Just let it calculate the LB position.

As far as only using Verbatims go i have found little difference in the quality between 2.4 and the 8X with my samsung SH203B (burnt at 10X)Gee, you're gutsy for a guy who wants his DVDs to last forever. I burn my 2.4s at 4x. You're just inviting trouble at that speed and that's why you might see higher than normal PIEs on layer 1.

Regards

[r0lZ]

No, don't do this. ImgBurn has its own routines which may differ by a few sectors. If you are in build mode, don't try and 2nd guess ImgBurn. Just let it calculate the LB position.Blu, I'm not sure Dgn-Master forces the LBA determined by PgcEdit. If it's the case, you're right. But if he uses PgcEdit to determine which cell is the best one and then select the same cell in ImgBurn's GUI, that's OK!

[Dgn-Master]

No, don't do this. ImgBurn has its own routines which may differ by a few sectors. If you are in build mode, don't try and 2nd guess ImgBurn. Just let it calculate the LB position.

Blu, I'm not sure Dgn-Master forces the LBA determined by PgcEdit. If it's the case, you're right. But if he uses PgcEdit to determine which cell is the best one and then select the same cell in ImgBurn's GUI, that's OK!

I actually use it to determine a LB close to the one that Pgc says is optimal (cell) NOT forcing it.

Gee, you're gutsy for a guy who wants his DVDs to last forever. I burn my 2.4s at 4x. You're just inviting trouble at that speed and that's why you might see higher than normal PIEs on layer 1.

Regards

Wouldn't call myself gutsy quite the contrary as after using my drive i found over many, many tries (even with the layer break spike that is now fixed thanks to you guys) that the higher the burn speed the better the DVDinfo quality score. However, i do burn the 2.4's (at 4) when i find them on sale at Future Shop, it just so happens i got a great deal this time on the 8X and my drive does them at 10X. If i find in the future the quality drops i will revert to the 2.4X on future purchases.

As always :thanks:

[blutach]

Your choice dgn, but you might like to compare these threads. Have fun.

http://forum.imgburn.com/index.php?showtopic=2310
http://forum.imgburn.com/index.php?showtopic=2833

Regards

[Dgn-Master]

I will of course keep those scans in mind, and thanks again.

[turbojet]

Would it be possible to bring back the option to not find BOV's when a dvd is opened?

[r0lZ]

No, sorry. PgcEdit v9 needs the BOV information. But it can now save the buttons (and BOVs) information on your hard disc, and therefore it needs to scan the BOVs only once (and again if you modify the VOBs with an external tool.)

If you are really sure that a DVD has no BOVs, you can click the "Assume No BOVs" button when PgcEdit is scanning the VOBs. It will not try again.

You can also set it to scan every 30 VOBUs (the slider at its maximum value), and tick the "Deep scan" and "Check for multiple sets" options. With those values, the scanning is very fast. I use that config all the time, and I have never missed any BOV.

[turbojet]

Thanks for the tip it's pretty much instant now. Will this still find BOV's in very short pgc's that are basically menus like disney fast play or cbs main menu/previews menus?

[r0lZ]

Yes. The principle of the "scan every N VOBUs" is this: PgcEdit checks ALWAYS the first and last nav packs in each cell, plus a pack every N packs in animated cells. And if it finds one BOV in a domain and Deep Scan is enabled, it rescans every nav packs in the domain, to be sure to find all BOVs. (It's why the scanning of VOB files containing BOVs is still slow.) Therefore, with those options, PgcEdit will probably never miss any BOV, except perhaps when a domain has only one or two BOVs appearing during a very short moment in the middle of a cell, and PgcEdit is unlucky enough to just skip that part of the cells. There are very few chances for this to happen!

Note also that usually, all standard menu cells (including when the menus are authored as BOVs in a title domain), are beginning and/or ending by a nav pack with buttons. Therefore, the only case where PgcEdit could still miss a BOV is if there is a short BOV alone in the middle of a movie, for example to jump to an hidden bonus. And even in this case, there are many chances that the cells ends just after the BOV (as this is necessary to resume the movie at the right location after having played the bonus) and therefore PgcEdit should not miss it.

Don't worry! As I said, I have never missed any BOV, and I use always those settings.

[laserfan]

I made a backup of my "Dances with Wolves" DVD (interestingly the DVD was skipping on my players, and wouldn't read from my DVD-ROM drive in my PC but my BD-ROM drive was able to read it, so I could make a backup) but in testing-before-burning I note that one PC player shows the Subtitle 1 track (with American Indian translations to Eng sts) but the other does not.

How do I go about making sure that the VIDEO_TS I made is set to turn-on the subtitle on playback?

It's actually Sub-picture 0, currently set as 0 2 0 0 if that helps.

[blutach]

There may be 2 tracks on that DVD - one for subtitles for the whole movie and the other just for "Indian speak". Usually, the startup will set the latter track on. If there's only one track, ensure that somewhere just before the movie starts, you enter a SetSTN Subpicture track 0, on command. See 2COOLs' sticky.

Regards

[laserfan]

See 2COOLs' sticky.Oh, my, IfoEdit, thank you Les! :scared:

I had Googled this and was directed to some non-existent websites (or I have DNS problems) then I searched this thread. But I forgot all 2cool's stuff was stickied here. The sticky procedure worked! :o

Sorry r0lZ--it's just that I always think of PgcEdit first when needing some edit function! :)

[blutach]

Of course, using PgcEdit is simpler, due to its command editor, its overall view of the structure and its trace function. This is the guide I was referring to.

http://download.videohelp.com/r0lZ/pgcedit/third_party/2cool/subtitles/subtitles_on_default_pgcedit.htm

Regards

[laserfan]

Of course, using PgcEdit is simplerNOW he tells me! What the heck is videohelp.com anyway! :p ;)

[blutach]

It's where r0lZ's files are uploaded to.

Regards

[mikenadia]

From rOlZ:
So, even if you are sure that a PGC is really uncalled, it is not safe to delete it manually (unless it is at the end of the LU.)

This quote was referring to a DVD with MBS. Now, in the case of a DVD with no MBS but several LU with different commands, the uncalled PGC in the LU are not removed automatically (as indicated per message).
I do not want to delete the additionnal LU. Can I still delete, if uncalled, the last PGC in each LU? And what about the others?

Thanks in advance.

[r0lZ]

If you are sure they are uncalled, yes, you can manually delete them. You should delete the uncalled PGCs in the middle of the LU only if they are uncalled in all LUs.

[aslaksen]

Hi, I love PgcEdit, but I can't get Preview to work under Windows Vista. The preview window opens, I can turn the audio on, I can do bitmap dumps, but I don't get a picture. Any suggestions?

Thanks!

[M_Knox]

Use the Search, Luke!
http://forum.doom9.org/showthread.php?p=1250477#post1250477

[aslaksen]

Use the Search, Luke!


Sorry, I had actually done a search on pgcedit preview vista, but I had left the default of "Show Threads", which is not very useful given that the pgcedit forum is one long thread. I now tried it with "Show posts" and immediately found everything.

It solved my problem!

Thanks!

[selyb]

Request: When I kill playback of a menu, check to see if it is uncalled and if not then don't ask to choose a button to automate

I love the way PgcEdit handles all this but it happens very often for me that I bypass the Parental setting, then when I kill the playback of the pgc, I have to choose a button which is kind of pointless by then

[r0lZ]

I agree, but searching for uncalled PGCs is a long process (especially with DVDs with lot of PGCs and many commands), and it might become a nightmare for the user if PgcEdit has to rescan it every time he kills a PGC with button. Furthermore, you can do a Delete Uncalled PGCs to remove it. There is no need to kill it before. And anyway, if you know that a PGC is uncalled, the button you select doesn't matter, and you can accept the PgcEdit default selection. Not too much clicks IMO.

[selyb]

I understand

[edwood]

I have version 9.2 (English Version) installed. When I click on the help button and select Documentation, I get the following message in the right help window:

"Navigation to the webpage was canceled"

What you can try:
Retype the address.

What do I need to do to be able to access the Documentation file shipped with PgcEdit 9.2?

Thanks for your help.

Ed

[mikenadia]

Working here. You should probably just reinstall PGCEdit. You are missing (or it is not at the right place) an HTML file.

[r0lZ]

If you have Windoze, download and install PgcEdit_Manual.chm (http://download.videohelp.com/r0lz/pgcedit/versions/PgcEdit_Manual_chm.zip) in the same folder than PgcEdit.exe, or in a "doc" sub-folder. That should work. If PgcEdit cannot find the doc file locally, it tries to display the online HTML help (http://download.videohelp.com/r0lz/pgcedit/doc/PgcEdit_Manual.htm), but you may have network or server problems.

(BTW, there is a sticky thread about PgcEdit 9.2 (http://forum.doom9.org/showthread.php?t=145037). Please use that thread in the future...)

[edwood]

Thanks, i'll try that.

[blutach]

Remember, after downloading the CHM help file, to right click on it and click on unblock.

If webhelp is unavailable (for those who haven't got the CHM help file), it's probably temporary.

Regards

[edwood]

Thanks for all the excellent help. I tried your suggestions and the help screen is now available.

Have a good fourth!

Ed

[arrirc]

Hello r0lz

It seems that there is a conflict between the preview function of PgcEdit and ATi Graphics card driver. I have recently installed and updated ATi HD4770 card and the corresponding driver but it seems to crashing when I try to use the preview- not every time but a number of times I get a BSOD.

Could you look into this matter please?

My OS is XP Pro SP3 updated till date and PgcEdit is the latest version.

Thank you

[r0lZ]

Have you tried to disable the directdraw overlays in PgcEdit?

[arrirc]

Have you tried to disable the directdraw overlays in PgcEdit?

Thank you for your response.

No I have not done it, but could you please tell me how exactly can I do it? :confused:

[r0lZ]

Look in PgcEdit's Preview menu.

[arrirc]

Look in PgcEdit's Preview menu.

Thanks very much, it seems that the trouble is gone after following your suggestion. I am yet to test with VobBlanker though. :)

[IVaN_000]

Hi.

Any chance of some subpicture support in a future version of PgcEdit? That would be great.

I'm interested in plugin development. Any documentation on that subject? (I didn't kill myself googling. Sorry)

[blutach]

Check out DVDSubEdit.

http://download.videohelp.com/DVDSubEdit/

You can call it from PgcEdit by setting up a tool (see the help file on how to do this).

Regards

[M_Knox]

I'm interested in plugin development. Any documentation on that subject? (I didn't kill myself googling. Sorry)

There's no special plugin API for PgcEdit. You just write a piece of Tcl/Tk code and PgcEdit executes it as-is.

[r0lZ]

And unfortunately, I have never had enough time to document the PgcEdit functions.

Let me know what you want to do, and if it's not too complicated, I will try to give you the necessary documentation, or even write the plugin myself.

[IVaN_000]

Nothing specific. Sometimes I feel like I could automate some things I do manually. For example, "Remove useless stuff" works like a charm, but it could be better. Consider the following:

** pre commands:
1 LinkPGCN PGC 3
2 LinkPGCN PGC 4
** pos commands:
...

The second line is never executed, so it could be safely removed, and PGC 4 can be possibly declared uncalled and removed.

Many times you'll see lines like this:

if ( gprm(8) == 1 ) then { LinkPGCN PGC 1 }
if ( gprm(8) == 2 ) then { LinkPGCN PGC 2 }
if ( gprm(8) == 3 ) then { LinkPGCN PGC 3 }
if ( gprm(8) == 4 ) then { LinkPGCN PGC 4 }

And searching the whole DVD you find out that gprm(8) sometimes gets a 1 or a 2, but never a 3 or a 4, so the last two lines can be removed. This kind of stuff is very time consuming if you do it manually.

[blutach]

You will find the next version has a remove dead commands feature which will automatically remove command 2. Also coming is a remove uselss NOPs.

As for the gprm(8) example, the next version will have a summary of the various states that a gprm can take and of course removing commands which are unable to be executed is easier via the Info --> gprms feature, which allows you to isolate commands.

Regards

[IVaN_000]

Great. Thanks.

[backstar]

I don't know if this is the place to recommend new third-party guides for the pgcedit page... but here's one on editing / replacing DVD menus...
http://backstar.com/blog/2009/09/22/create-new-menu-for-existing-dvd/

[r0lZ]

I've noticed it, and replied in another thread (http://forum.doom9.org/showthread.php?p=1327947#post1327947).
Note that this thread concerns PgcEdit v9.0 and v9.1. There is a more recent sticky thread about PgcEdit v9.2 here (http://forum.doom9.org/showthread.php?t=145037).

[blutach]

Backstar - this is 3 threads in which you have mentioned your guide. Please observe our rules on cross posting.

Regards

[foobaz]

Hi r0lZ, Great new rev of your fabulous program. I have one question. Whenever I try to use 'Kill PGC Playback' it always backs up the VOB. I don't really want to do this. Past versions just simply rearranged the pre- post- commands. Is there a way to disable this backup behavior?

[r0lZ]

PgcEdit offers to back the VOB up only if you have killed a PGC with buttons, and the first time you accept the offer to replace the existing cells with a black frame in a specific doamin. In other words, it does it only when the VOB file must be modified. This is highly recommended if you want to use the incremental restore features.

But normally, PgcEdit asks for confirmation before doing the backup. You may have replied once "Do not show this dialog any more" to hide the dialog permanently and always use its default option. If it's the case, just use Options -> User Interface -> Restore All Hidden Dialog Boxes. You can also tick Display Hidden Dialog Boxes During Current Session and, when the dialog you want to unlock appears, turns its "Do not show this dialog any more" option off. The next time, it will be shown anyway.

[foobaz]

PgcEdit offers to back the VOB up only if you have killed a PGC with buttons, and the first time you accept the offer to replace the existing cells with a black frame in a specific doamin.
OK, thanks. I will pay close attention next time to the type of PGC and go from there.