PgcEdit 0.5

[r0lZ]

PgcEdit 0.5.3 released

It's principally a bugfix release. Please download it!

• Added an option in Info -> Calls Cross References do delete the commands in the unreferenced PGCs, and to clear the Prev/Next/GoUpPGC links. May be used to find more unreferenced PGCs in subsequent calls to the Calls Cross References function. Also, another option allow to convert unreferenced menu PGCs to dummies, to easily blank them with VobBlanker.
• Added "Delete All Commands" in the Edit (and popup) menu.
• Important bug in v0.5.2 fixed: new buttons created in a cell originally without buttons/BOVs were saved only in the first nav pack of the cell.
• PgcEdit was unable to parse the VTSM_C_ADT table if the table was present, but with no entries defined in the table. Fixed now.
• Fixed a bug in the parsing of the VTS_C_ADT table, occuring in rare circumstances: a wrong Nav Pack number was read, causing the search for menu buttons or BOVs to fail.
• Inport First-Play/Intro/Closing Clip: The cell commands numbers of the imported title are now forced to 0 in the cell playback table.
• Added a little delay when the Open DVD/Save DVD file requester is closed, to avoid a little Tk bug.

[lark]

Originally posted by blutach
Are you saying the macro killed the cell command/command number in the ORIGINAL TTN PGC or just did not reproduce it in the new title?

i tried to say that the macro retained the cell command number in the cell playback table, but removed (didn't reproduce) the actual cell command. obviously the clip worked fine.

just looking at r0lZ's announcement, i think this should have been taken care of and the cell command number in the table will be 0 (haven't tried yet, but i'll t(h)rust my master's voice).
thx a 1M.

regards
t

[r0lZ]

Originally posted by lark
t(h)rust

my master's voice

That's better!

[CoNS]

Originally posted by r0lZ
Also, another option allow to convert unreferenced menu PGCs to dummies, to easily blank them with VobBlanker.

Will the execution of this function resolve the reallocation error in Nero, in the cases where the error is caused by the presence of empty menu PGCs (no buttons, the playback time is shown as 0:00 and not marked as dummy PGCs)?

[r0lZ]

Originally posted by CoNS
Will the execution of this function resolve the reallocation error in Nero, in the cases where the error is caused by the presence of empty menu PGCs (no buttons, the playback time is shown as 0:00 and not marked as dummy PGCs)?

I don't think so.

The Nero reallocation error occur when there is a VOB totally unreferenced in the IFOs. In this case, you may safely delete it. (But keep a backup!)
Also the error occur when the VOB size is 0 bytes. This problem is already identified by PgcEdit, and can be easily fixed.
The same error may occur if there are inconsistencies in the IFOs. In some cases, PgcEdit will fix them when savind the DVD. But in some cases it will not.

In the case of a non-dummy PGC with a 0:00 PB time, there muts be a cell referenced in the IFO. The cell is most of the fime a single, black frame (henced the timing displayed in the PGC selector). But that is perfectly normal, and, IMHO, doesn't produce the Nero error.

The problem with this nero error is that it is not verry descriptive. You cannot easily guess what caused it.

Anyway, since I burn my DVDs with PgcEdit, mkisofs and DVD Decrypter, I have never experienced that error, and all my burns are recognized by my players.

Of course, if you can, send me a small DVD which cause that nero error, and I will see what I can do...

[lark]

i'm afraid 0.5.3 broke the import closing clip.
at least i'm getting this error

syntax error in expression "$c < $::pgcs(numvts),1,numcells)": extra tokens at end of expression
syntax error in expression "$c < $::pgcs(numvts),1,numcells)": extra tokens at end of expression
    ("for" test expression)
    while compiling
"for {set c 0} {$c < $::pgcs(numvts),1,numcells)} {incr c} {
		set_int ::pgcs($::pgcs(numvts),1,cellpbtable) [expr {($c * 24) + 3}] 0 1
	}"
    (compiling body of proc "::macros::import_title_closing_clip", line 356)
    invoked from within
"::macros::import_title_closing_clip"
    (menu invoke)

it still worked with 0.5.2 b2.

<why does code show smilies?>

regards
t :)

[jeanl]

Originally posted by lark

<why does code show smilies?>

it's laughing at us! I hate that!
jeanl

[r0lZ]

Originally posted by lark
i'm afraid 0.5.3 broke the import closing clip.
at least i'm getting this error

syntax error in expression "$c < $::pgcs(numvts),1,numcells)": extra tokens at end of expression
syntax error in expression "$c < $::pgcs(numvts),1,numcells)": extra tokens at end of expression
    ("for" test expression)
    while compiling
"for {set c 0} {$c < $::pgcs(numvts),1,numcells)} {incr c} {
		set_int ::pgcs($::pgcs(numvts),1,cellpbtable) [expr {($c * 24) + 3}] 0 1
	}"
    (compiling body of proc "::macros::import_title_closing_clip", line 356)
    invoked from within
"::macros::import_title_closing_clip"
    (menu invoke)

it still worked with 0.5.2 b2.

<why does code show smilies?>

regards
t :)

Right!
I will upload a bugfix immediately.

Smilies: When posting, enable the "Disable the smilies in this post" checkbox.
Of course, smilies should not appear in CODE sections. It's a Doom9 bug! ;)

