Replacing cells with blanks using Menuedit, why does does IFOEdit change the vob?

[Matthew]

I followed the guide on the menuedit page to replace an unwanted still picture (no buttons) with a blank. [Menuedit 2.3, registered version].

Then I used IFOEdit as per instructions to generate new IFOs. It wrote a new menu vob which is not required according to the guides. However, it was different (same size but the files don't compare okay).

If the menuedit-produced file is all a-ok, why was it modified by IFOEdit?

Thanks :)

[2COOL]

Originally posted by Matthew
I followed the guide on the menuedit page to replace an unwanted still picture (no buttons) with a blank. [Menuedit 2.3, registered version].I assume you mean this guide from the MenuEdit Q&A sticky.

IV) There is a logo/intro/warning screen on your DVD you want to get rid of.

Problem: You can't simply delete these and still have valid DVD structure (playable DVD).
Solution: Using MenuEdit one can easily find vob/cell containing unwanted material and replace it with empty cell (a cell that has only few blank frames). To get such empty cell just open smallest .vob file in your VIDEO_TS directory - most probably it is the one. MenuEdit changes only .vob file, so corresponding ifo file should be adjusted after that as well. Using IfoEdit one can do it with few mouse clicks. Full step by step procedure (with screenshots) can be found here (http://menuedit.dimad.net/ht_me_replace_cell.html).

If the menuedit-produced file is all a-ok, why was it modified by IFOEdit?IfoEdit fixes the sectors in the VOB and updates the IFOs with corrected sector values. If the cell you replaced is the same exact size in bytes with the old ones, you probably don't need to strip the VOB but just get VTS Sectors. But just in case, you should always do the post mock strip method after replacing any cells. ;)

[Matthew]

Thanks for the reply, you seem like a god in these matters =)

Didn't read that part of the sticky, but I did happen to use the linked guide at http://menuedit.dimad.net :/

I suspect I didn't make myself clear. The vob produced by MenuEdit is not the same size as the original. Anyway, I used IFOEdit to produce a new IFO for the MenuEdit-outputted vob, but IFOEdit also outputs its own menu vob. The guide says only the IFOs need to be copied across, not the new menu vob created by IFOEdit. But if this new menu vob outputted by IFOEdit is obsolete, one would expect it to be the same as MenuEdit's, but it's not (although it is the same size). So I'm confused about that. It's as if maybe MenuEdit doesn't fix the menu vob properly as the guide claims.

Thanks :)

[Dimad]

Originally posted by Matthew
It's as if maybe MenuEdit doesn't fix the menu vob properly as the guide claims.

MenuEdit modifies everything in vob files needed for correct playback. It does not remove "prohibited user operations" from them. IfoEdit can also keep these intact, but by default it will remove them. I guess that is what make files different.

[Matthew]

Thanks for the reply.

I just did a test - the VIDEO_TS.VOB contained one video with no buttons (nothing else) and I replaced it with a single black frame.

Via a process of elimination, I found the only "VOB EXPERT" option in IFOEdit that led to the vob being altered was "Adjust Audio/Subp point." If that was unchecked then the vob was unaltered by IFOEdit.

The P-UOps thing may simply not apply to this particular vob file so I'm not saying that explanation is invalid, but I am interested in what the "Adjust Audio/Subp point." thing is about. It sounds like it could actually matter.