MenuEdit - Tool to edit DVD Menus

[mpucoder]

Originally posted by Dimad
To make me happy I'll need to figure out what exactly these fields in PCI-pack mean: startingButton, forceSelButton, forceActionButton. If someone knows it say it loud.


Sorry for the long silence, a really active forum kept me busy.
Have you seen http://mpucoder.kewlhair.com/DVD/pci_pkt.html ?
For single display mode subpictures (4:3, or 16:9 with no letterbox or P/S allowed) there are 36 buttons. The buttons get divided evenly if auto_letterbox and/or auto_Pan/Scan is permitted (18 buttons each if only one auto mode added, 12 buttons each if all three modes allowed)

Starting button number and number of buttons define the range of valid button numbers. It should correspond to the defined buttons in BTN_IT. Note: number of buttons is for one display mode, multiply by the number of display modes (1,2, or 3) to get the total number of buttons.
Force select causes a button to be selected at btn_sl_e_ptm (button select end time, basically a time-out) but not acted on. Force action causes a button to be acted on at btn_sl_e_ptm. Normally only one of these values is set, since force action should happen fast enough to not see the select color, but they may both be set, causing the button to flash on some players prior to actioning. They may also be set to different buttons, causing unpredictable results.

[Dimad]

Originally posted by baker
Now the idea was using the fantastic menu edit program (which has worked flawlesssly may I(attempt)say) we could simply remove the button for the extras, leave the scene selection and subs selection menu on and bang.... we would have a brilliant looking quailty DVD with the original menu and scene selection.

Don't forget: you may use it also to remove links to unavailable scenes in scene selection menus when original disk is split to 2 DVDs.
:)

[schlaufer]

Originally posted by Dimad

Here is the MenuEdit with quick and dirty fix.
To make me happy I'll need to figure out what exactly these fields in PCI-pack mean: startingButton, forceSelButton, forceActionButton. If someone knows it say it loud.

Hi Dimad,
thanks for this nice app. Version 1.1.0 solved the problem for too.
Cheers,
schlaufer

[Sp33d]

I'm not sure where this post should go but I have a question about this app. If I use IFOEDIT to strip streams, how can I incorporate my menu back into the mix? For example, I back up a movie and it's 4.72GB. To get it down to size I use IFOEdit to strip soundtracks. There's no way to add the menu back to this because the IFOEdit files start right at the beginning of the movie. Is this utility only useful when the movie files with menu is smaller than 4.36GB?

[VidHack]

Wrong forum, please start a new thread. You need to learn how to use IFOupdate. This will let you merge in your old menu. Please start a new thread if you need help.

VidHack

[int 21h]

Great application, great start to what I'm sure will only get better :)

[dvdmonkey]

I haven't really played to much with the app yet, but when you delete the buttons, you don't need for your menu, does the app remove the segment vob out of the menu vob aswell?
If not is that something you can incorporate into your future upgrades? I have been trying to edit Star Wars' P.M. to get the DVD to use only one menu, and your program sounded promising for my problem.
Thank-you

[int 21h]

Sixth Sense: Special Edition (Buena Vista 1999), NTSC, R1
VTS_05_0.VOB
VOB-ID: 1, Cell-ID: 1
IndexofButton: 4 ('Preview Trailers')

Emailed the before and after nav-packs of that vob/cell.

Thanks again.

[DVD Maniac]

I have just used this program on a multi episode test (Fawlty Towers) split to two discs to retain full quality amd working menus. This is a tall order to get all the menus working correctly but I think I am there now.

Previously I was using the direct edit trick in Vobedit to disable button's (setting all the attributes to 0) and editing button navigation (by changing the hex values directly and copying from the previous buttons hex value). After much time messing around I finally got all the buttons I wanted disabled / edited working correctly on the PC player. I nearly chucked my settop out the window when I found that ALL the disabled buttons still worked!

Having tried this app - all the buttons now disable on the PC and settop - success!

Some questions then for the experts -

1. What is the app doing differently to the "manual" method in Vobedit?

