Any cons to using DGIndex on HDTV transport streams?

[mimungr]

I have some HDTV transport stream captures that I want to convert to MPEG-4 using XviD. The Doom9 guide suggests to first use ProjectX to demux and then run DGIndex on the demuxed m2v. However, DGIndex can process the transport stream directly. Are there any cons to using DGIndex directly on the transport stream?

I tried a few tests. Using DGIndex directly seems to be much faster, and the result looks identical. The only advantage I can think of to using ProjectX is that perhaps it handles bitstream corruption better? It seems to have some settings to help maintain A/V sync in the presence of corrupt video or audio frames.

[squid_80]

The only advantage I can think of to using ProjectX is that perhaps it handles bitstream corruption better? It seems to have some settings to help maintain A/V sync in the presence of corrupt video or audio frames.
Exactly. ProjectX can insert silence to keep sync if there are dropouts. It can also demux everything at once, whereas DGIndex only handles one pair of audio/video PIDs.
If you know your HDTV stream is good (I only have experience with DVB-T, there's always a dropout or two) it would be safe to skip using ProjectX.

[nnigam]

I use dgindex when I want to process the whole file. HDTV2MPG2 when I want to cut out commercials. Both work fine for hd streams. I would like to try out ProjectX, but cannot find any instructions for it. I did find a manual for a very old version, but the new version is so vastly different. Most HD streams have multiple channels and I cannot see where to select the stream that I want. I also keep on getting and error saying 'error while decoding frame' so I cannot move to the location where I want the cuts. Any updated manual in english yet?