pgcedit delete uncalled title sets & ifoedit?

[david42]

I was using pgcedit 8.6 to 'delete uncalled title sets' when it ran into a title (that is empty and useless) and popped up a window advising to use ifoedt to fix the problem by changing it to jump to a different title.

I couldn't find out how to use IfoEDit v0.971 (Public Version) to edit the ifo to change the jump to an earlier unused title in the dvd.

Sorry about the poor description of the problem but I'm unfamiliar with ifo's and this is an early attempt on my part to use the 'delete uncalled pgc's and titlesets' features in pgcedit.

I think pgcedit had trouble getting rid of the last title jump on the dvd yet was smart enough to know that the title was never called even though an ifo referenced it.

I'm thinking the pgcedit message to use ifoedit should tell the author of the program more about this problem. Also I wonder if the ifoedit the message told me to use was a legacy version that let editing of the title to use but the ifoedit of today no longer allows that edit. (Or it could just be me...)

Any help will be appreciated.

[r0lZ]

Hum, that's strange, as most references to IfoEdit have been removed from PgcEdit. Could you post the exact content of the error message? (BTW, you can right-click on the error message to copy it in the clipboard.)

Also, note that Delete Uncalled PGCs and Delete Uncalled Titlesets don't remove the PGCs or VTSs that are still called, even if the command that calls the PGC or VTS cannot be executed because it is skipped by a conditional command. Therefore, PgcEdit should not attempt to fix a command, or ask you to do it yourself.

If you need more help, please try to describe exactly what you are doing, and how PgcEdit reacts.

[david42]

Sorry about my slow reply time. When I ran into this problem on 2-3 dvds circa 2007 I was going through dozens of my dvd's to make a owner friendly version to play. The problem is that I forgot which DVD(s) had this problem thus I can't recreate the window pop-up. It seems likely that I was using pgcedit 8.0 or 8.4 when I saw these because 8.6 has more features to deal (automatically) with deleting most of the unused titlesets. I believe that even with these great (8.6) features I still ran into one movie that pgcedit's automatic features had trouble with. If I ever run into this again, I'll take notes and post FYI.

[david42]

Here's a case :
1. Start PgcEdit v8.6 and open video_ts for Vince Vaughn's Wild West Comedy Show.
2. When Find BOV window finishes running PgcEdit generates the following pop-up window :

----------------------------------------------------------
| PgcEdit: Load NAV pack |
|---------------------------------------------------------|
| Error laoding NAV pack from |
| "C:\VINCE_VAUGHNS\VIDEO_TS\VTS_06_3.VOB" |
| at sector 331510 (in file): |
| Nav Pack identifier not valid. |
| The VOB file *may* be CSS encoded: |
| You cannot edit a CSS encoded disc! |
| Or the VOB doesn't match the IFOs: |
| Try to do a mock strip with IfoEdit. |
| |
| Skip remaining 'Bad Nav Pack' error messages |
| ---------------------- ------- ------ |
| | Yes to All domains | | Yes | | No | |
----------------------------------------------------------

A.) What does NAV stand for?

B.) So how does one do a mock strip in IfoEdit? I do not see "mock strip" anywhere in IfoEdit.
Perhaps it's a term dvd authoring engineers use but IfoEdit buttons or boxes are under other names. I have IfoEdit 0.971.

I noticed that VTS6 is special features bonus extras I can live without but am sending this because I'd like to learn how to use IfoEdit to adjust NAV packs. The problem VOB file has IFO & BUF file sizes that are different and rip had errors on this VTS.

[setarip_old]

@david42

Hi!

"Vince Vaughn's Wild West Comedy Show" is a New Line Home Entertainment release. As such, there's a very strong possibility that it contains "XProtect" copy protection. Improper ripping could be the cause of your difficulties.

May I ask what software and procedures you used to rip this DVD?

[Wombler]

There are difficulties with this disc that I've seen discussed elsewhere causing problems with ripping.

There might be a new variant or even possibly a new type of copy protection used on this disc.


Wombler

[blutach]

The NAVPacks are navigation packs and clearly the rip is bad. Strange to see it in a VOB in the middle of a titleset, though.

Mock strip with IfoEdit - http://forum.doom9.org/showthread.php?s=&threadid=84097

Regards