2. Why are there multiple references / nav packs to the same vob? It seems that you have to only change the FIRST reference using the manual method for all the edits to work (ie changed nav function). Is the tool editing ALL the vob nav packs, not just the first reference?

3. Why the different results on PC player vs settop

Thanks

[Black Hole]

Hi Dimad,

First of all I wish to thank you for this nice tool. The first time I saw it was on Doom9 news on 25th February but I didn't have an opportunity to test it properly until today, 9th March. Prior to MenuEdit, I was used to edit buttons directly with an Hex Editor because I found that VobEdit was sometimes destroying the NAV packets of the original VOB file, so I have some background in doing tests.

Today I tested with Jimmy Neutron main menu, just to find the same behaviour posted earlier: the buttons order were moved, but the command (the most important thing after all) was not copied back. I discovered this with VobEdit against the patched VOB, so I logged on here to find if another MenuEdit version was released. I was using the version released on 17th February ZIP file.

Well, my OS is Windows 2000, but I think that doesn't really matter since it was discovered along this thread that the errors weren't OS-dependant. While I was reading, I was going to point you to the excelent MPUCoder web site, but he himself has already done so - MPUCoder and Derrow are gods to me! :D -

I haven't still tested the 27th February MenuEdit 1.1.0 version, but others reported that it worked fine. I will check it as soon as I post this reply, but I would like to give Dimad some suggestions about his program, which I think are easy to code and could greatly improve the way people understand the tool (which is still a bit oriented to pros).

1. Include the version number inside the program
This is a simple thing for not to mix different versions of the program. I already got 3 different executables from this thread and the internal version of all 3 of them is 1.0.0.1 ... you can only see it in Windows Explorer file properties, so a little "About" button in the main program or adding it besides the name of the title bar is very welcomed.

2. Check more buttons beyond the first ones
This is very interesting and MPUCoder has given hints about it. I found some time ago, while I was trying to correct "Lilo & Stitch" menu buttons, that there were 2 copies of the buttons: one for 4:3 and another one for 16:9 ... one was starting at button 1 and the other one was starting at button 19, and I didn't know why until I read MPUCoder reply in this thread ... it made me trash a disc when I found it not working in a friend's 16:9 television!! :mad:

3. Make a small section presenting button properties
Since you already got the data from the NAV packet, it would be very useful to present numeric information about the button being changed. Over the preview screen you could place 36 little squares numbered 1 to 36, as shortcut buttons to the info of that button, being greyed and non-selectable those whose 18 bytes of data are all zero's. That way you could inform the user of the availability of ghost buttons which are just 1 pixel wide with auto-select or auto-action.

When you click on any of those 36 shortcuts, the VOB button should be highlighted on the preview screen and a small info section should be filled with all the available data: starting & ending XY coordinates, selected button when up/down/left/right is pressed, and action command to be executed.

