PgcEdit 0.5

[zacoz]

Got zip thanks jeanl, but they didn't help track down the problem. They all play slow.

I then tried using them through PgcEdit pre 0.5.7 final (copied into bin directory and renamed to PgcEditPreview) and they still played slow. Copied PgcEditPreview from pre 0.5.7 final into post 0.5.7 final bin directory and it played fast. So this seems to discount that it's to do with having run it through PgcEdit.

I did realise that I had disabled the Radeon graphic control center background process. When re-enabling this I did discover that if I run the old PgcEditPreview (from pre 0.5.7 final) through PgcEdit with overlay disabled it plays slow. No amount of disabling/enabling overlay with the new PgcEditPreview versions got them to go fast however.

A question jeanl. Did anything change on your system that may have affected the compile process ? Do you have the source from the old version that can be compiled now for comparison testing ?

[jeanl]

zacoz, I have the old code, but from my understanding the old version is the same as one of the ones I sent you. I'll recompile and send.
In the meantime. I'm pretty sure your problem comes from the fact that preview can't acquire the overlay mixer. You can check that by wiggling the preview window. If you see the video "float" within the window (as if it's not exactly tied to it), the overlay mixer is on. If the video feels securely attached to the window, you're in bitmap mode (I'm pretty sure that's the case for you). You can also take a screenshot of the preview (Alt-Prt Scrn). If you have black instead of the video in the printscreen, you're in overlay mode.
Now the question is, why in the heck isn't preview getting the overlay buffer?!
I'll get back to you, but if you can make this small experiment, that will help.
Jeanl

[jeanl]

OK guys, I found the bug. It was a very stupid mistake on my part. The current version of preview ALWAYS use bitmaps and never tries the overlay mode. A simple line I forgot to remove when I was making tests for the button display code.
I'll create a new version and post a link.
Sorry about that zacoz!
jeanl

[blutach]

I can report the "buttons bug" in Preview is also now fixed. Thanks jean!

Regards

[zacoz]

I can report the "buttons bug" in Preview is also now fixed. Thanks jean!Ok, did I miss the link to the new version somewhere ?
OK guys, I found the bug. ... A simple line I forgot to remove when I was making tests for the button display code.While not in your programming league, I know from experience that this sort of thing is so easy to do.

Seems this is one time that having an old PC has helped hey - the speed difference being so noticable with it.

[r0lZ]

Yes, you have probably missed beta 16. Anyway, here is beta 17 (http://www.videohelp.com/~r0lZ/pgcedit/beta/PgcEdit_winexe_0.6.0beta17.zip).

[zacoz]

Yes, you have probably missed beta 16. Anyway, here is beta 17 (http://www.videohelp.com/~r0lZ/pgcedit/beta/PgcEdit_winexe_0.6.0beta17.zip).Ah ha, I thought beta 16 had come out prior to the problem being found, so I hadn't downloaded it. Hard to keep up with every beta release - they just come out too fast.....lol

While jeanl, jsoto, and yourself obviously must enjoy the work you put into the programs we all here use, please know that the effort and support is appreciated nonetheless.

[r0lZ]

Thanks, zacoz.

Remember that the betas are... just betas. You don't need to try all of them, especially the first ones, potentially bugged. I like to release many betas, so that beta testers are able to confirm that the changes I made are correct, but I will summarize them soon in v0.6.0 final. This is the version to watch!

Oh, please note that the Preview has not yet been updated in beta 17. Since jeanl is working on the LB cell bug, I prefer to wait.

[zacoz]

@ r0lZ / jeanl: Should PgcEdit 0.6.0 b17 contain the fixed overlay version of PgcEditPreview or are we getting issues confused ?
Downloaded it and still can't get it to use overlay, however the earlier (pre v1.9 preview) is using overlay mode.

[zacoz]

Seems we were posting at the same time - do you have a second job as a mind reader ? ....lol
Beta's - Yes, haven't downloaded many of the 0.6.0 beta's as I'm not interested in the DL functionality, although I do download some of the others if I'm interested in the improvements being implemented.

[jeanl]

zacoz, I didn't post a link, and r0lZ does not have the latest version. I sent it straight to you (email) for you to confirm. You'll have to dig it up from the spam! I'll send the version to r0lZ promptly...
jeanl

[zacoz]

Thanks jeanl...For some reason I hadn't even thought about downloading my email tonight. Long day at work today maybe (end of financial year processing and on top of that starting a new job on Monday - same employer).

Just tested v2 and got to say ...You are THE MAN :cool:

From the size I gather that it uses dynamic link to mfc42. There's absolutely no slowdown noticeable at all between v2.0 showing button locations and v1.8 without buttons.

Thanks for your efforts in tracking issue - considering I seemed to be the only one who was seeing a significant slowdown. :thanks:

[jeanl]

Zacoz, I'm glad the problem is fixed for you! Sorry about this stupid mistake. Yes, the version I sent you was probably the dynamically linked version, smaller.
And good luck with your new job man!
Jeanl

[r0lZ]

Preview 2.0 (http://www.videohelp.com/~r0lZ/pgcedit/beta/PgcEditPreview20.zip), now hopefully bug free!

[2COOL]

@r0lZ

I came across an interesting bug. In my "Goto calling command" dialog, if I select Refresh and then Close, it won't close. You can't even use the top right close button either. But if I then select New Target and Close, it will.

I was using your current beta17

[r0lZ]

Thanks, 2COOL. Bug found and fixed.

[blutach]

Welcome back 2COOL - some interesting events during your absence mate :)

Regards

[doomer2]

I was just making a backup of a dvd with 0.5.7, and got this message when trying to edit a menu:

Warning: PGCEdit has detected several sets of buttons in this cell. .... Warning: If you edit the menu, the additional sets will be lost!

I've never seen this message before, and don't know how common multiple button sets is. Is adding support for this something on the soon todo list, or is it so uncommon that it's an unlikely/far away feature addition?

Thanks.

[r0lZ]

I'm affraid it's the second case. Dealing with multiple sets of buttons requires many changes in the program, and this feature is really not common.

Multiple sets of menu buttons are used for several purposes. For example, you can have a menu button command that change in the middle of the cell. Or the button highlight may be animated.
If you edit the menu anyway, you will keep only the first state of the button, and it will be repeated upto the end of the cell. This doesn't maen that the menu will not work anymore, but that may be the case. Do an incremental backup first, and backup the menu VOB when requested!

You may want to try MenuEdit for this job, as it has provision for a limited number of button sets. But with the free version, you will be able to edit only the first group of buttons. (A menu group is NOT a menu set!)

[2COOL]

Or the button highlight may be animated. A perfect example found here (http://forum.doom9.org/showthread.php?p=659021#post659021).

[jeanl]

Yeah, appleseed and spiderman1 are good examples of animated highlights. It's much more frequent to have several button definitions in the same cell (I've seen it a few times), for example, with inactive buttons (NOP commands) first, during the first few seconds, then "true" active buttons toward the end.
Menushrink always takes the last definition, when there's several, in the hope that this is the right one... Not an easy thing to automate...
jeanl

[doomer2]

Is there any way to replace a title wholesale in PgcEdit? I have a DVD that I took the video from one of the titles and did some effects processing on it, and exported it back to a dvd. I'd like to replace the Title on the original disk with my edited version without having to reauthor the whole thing (there are a lot of images and menus on the original).

I know you can import/replace menus and I know you can import an intro or closing clip. But I don't see a way to replace a title with a title from another VOB set like you can with menus. Is there a way?

Assuming there isn't a way to do it from within PgcEdit, can I cheat and replace the VTS_03_01.VOB and VTS_03_02.VOB with the edited VOB's and open it in PgcEdit and rely on PgcEdit to fix the title and IFO structures to match what's in the new VOB's? Will the chapters still work?

Thanks.

[jeanl]

This is a job for vobblanker. That's exactly what vobblanker is for. Cutting things out, splicing things in. So give it a shot.
Replacing the vobs might work, depending on what you did to them, provided you do an IFO mock strip before you import in pgcedit. But that's not entirely safe if you have cell commands, and unusual cell flags. Use vobblanker instead...
jeanl

[r0lZ]

Replacing the vobs might work, depending on what you did to them, provided you do an IFO mock strip before you import in pgcedit.Hum, I think the correct method using IfoEdit and PgcEdit is to overwrite the original VOBs and then do the mock strip. To use this method, the number of PGCs, cells, programs and chapters must be the same in the original and the new VOB, in the same order.

But I agree, it's a job for VobBlanker!

[jeanl]

Hum, I think the correct method using IfoEdit and PgcEdit is to overwrite the original VOBs and then do the mock strip.
Yes, that's what I meant. Replace the vobs, do your mock strip, then load in PgcEdit (which isn't really necessary)...
jeanl

[r0lZ]

Ah, OK. I misunderstood you.

Note: This discussion continues in the VobBlanker thread here (http://forum.doom9.org/showthread.php?p=683374#post683374)...

[r0lZ]

PgcEdit 0.6.0 is out.
Please use this thread (http://forum.doom9.org/showthread.php?t=96972).