Penguin_Factory wrote:If set up correctly, DGIndex will create a *.d2v file and also a *.avs file
It doesn't appear to be working. Does that really matter, though? I've already got the script written out manually.
Including the template for autogenerating scripts was dropped in later versions (or it had only ever been included when installing DGIndex from the AMVapp). It can still be used if you create a template in DGIndex's folder. The documentation talks about this. It's actually possible to autogenerate larger scripts, but for most sources, the MPEG2Source() command is enough.
But no, it's not necessary to redo the script using the template. Just correct the script you've already written if it's actually what's causing the problem.
I was thinking, could the MPEG2Dec3 plugin be out of date or something?
DGIndex is a newer, more advanced version of DVD2AVI, which is why, as you said, it looks similar. DGDecode is a newer, more advanced version of MPEG2Dec3. To quote the official site:
- Code: Select all
DGIndex is baselined off DVD2AVI version 1.77.3. DGDecode is baselined off MPEG2DEC3 1.10.
So yes, MPEG2Dec3 is out of date. It's been out of date for a long time because development is focusing on DGDecode now. The proper course of action is to delete MPEG2Dec3 and DVD2AVI, and replace them with DGIndex and DGDecode. As DGDecode comes packaged with DGIndex, if you always replace the existing versions with the ones you get from the official site, there won't be any mismatched version errors.
Indexing the MPEG2 means opening it ('it' being the .vob/.m2v/.mpg/whatever - MPEG2 is the video format used on DVD) in DGIndex, then using the Save feature to make a d2v file. There are more intricate nuances to it if the MPEG2 is mostly film, but that's the basic gist of what you do.