4. Make a small button editor
It would be very useful, just in case we need to change the behaviour of the button, to change the above parameters. In fact it would be as easy as the current task of MenuEdit, as you already know which values must be changed (you do, don't you? hehehe). This way, we could recode the way buttons are selected with the remote controller.

The toughest part would be a VM Command editor, but that is not so urgent. You have a lot of info about commands in MPUCoder site at this page (http://mpucoder.kewlhair.com/DVD/vmi.html). The naming of commands in that web are the same as the little command editor in IfoEdit, but differs from the naming in DVD Maestro or Scenarist. I could try to help you match them if you really need it.

5. Don't save changes immediately
You should track the changes in memory or in a file, just in case we need to undo the values of a button and revert to the original state. When we've finished our editing or deleting, the user should be forced to save them all. If the user exists the program without saving changes, a requester should warn him to do so, giving the option to skip the process, just in case he doesn't want to change anything at that moment. An option to back up the original VOB would be also a good idea ... when you code an application (I used to do that years ago) is advisable to make it fool-proof, but even in that case, you will find the "King of Fools" complaining and moaning :p

I hope you will take all this suggestions as positively as me writing them up!

Greetings from Spain.

[yamyam]

I have been using menuedit to disable buttons in dvd menus, it works great, a very promising little program but on certain menus it freezes like on a view to a kill (pal). I really hope this will be developed further because its very easy to use and saves a lot of messin around.

[int 21h]

Nevermind on the bug... I forgot to remove all instances of the button, throughout the motion menus.

[baddbill]

Great program! It has worked wonderfully on several DVD's except my last. On XXX after I edit the main menu with menuedit the swirly lines that appear on each side of a selected menu button are deformed or only partially visible. You can still tell which button is selected but it doesn't look good.

I've read on this forum that deleting the default button is not a good idea. Is this true? If so what is the best way to change the default button?

Thanks,
Bill

[baddbill]

Hi Dimad, I deleted the audio, subtitles and chapter selection buttons on the main menu of XXX with menuedit 1.1. Before the image is created the files play fine with both PowerDVD and WINDVD. After I create an image with imagetools .89 WINDVD plays it fine but PowerDVD won't play any of the traiers or half of the bonus material. I would email you the vob file but after I stripped out three vob id's the vob is still 90 megs. Here is some info for you:

XXX, NTSC, Region 1
VTS_02_0.VOB
Main menu is vob ID 1, cell ID 5 and 6
I deleted buttons 0, 3 and 4 all at once in both cell ID's


This is the only menu that I have edited in the vob. If you need any more info let me know.

Thanks,
Bill

[Dimad]

OK, I'm back and even have done one thing: opened a web site for the MenuEdit: http://menuedit.dimad.net
All further releases will be posted there.

I've read all last posts, Black Hole - that is impressive writing, and will reply latter.

[Fmazzanti]

Nice looking site... :)

[djadjet]

Nice.

Hope you enjoyed skiing.

[Dimad]

MenuEdit 1.1.2 is released. (http://menuedit.dimad.net)
Check "what's new" to see what was added/fixed.
All future notifications about new releases will go through MenuEdit newslist. So, take your time and subscribe if you are interested.

[Cataro]

Hi Dimad,

Thanks for this nice app. Great job.

Greetings from Portugal

Cátaro
:D

[2COOL]

Dimad,

When I test my menus after MenuEdit, everything is fine. But when I view it on my standalone, it seems that my titlespace for my highlights have shrunk . It's like my aspect ratio for my button highlight space has shrunk but still centered. Many of my buttons have offset highlighting toward the center. Normally viewing it on a TV, you have a rectangled view, but my highlight space is a centered square with some buttons out of it's boundaries now. It's only after I view it on the TV. I've done 3 movies so far and still the same.

[djadjet]

I have encountered exactly the same problem. It happens on the 4:3 but not on 16:9 (at least for me).

[firstelvys]

Dimad,

I'd like to thank you for a great tool. I know already told you this before, but it bears repeating. You are probably busy, so I will get to the point. We all know that DVD's do not like to have the default button on any menu deleted. Many DVDs just hang there. I have found that deleting their functionality allows this with out a problem. I used VOBEdit until your fantastic tool came along and I just zeroed out all of the funtions of a button while leaving the button itself intact. I believe you're already doing this as part of your tool. I thought that is what you meant when it said "edit button" on your tool. Again, thanks for the great tool.

Elvys

[DVD Maniac]

Hi Dimad,
I sent you a post to your site - no reply.

Regarding the edit function. On the screen you get position edit and next button edit feature - obvious how these work. I want to make the button link to another vob in my menu. At the bottom of the edit pop up screen there appears to be a an entry point to do just this labelled "Command" with what appears like a look up button next to it. Problem is that it is greyed out and apparently non functional.

Please explain how to use this (Is it not yet functional????)

Thsnks

[Dimad]

Seems that time has come to make few things clear.

I wrote MenuEdit to save me some time when I make a copy of the DVD. And it does exactly what I want it to do, if you have not tried to fix menus on DVD either with HEX-editor or with IFOEdit, try it - you will better understand what I'm talking about.

Then I figured out that I must not be the only one who wastes an incredible amount of time on this. So, I made MenuEdit public.

Lets do some math: approximately 2000 copies of the MenuEdit were downloaded since it was first published about 6 weeks ago. Assume that MenuEdit is used once a week to edit menus in the copied DVD (some people seams to copy dvds more often, but lets be conservative). Assuming that editing menu "hard" way requires 1 hour (again, lets be conservative) and with MenuEdit it hardly takes any time, this tool already saved 12000 hours. Which is 500 days or roughly 1.4 years.

MenuEdit used this way for a year will save its user at least 52 hours. This is 6.5 8-hours working days! Time, which could be spend either for fun or for earning money.

I enjoy writing neat and useful programs, but this is not the only thing I like (say, I find playing with my daughter much more interesting). I started to wander why should I spend my time working on the features I don't need at the moment (locking myself away from my family) to save someone's time. If you have an answer let me know.

To help me answer this question I've set up the MenuEdit web site and put "make a donation" button there. You need to understand, I have a day job and I'll never earn even close to this amount by selling MenuEdit or receiving donations for it. I've done it to see how much people are interested in this tool and how much they value their time.

So far there was not a single proof that someone finds MenuEdit (read: my time) worse anything. Sorry, I need to correct myself here: some people at least said "Thank you". My answer to them: "You are most welcome!".

Until something will change I will work on MenuEdit when I have a mood for it.
As I said before, eventually I'll add:
- editing of other button attributes (command, etc.);
- automated treatment of the deleted default buttons;
- cell accurate preview of the menu (actual menu will be shown on the background);
- deletion of cells from the vob-file;
- saving of the button images so that interested people can use them in other authoring programs,
- etc.
- etc.

Even then it is not clear how to avoid the problem of this program being sold by other people, but I'll cross that bridge when I come to it. :)

Yours,

[mpucoder]

It has long been the policy of Doom9 to NOT bother freeware authors. Be grateful for what they do, maybe report a bug or circumstances around a known bug that could be useful to the author. But NEVER press for new features or release dates. The authors of these programs write for their own satisfaction, and share the programs with you in the hope that you will find them useful. The pleasure derived from writing freeware can quickly fade when people start asking for features, or when promised features will be working.

[DVD Maniac]

Dimad,
I understand where you are coming from on this, my post was referring to your latest release on your site where it does say that the command function edit has been added. I have posted a couple of thanks to you on previous occasions.

I think you will get some donations as this is such a great tool and I have been planning to do so myself. I regularly donate for tools I find really useful and this one will be no exception. I myself have no expectation levels on what you do with further development - its great as it is and I am happy to donate. I hope others will do the same.

[Dimad]

Originally posted by DVD Maniac
Dimad,
... was referring to your latest release on your site where it does say that the command function edit has been added...

Sorry, but here is the quote from the site:

Version 1.1.2
…
Add - Position and links to adjacent buttons can be edited manually for each button.
…


I don't want to sound like I don't care what is the public opinion about MenuEdit or what are the features one would like to have added. Everyone is welcome to submit these - I'll put it on MenuEdit's TODO list.

Mpucoder put everything together very nicely, I would not say it better. Once again I would like to thank him for his nice and very informative site. Another proof of the fact that info assimilation depends strongly on the way it is presented.

Regards,

[VidHack]

Dimad,

Hello, just wanted to throw a THANKS for the app out there to you. I do remember the OLD days of Hex-editing and you have already saved me a few hair follicles. Your app is sweet. Also, you actually got me on a search for more code. I have now studied VobDump and am trying to see if I can port any of that file pointer code to VB. Also, please check out the OGLE Player, its an open source DVD player that has awsum pages of source code, especially there MPEG screenshot routines, I have thought on this issue and hopfully the eventual rolling in a routine like that to your wonderful app. So, I respect your decision on whatever you do, and thank you for guiding me in a new direction.

VidHack

[Dimad]

Hi, VidHack!

So far I've looked through VirtualDub, mpeg2dec, ogle and xine source code. All of these are quite nice apps, but my lord what a mess - it is not straightforward to get needed piece of code out of them.

VB is visual basic? Have not used this for a while now.

[mcentee]

Hi - great little app - does what is says on the tin..however..

Once i have edited a menu vob, the next time I try and edit it (whether I va copid it to another filename, or another diretory) menuedit comes back straight away with the following "information" dialog box:

ERROR - The Operation Completed Successfully

Any ideas ?

[Dimad]

Originally posted by mcentee
Hi - great little app - does what is says on the tin..however..

Once i have edited a menu vob, the next time I try and edit it (whether I va copid it to another filename, or another diretory) menuedit comes back straight away with the following "information" dialog box:

ERROR - The Operation Completed Successfully

Any ideas ?

Yes, a few. But I'll need to figure out exact location.

I'll be away for two weeks, but comp will be with me. If you don't mind I'll send a debug version to you when it's ready and I have an access to the internet.

By the way: What happens after this message? Does it still work after that?

[rpboy]

Originally posted by Dimad
Edited 03/18/03
I've opened a site for the MenuEdit. http://menuedit.dimad.net
All further releases will be posted there.

I've been trying to get to this site and it keeps saying "Cannot Find Server". Anyone know another location to download this tool? I'm very excited to try it.

Any assistance would be most appreciated.

[mcentee]

Dimad - have a good break! FYI the app doesn't process the vob file after the error.The app doesn't "hang" either, just ;ets you go on opening a nother vob if you want, but if you try to open the same vob you get the same message.

[VidHack]

Enjoy the trip away. I have confirmed the bug that 2Cool posted a few pages back regarding Button aspect ratio incorrect. So, I am kind of hoping you can get your hands on Men in Black DVD, so perhaps together we can figure it out. I am starting to dig into this problem on my own.

Here is the info...so far...

DVD: Men in Black (Directors Cut)
Menu VOB: is the widescreen/fullscreen selection menu :VIDEO_TS.VOB
(I had to rename it to VTS_08_0.VOB, to directly open it up in your app)This VOB is only 3598kb, so even a personal email may be possible to send to you, not in this forum...I understand..)
VOB ID: it only has VOB ID 1 and VOB ID 2, both with cell ID 1 and cell id 2.
Both only contain 3 buttons (Which makes this a really nice troubleshooting/beta test menu VOB)

Basically I am removing the fullscreen button, so only the Widescreen button is available. Which worked fine, and playing it on the computer PC DVD player, all seemed OK. But in the stand alone, the button X START value seems to be divided in half. So, opened the VOB in VOBedit and did some comparisons (Against the UNmodified VOB)....Hmmmm....Interesting....

Notes:(So Far)VOB ID 1 Cell 2
General: Using NAV Pack 1273 (First pack of Button info not zero)
(Oh yea, I realize that your array values in C++ must start with zero, but this really messes with your head in VOBedit, buttons start with a value of 1, and yours start with 0) Also, I see that you really dont delete the button, you give it a X/Y value of 1/2 and hide it in the corner of the screen, one Glitch may be that you arent killing the COMMAND, perhaps sliding in a NOP, should be tried. I have compared the NAV packs button x/y values and all seem PERFECT, but there are differences in a stand alone DVD player, they use other Tables that a software player doesnt. So, the current PGC.IFO will also have to be compared, especially http://mpucoder.kewlhair.com/DVD/spu.html
This may shed some light on this issue.

Anyway, I like what your doing with your app, and the direction I see your going. Perhaps setting up a few troublesome Menu VOBS for beta testing against (NTSC/PAL)(Widescreen/Fullscreen)(Anime/Whatever) could be considered. Thanks again, keep the faith...your work is appreciated.

VidHack

[VidHack]

OK, a bit more digging into this problem....

Perhaps more options are in order in your App. I see how you shift the X/Y coordinates to 1/2 and stack the buttons on each other. Heres a few problems though... When I used to Hex-Edit, I would NOP the Command, so that the button still existed but didnt do anything, it would still highlight when selected but not link to anything. This is important to note because the links in the .IFO PGC are still presserved. The current approach of your app leaves some bugs if there is a hard link in the PGC.IFO that links to the button directly, this causes in consistancies during runtime of the DVD.

Perhaps, changing;
:byte: :value:
008d Highlight status / emphasis1,2 / pattern
00bb button color (0=none)
00c5 Command (NOP)
009d Starting Button (brutal if set to deleted button)

Can be changed instead of the X/Y variable, so that it just wont highlight and a NOP is inserted.

The PRE / POST Commands in the associated .IFO hardlinking to the deleted button is a real problem.
And I am still podering the subpicture packs.

Anyway, I think your app is sweet, just needs a bit more debugging/tweaking. I may have to stick with Hex-Editing a bit longer. Thanks for your on-going work with MenuEdit.

VidHack

[Fmazzanti]

Dimad,
some more input you may beinterested in... this one is stupid but still interesting. When you click the 'open' button, MenuEdit let's you choose whatever VTS_**_0.VOB you want to open, but not VIDEO_TS.VOB, and sometimes you have to edit buttons there.
Just my 2 cents...

[Dimad]

The current approach of your app leaves some bugs if there is a hard link in the PGC.IFO that links to the button directly, this causes in consistancies during runtime of the DVD.

Yes, I know. That "quick and dirty" fix is still there. I'll make a more robust automated button deletion in the next release.

I'm a bit confused about subpicture problem. MenuEdit should not change any fields which affect it. Could it be the same problem as reported here: http://forum.doom9.org/showthread.php?threadid=49778?

Can someone, who encountered this problem, do few simple tests:
I) if you have a RW disk try to write a movie with the "original" menu VOB file(s). Does it behave differently now in standalone?
Problem remains? -> Sorry, not MenuEdit's fault.

