Why can't DGIndex read IFO files directly?

[Dr.Khron]

Having ripped a ton of TV episode DVDs, I agree that there is a need for this functionality... but I don't think it belongs in DGIndex. As Neuron said, DGindex is a general, all purpose program, and the need in question is very specific.

I think what we need is a seperate app, a "ripping front end" that would cordinate DVDD and DGindex together to crank out a series of VOBs, D2Vs, and WAV files that are ready to go. This would be an enormous time saver for ripping TV episodes.

I guess what I'm thinking of would be a modern version of Robot4Rip, which I used to love using with Gknot. Perhaps someone could whip up a R4R for MeGUI?

[Kayaker]

What I do now with episode stuff is ripping once, then selecting VTS and PGC with PGCEdit or VOBBlanker (to really SEE what is in there. The PGC times can lead to confusions ) and the semi automatically run PGCdemux from the original VOBs into new ones.

It's a hard disk waste because you potentially end using double the space with VOBs.

One PGC per directoy.

But you end up with singles VOBs that DGIndex is happy to process. Automatically if you want.

[Guest]

Actually I've tried VS 2005 first, but got some missing direct draw header and read somewhere that they change it or the default location, or something of the sort.

In VS 2003 that header was ok.

But you are talking about you new MPEG-4 is in VS 2005 right ?

Cos the dgindex project is still in old VS 6.0 No, I'm talking about DGMPGDec 1.4.9, which has not had its source code released yet. In fact I am using Visual Studio 2005 Express.

[Kayaker]

I see.
It is in release candidate 2.

When do you think it will be ready ?

[Guest]

I plan to release it early in the week of May 21.