[r0lZ]

PgcEdit 0.5.4 released.

Fixes the bug in Import Startup/Intro/Closing Clip macros, introduced in v0.5.3.

Also, there is a new PgcEdit_preview executable, by jeanl. Not a verry important improvment, but it's the first step to implement the preview under Linux (and maybe also under Mac OSX).

• New PgcEdit_preview v0.7: with option to turn off the usage of DirectDraw overlays to show the preview, and an option to save the menu backgrounds as PPM instead of BMP (internal use only!)
• Added "Preview -> Disable DirectDraw Overlays" (Windows only) option. On some systems, it may be faster to turn off the DirectDraw overlay display.
• Shift-clicking on the "BMP" button in the preview window allow to save an image in PPM format.
• Inport First-Play/Intro/Closing Clip macros were broken in 0.5.3. Fixed.

[blutach]

Man, I went to bed and missed a whole release!

Regards

Originally posted by r0lZ
But don't expect that soon, as I need to take some distance with PgcEdit, at least during the springs and summer.

@r0lZ: I'd hate to try and keep up with releases if you weren't taking some distance.........lol

[lark]

i'm getting this error during trace.

image format "bmp" is not supported
image format "bmp" is not supported
    while executing
"image create photo ::menubuttons::black1pixel -format bmp -data  "BM:\000\000\000\000\000\000\0006\000\000\000(\000\000\000\001\000\000\000\001\000\00..."
    (procedure "display_preview" line 109)
    invoked from within
"display_preview $w.video.f $type $vts $lu $pgc $cell $vobid $cellid $numbuts $vobu_direction"
    (procedure "display_cell" line 168)
    invoked from within
"display_cell $w $type $vts $lu $pgc $cell $cell_program($cell) $vobid $cellid $sprm8 true $mode 0"
    (procedure "display_domain_buttons" line 302)
    invoked from within
"display_domain_buttons menu $vts $lu $pgc $sprm8 $mode $show_cell"
    (procedure "::menubuttons::display_menu_buttons" line 16)
    invoked from within
"::menubuttons::display_menu_buttons $cur_vts $cur_lu $cur_pgc $::tr::sprm(8) trace $::tr::current(Cell)"
    (procedure "simulate_play" line 234)
    invoked from within
"simulate_play"
    (procedure "step" line 10)
    invoked from within
"step	"
    (procedure "::tr::dvd_trace" line 326)
    invoked from within
"::tr::dvd_trace"
    (command bound to event)

i tried also to disable DirectDraw Overlays but w/o luck.

btw view pgc works fine.
and v 0.5.3b2 worked ok.

regards
t

[r0lZ]

Humm, Sorry. I have removed the BMP library (because it is not correctly supported under Linux) and changed all BMPs used internally to PPMs, but I forgot this one.
I will release a new version soon (probably in 2 or 3 days).

This bug occur in the menu editor, when a letterboxed 16:9 video must be displayed in the background. It will not occur in 4:3, or 16:9 full screen and pan&scan.

[r0lZ]

PgcEdit 0.5.5 released

Thanks to jeanl, PgcEdit is now able to use PgcEditPreview.exe under Linux, through wine.

Also, the preview may run under Mac OSX, through darwine. However, it has not been tested yet. I'd like to hear if it works...

Of course, both wine (aka "wine hq") and darwine are free.

• PREVIEW (and menu backgrounds) available for Linux, and probably also for Mac OSX. You must install wine (for Linux) or darwine (for Mac OSX) to be able to use it.
• Added the Preview -> Use Preview option, to allow Linux or Mac users to turn the preview off, in case of problems with wine or darwine. Although not verry useful, this option is available also under Windows.
• Fixed a bug in v0.5.4, which caused the display of 16:9 letterboxed menus in the menu viewer to fail.
• When saving menu buttons, if you answered NO at the "Backup VOB?" request, PgcEdit offered to backup the VOB again and again. Fixed.

Enjoy!

[arsmori]

r0lZ's on a roll.
Your work is greatly appreciated (paypaled you some beer money too).

[r0lZ]

Thanks.

@Unix and Mac users: I have started a special thread on PgcEdit's Preview under Linux and Mac OSX.

[CoNS]

Originally posted by r0lZ
Anyway, since I burn my DVDs with PgcEdit, mkisofs and DVD Decrypter, I have never experienced that error, and all my burns are recognized by my players.

Isn't this process unneccessarily time and space consuming when you're working with a disc in a VIDEO_TS folder on your harddisk? You're creating an image first and then burning, or do I misunderstand?

[lark]

you might think so, but it's not that obvious.
which app are you using to burn?

regards
t

[r0lZ]

Yes, an image is created on disc before the actual burn. If you have 2 physical HDDs, the time it consumes is around 3 minutes to write a full DVD-5 image. And the image may be automatically deleted after the process, if you wish.
I do it that way essentially to ensure 32K gaps between the IFOs and BUPs. Nero is not able to respect your VTS pointers!

[blutach]

Speaking of Nero (and perhaps this belongs in DVD Burning), the latest thing I have found is if you burn in using the UDF/ISO bridge mode, selecting UDF 1.02 (like you should), it doesn't work!!! It even warns you it won't work and that you must select DVD-Video high compatibility mode.

How bad is that?

Regards