II)
1) save an original vob file somewhere;
2) open a vob for editing;
3) instead of deleting buttons, "Edit" at least one of them;
4) don't change anything, just hit "OK" in Button dialog;
5) when you done, hit "OK" in Menu dialog;
6) use some program to compare original and edited files (file's content,not just size). (Here is the link to some utils: http://www.thefreecountry.com/programming/filecomparison.shtml)

Is there a difference? -> Too bad I've messed something up. :(

Thanks in advance for your help.

I had to rename it to VTS_08_0.VOB, to directly open it up in your app
or
MenuEdit let's you choose whatever VTS_**_0.VOB you want to open, but not VIDEO_TS.VOB

What can I say? RTFM. :) (No offense.) This is answered in MenuEdit's FAQ (http://menuedit.dimad.net/faq.html#Can I use MenuEdit to edit file different from *_0.VOB without renaming the file)

[Fmazzanti]

Originally posted by Dimad

What can I say? RTFM. :) (No offense.) This is answered in MenuEdit's FAQ (http://menuedit.dimad.net/faq.html#Can I use MenuEdit to edit file different from *_0.VOB without renaming the file)

Ahh... yes. Thanks for the polite answer.

[VidHack]

Hello,

This is going to be a long POST, so sit back and grag a coffee. I spent a few hours troubleshooting the aspect ratio problem. I believe I found the exact cause of it.

