Just checking the dvd files with PgcEdit before burning

[Vaios]

PgcEdit seems to be an amazing tool for dvd authoring. rOIZ really deserves congratulations. Of course I think I’ll never be able to understand and use more than 1/100 of its functions. For now, I thought about using it for checking that the DVD structure and IFO files are correct, before burn.
First of all, it only opens dvd folder, right? It can’t open iso image.
What problems and bugs of DVD Shrink we can check and fix in PgcEdit?
So far I found out about discrepancies in the audio and subtitles streams (if we delete some, the order then is ok? Tried first to change the order and messed it up).
A left over layer break (we search for non seamless flag in the middle, right? the ones at the start and the end is normal and we don’t remove?).
What do you think about the option “filter puos”? Try that too?
Generally if we open the folder and we don’t get any warnings, there should be no serious problem? Just save at the end to leave the 32 k gaps and it should be ok to burn with ImgBurn?
If we burn directly the RipIt4Me exported files? These ones should be cleaner right? The only problem is that it leaves the non seamless flag of layer break?
Any other suggestions and comments?

[blutach]

Well, not quite. PgcEdit is a magnificent authoring and editing package, but it is a long way from being a verifier. It does some basic checks and makes some corrections if needed but it is not a verifier (yet).

Without any disrespect intended for r0lZ, a better "tester" at the moment is DVD Remake Pro, IMO.

Probably the standard in verifiers is the Philips Video Verifier, but most will be dazzled by its output (which will show you that no DVD whatesoever is compliant, according to them)

Regards

[r0lZ]

Thanks Vaios!

To open an ISO with PgcEdit, you must mount it (for example with DaemonTools.) You can inspect the files on the ISO, but you cannot save your changes, as an ISO is read-only.

I would like to add several checks in PgcEdit. It will never been a real verifier, as it's not its goal, but I would like to pinpoint the most common authoring errors. It's not easy to do, though, so, don't expect that soon...