[r0lZ]

Strange to see it in a VOB in the middle of a titleset, though.I've already seen protected sectors in the middle of the movie, at the layer break position. A cell command jumps to the next valid pack, and skips the garbage. Since the protected sectors are evenly distributed on both layers, the end of the last valid pack on L0 is at the same position as the start of the first valid pack on L1, and the layer break works almost as on a standard, non protected DVD, except that it requires a cell command.

[r0lZ]

@david42: PgcEdit displays this dialog when it finds a bad pack of data in the VOBs. The cause might be that the DVD is still CSS protected, or that it contains some protected packs with intentional read-errors. In your case, they are probably intentional bad packs. Ideally, a good ripper should remove or replace them with good sectors. You can try to remove them with FixVTS, as in this case, using IfoEdit is imo not recommended. You can also burn the DVD as it is. With some luck, it will work.

[david42]

I still have trouble navigating around on doom9 so the direct pointer is greatly appreciated.

[r0lZ]

Just process your DVD through FixVTS (http://www.videohelp.com/tools/FixVTS) and try to load it again in PgcEdit.

[david42]

It doesn't matter what software one tries to use to decrypt it. All the usual suspects, that I've heard of (eg. smartripper, dvd decrypter, ripit4me, dvdfab) have been broken. I'm not sure why consumer rights group don't get p'd off that the right to modify something you've purchased has mostly gone the way of the dodo bird.

I'm curious how dvd players manage to sort out this. I've noticed dvd's with multiple files WITH THE SAME FILENAME. I've noticed IFO & BUP's that are different sizes. It's NOT that the
dvd is dirty or scratched, just plain authored and manufactured to restrict copying.

Will consumers have to replace their dvd players to keep up with dvd authoring (tricks) used to (allegedly) prevent pirating? The easiest way to break security is to BRIBE someone who
works on the inside. It's just wrong that innocent consumers have to pay for development and constant upgrading of anti-pirate techniques that are never going to stop cheaters who make fortunes breaking laws; which they apparently care nothing about.

[blutach]

No need to rant david and we all feel the same. Have you done as r0lZ suggests?

Regards

[setarip_old]

@david42I've noticed dvd's with multiple files WITH THE SAME FILENAME. I've noticed IFO & BUP's that are different sizes.You have just described the most apparent part of "XProtect" copy protection, that I alluded to in my first post to this thread.

Thusfar, iterations of this protection have been properly handled by AnyDVD, DVD95CopyPro, DVDFab HD Decrypter, to name a few. If this specific newly released DVD cannot be properly handled TODAY by these programs, wait a few days and they'kll be up to the task ;>}

[Wombler]

It doesn't matter what software one tries to use to decrypt it. All the usual suspects, that I've heard of (eg. smartripper, dvd decrypter, ripit4me, dvdfab) have been broken.

Fengtao released an updated DVDFab HD Decrypter earlier this morning to cope with this title amongst others.

Download the latest version (5.0.3.0) from here (http://www.dvdfab.com/free.htm)and give it a go.


Wombler

[david42]

I wasn't quite sure whether you were asking for me to run FixVTS manually outside of PgcEdit then run PgcEdit; OR let PgcEdit load the video_ts, whine, then run fixvts inside pgcedit; so I tried both.

1. Ran FixVTS (v1.6.0.2 on all vob's outside of pgcedit) then ran pgcedit. Told pgcedit to load video_ts and it popped up a warning window [Verify number of streams (in whole DVD) window title saying 'Warning: There are 6 discrepancies in some VMGM/VTSI_MAT tables. Do you want to run the "Fix number of streams" macro to fix them?' ] So I told it to fix all of them. Then it came up with the aforementioned error loading NAV pack from VTS2_01.VOB pop-up which I dismissed, then it seemed to do ok (except Find BOVs had >7200 cells in VTS_17_1.VOB), then I did my video editing (blankings & kills), ran trace and found VMGM LU5 (Menu) popped-up a window about 'illegal command found, skipping' [The command is "SetSTN Set Audio stream = 0 ; set sub-picture stream = 0 , off"], which doesn't appear to mess up the final dvd in a retail dvd player.

2. Ran Pgcedit and told pgcedit to load video_ts and it popped up a warning window [Verify number of streams (in whole DVD) window title saying 'Warning: There are 6 discrepancies in some VMGM/VTSI_MAT tables. Do you want to run the "Fix number of streams" macro to fix them?' ] So I told it to fix all of them. This time there was NO error loading NAV pack pop-up, then it seemed to do ok (except Find BOVs had >7200 cells in VTS_17_1.VOB), then I did my video edits )blankings & kills), ran trace and found VMGM LU5 (Menu) popped-up a window about 'illegal command found, skipping' [The command is "SetSTN Set Audio stream = 0 ; set sub-picture stream = 0 , off"], which doesn't appear to mess up the final dvd in a retail dvd player.

Both versions of using fixvts played, they just had several titles of the main movie (3 of the 4 were not played). The movie and extras (from vts6) did play ok though. The only other item of mention is that ripit4me dropped some cells that dvdfab retained.

So I guess this means that fixvts, in pgcedit, does seem to be able to correct the NAV pack error. It does seem as though fixing that error does not mean the movie (or full dvd) is actually complete.

What's up with not being able to fix the illegal SetSTN command? I tried but pgcedit wouldn't let me strip the ", off" away on that command. Perhaps there could be a way to spot illegal command syntax and automate stripping out the unknown syntax? Or maybe the 'edit command' choices are missing late editions to the dvd spec for command syntax?

[blutach]

'Warning: There are 6 discrepancies in some VMGM/VTSI_MAT tables. Do you want to run the "Fix number of streams" macro to fix them?' ]
This is a feature that PgcEdit fixes these automatically for you.

