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

[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.