What I did: I loaded a original menu VOB (VOB1) into HEXedit. Then I loaded the button deleted VOB (VOB2) into HEXedit and ran a 'Difference Compare Dump' of the modified bytes. What I learned was that you modify 22 bytes per NAV packet. Then I grabbed my DVD packet lookup sheets (From MPUcoders website) and examined exactly what you modify. Thats when I saw the problem.

Background: The VOB that I button modified had exactly 4 NAV packets, with 3 buttons that show up on the TV when viewing it, Button 0,1,2, and your app showed exactly button 0,1,2 when editing. Heres the BUG... There is really button 1,2,3 AND button 19,20,21 in the packet stream (19,20,21) are used for the different aspect ratio (16:9). Your app did delete button 2 and its counterpart button 20, but it also changed the X/Y values on button 19 and 21 to match button 1 and 3. This is the BUG, the app shouldn't modify buttons 19 and 21 X/Y original values.

The Fix: Please add a button on your app to show upper range buttons in your editor window. Example...Buttons 1-16...Buttons 17-32 or something like that. You will notice on some DVD's the X/Y start/stop values are different. You can manually fix this problem by using VOBedit after you use MenuEdit to reset them back, just compare the original values with the new ones and change them back.

I have a detailed sheet that shows the exact values of my buttons, before and after, the modifications, If you want me type it in, let me know...Its quite long. I hope you understand what I have written, a quick patch to your great app shouldnt be that difficult, just use the original X/Y start/stop values on the Unmodified upper range buttons. Thanks again.