What's up with not being able to fix the illegal SetSTN command?
It is not allowed to use a SetSTN command in VMG. To issue one, you need to be in the VTS menu or titles domain.

Perhaps there could be a way to spot illegal command syntax and automate stripping out the unknown syntax?
Doesn't PgcEdit highlight this bad command?

Both versions of using fixvts played, they just had several titles of the main movie (3 of the 4 were not played).
This is an example of some protection systems, as well as legal seamless branching/multi-story authoring.

By the way: Running a program either within or external to PgcEdit should result in the same output (except that FixVTS only runs on a single domain if called from PgcEdit). Your FixVTS is not the last version either. You may wish to upgrade it or use VobBlanker or IfoEdit to mock strip the affected titlesets.

Regards

[setarip_old]

@david42

Just as a point of information, the most recent version of DVD95CopyPro (v.3.9.148) is able to properly process/rip "Vince Vaughn's Wild West Comedy Show"

[david42]

It is not allowed to use a SetSTN command in VMG. To issue one, you need to be in the VTS menu or titles domain. Doesn't PgcEdit highlight this bad command?


PgcEdit does highlight this bad command. I wasn't sure if I could delete that line without undesired side-effect. Is the dvd programming spec available for free, where? Also I'm curious why dvd players don't choke when playing back a dvd that was authored NOT playing by the rules?

[blutach]

No, it isn't. But there are several sites which give the allowed commands, including the one I referenced in post 17 above.

You can delete any illegal command and/or replace it with a NOP without fear of hurting the nav.

Regards

[david42]

No, it isn't. But there are several sites which give the allowed commands, including the one I referenced in post 17 above.

You can delete any illegal command and/or replace it with a NOP without fear of hurting the nav.

Regards
If I delete a command and do not replace it with a NOP, will the nav be hurt?

[blutach]

Not if your options in PgcEdit are set to renumber the GOTOs (default). Trace it thru and see.

Regards

[r0lZ]

But do not remove a cell command, or fix manually the cell commands numbers in the cell table of the PGC.

[david42]

But do not remove a cell command...

If removing cell commands is bad, why not have pgcedit block delete for cell commands?

But do not remove ... or fix manually the cell commands numbers in the cell table of the PGC.

Is the cell table of the PGC found by double clicking on a PGC, in the left pane of PgcEdit, that has a video time >= 0?

[blutach]

Removing useless cell commands is not bad - you just need to know what you're doing. If you remove a cell command, you need to ensure the remaining ones, which are renumbered, are nnumbered appropriatey in the cell table. And yes, double click on a PGC with video to see and edit this table, along with other info about the PGC.

Anyway, the new version of PgcEdit will have a new feature that automatically deletes useless cell commands.

Regards