VidHack

[2COOL]

G:D Vidhack! G:D Vidhack! Alright! now this is the fix I'm talking about! My many thanks to you, my friend, on your devoted research.:D

@Dimad

A future big THANKS to you if you get this fix implemented soon. I can do without your future implementations for now but this one affected alot of my DVDs. Especially the Road to Perdition. I don't have any button highlights in the Main Menu.

[Cayne]

I had the same aspect ratio problem.

I tried the way you described in your last post, but when nothing is edited it results in identical files.
It seems that the subpics for 4:3 are changed only when editing something.

[VidHack]

Well, here is some tech info for Dimad, on the suspect bytes....
(Only Nav Pack 2 is explained)
________________________________________________________________
Search for differences

1. F:\MenBlack_VOBS\Orig_MENU\VTS_08_0.VOB: 3,684,352 bytes
2. F:\MenBlack_VOBS\VIDEO_TS\VTS_08_0.VOB: 3,684,352 bytes
NOTE: 4 NAV Packets in this VOB that aren't 0 for button data.
________________________________
NAV PACK 2; lba 1364

:Orig: :Modified:

2AA0C4: 02 01 --button1 nr to select link byte
2AA0CD: 5B 40 *********
2AA0CE: B2 10 ** **
2AA0CF: 38 02 ** 2 ** new x/y values
2AA0D0: 0B 00 ** **
2AA0D1: 01 10 ** **
2AA0D2: 49 02 *********
2AA0E8: 02 03 --button3 nr to select link byte
2AA1FF: 45 49 --button19 xy byte - wrong
2AA200: 30 81 --button19 xy byte - wrong
2AA201: F7 13 --button19 xy byte - wrong
2AA208: 02 01 --button19 nr to select link byte
2AA211: 5D 40 #########
2AA212: 72 10 ## ##
2AA213: 7E 02 ## 20 ## new x/y values
2AA214: 0B 00 ## ##
2AA215: 01 10 ## ##
2AA216: 49 02 #########
2AA223: 8D 8F --button21 xy byte - wrong
2AA224: 71 B1 --button21 xy byte - wrong
2AA225: FF D9 --button21 xy byte - wrong
2AA228: B7 B8 --button21 xy byte - wrong ??
2AA22C: 02 03 --button21 nr to select 'right' pressed byte
________________________________

92 difference(s) found.
23 bytes altered in each NAV pack group.(23*4=92)
_____________________________________________________________________

This probably only makes sense to Dimad, so any questions let me know...Also, a few typo's in my previous post, there are 36 buttons total.

OK, (2Cool..Thanks for the praise...I return the THANKS to you and Dimad for all your continuing GREAT work) If you guys want to manually fix the VOBS, there are 2 ways to do it. First way YANKS, its the old way of using a HEX editor and doing a HEX string replacemant routine, which is even harde due to the deplicate NAV packs for 2 buttons being the same, so lets do it the old VOBedit way.

HOWTO: Well, you have to know how to use VOBedit. If its a moving menu, you have got your work cut out for you. There can be hundreds of NAV packs to manually change..(Thats why Dimad made his app) Basically you will need to open up Vobedit twice, 1 session is the ORIGINAL VOB and the second session is the MenuEdited VOB. Now, adjust the windows so that you can view both of them top and bottom of each other. Here is the boring part....In VOBedit1 and VOBedit2 click the BUTTON checkbox, then click on the first NAV pack, scroll down till you see the button info, you will see the X start and y start byte info of the original buttons and the modified buttons, but check to see if there are some high range buttons in the button 19-36
range these will be the ones that got accidently modified. Check the buttons that you DID NOT deletes X/Y values(The buttons you deleted will have a 1/2 X/Y value, so check the button preceding and after that one), if they now equal the lower range buttons, you have to click on the value and manually type in the old value, this will take forever, cause you have to do this for EVERY NAV PACK...Good Grief....I hope this makes sense to all of you, myself, I will wait for the patch....

Well enjoy, good luck all, and please support Dimad with a few bucks, cause after you do this by hand....He Deserves the dough!

VidHack

[baddbill]

VidHack,

You really seam to have a good working knowledge of editing menus. I'm still having the same problem with menuedit as I stated in an earlier post. I see that you hexedit your menus to modify the commands associated with buttons. Is there a guide on how to do this? I did a search on this forum and on google and didn't find anything. If you know of such a guide can you please direct me there. Or if it isn't too difficult post directions on how to do it here. Any help would be appreciated.

Thanks,
Bill

[VidHack]

Just to put a nail in this problem, and so you can understand whats going on here the specific problem.


Button Data:(using VOBedits button numbering system, Menuedit is -1)

Original VOB x/y values

Button Number X y
1 152/275 192/330
2 443/568 176/329
3 251/473 408/440
19 83/247 192/330
20 471/638 176/329
21 215/511 408/439

After MenuEdit

1 152/275 192/330
2 1/2 1/2 Deleted Button
3 251/473 408/440
19 152/275 192/330 wrong
20 1/2 1/2 Deleted Button counterpart
21 251/473 408/440 wrong

Notice how button 19 and 21 x/y values are really button 1 and 3 values,
this is the error, they should be the same as the original.

VidHack

(to baddbill)If you are familiar with HEXediting tools I will try to post the HEXeditor OLD way, keep in mind though, Dimad app is by far SUPERIOR, its just that bug that will be soon squashed. I will POST later...If I get time....

[baddbill]

Thanks VidHack, I really like how easy menuedit is to use. The problem I have with it is that in my stand alone player (Toshiba) the highlights that let you know which button is selected are either jarbled or gone completely! It is very difficult to navigate a menu when you don't know what button you are on. This problem has occured on every menu I have edited with menuedit except one. It appears that no one else has had this problem so maybe the problem is specific to Toshibas or my particlular model. But until I get a new DVD player or the bug is fixed with menuedit I would like an alternative for editing the "play" button on my second discs that only contain the "extras" and not the movie. Any advice or help would be appreciated.

Thanks,
Bill

[Dimad]

Originally posted by Fmazzanti
Ahh... yes. Thanks for the polite answer.

Sorry, I really did not want to offend anyone.

VidHack, THANKS A LOT for your time and efforts. I've looked through this piece of code before (modification of buttons from other groups) and have not spoted any problems. Now when you pin-pointed the problem I should be able to find it.

Regards

[Fmazzanti]

Originally posted by Dimad
Sorry, I really did not want to offend anyone.

Don't worry, it's ok.
BTW, I've been using your tool from the very beginning and (fortunately) didn't have any of the problems reported here... not a single time. And I've done some 10+ backups since then with MenuEdit intervetion. Guess I've been lucky, but still... I find this tool a blessing.
Thanks for it ;)

[Cayne]

perhaps you only have a 16:9 TV and don't notice it...

[Fmazzanti]

Well yes... my TV is 16:9, but I can still put it in 4:3 mode with black bars at left and right. And it still works...
I've also tested one of these movies in a 4:3 TV and no problem whatsoever. As I said, it may be that I've been lucky.

[Cayne]

perhaps there are also some differences in handling 16:9 between different standalone players.
Could be possible that some use the 16:9 subpic and resize it (like powerdvd does for example) and others need a 4:3 subpic in letterboxed mode...