View Full Version : DGIndex Question re AVI
ron spencer
23rd June 2005, 17:24
Have not played with this tool for quite some time now...so I tried the latest verision...I noted that the Save AVI option is now gone....just curious as to why it is not there anymore...I guess the only way to save the avi is to opne the D2V project in Virtualdub?
On a related note, is the new DVD2AVI ok for this as well?
Guest
23rd June 2005, 17:30
Two reasons:
1. The Save AVI code was not updated to support > 2GB files.
2. All the MPEG2 fixes for the frame loss issue, etc., are implemented in DGDecode and are not retrofitted to DGIndex.
Yes, you need to serve into VirtualDub and make your AVI from there.
jackei's latest DVD2AVI presumably can still save AVI's but I assume is still limited to 2GB files.
ron spencer
23rd June 2005, 18:33
thanks for the history update on this....yes the 2 gig limit is still present in the new DVD2AVI
so all I need to do in DGIndex is to save the project (WAV is made), and then take the d2v into VFAPI to make a "fake" avi and then open this avi in virtualdub? does this method take advantage of the fixes in dgdecode....
or do I need avisynth to load the dgdecode dll first and then open the avs in virtualdub?
thanks
Guest
23rd June 2005, 18:38
You can use DGVfapi but the better route is using DGDecode through an Avisynth script. Don't be scared of Avisynth. It's really powerful and is clearly described in the Quick Start guide in the 1.3.0 distribution. That will give you full access to the power of Avisynth scripting as well as the features of MPEG2Source that are not available through VFAPI.
Cyberia
23rd June 2005, 20:33
There are also examples for AviSynth in the DGDecode manual. ;)
ron spencer
24th June 2005, 03:56
you bet I saw them!!!!
Up and running again...are there any "must use" virtual dub filters for going from DVDtoAVI....bear with me as it has been a year since I did all this...fun as I remember!!!! I am already at 720x480 so no need to resize
Guest
24th June 2005, 04:09
1. Generally, Avisynth filtering is preferred. It's faster, more versatile, and can allow you to encode completely without color space conversions.
2. Don't contract filteritis! If you don't see anything that demands correction, then don't filter.
3. If the DVD is NTSC and the content is film, you will want to either use Force Film in DGIndex, or perform IVTC, using for example Decomb. One of the biggest mistakes is to perform simple deinterlacing of 3:2 pulled-down material.
ron spencer
24th June 2005, 15:38
I am hoping not to get filteritis....but having not used it for some time I am, well, anxious to try some stuff.
I do not remember the color space issues going to VirtualDub specifically...what exactly are they? Can you use AVISynth to stop this somehow? I just like VirtualDub as I can see a before and after effect of a filter.
thanks for your DGIndex, etc. software
-ron
Guest
24th June 2005, 16:24
VirtualDub filtering works in RGB only.
If your Avisynth script delivers YV12 you can pass that directly to the codec using Fast Recompress, thereby avoiding conversion to RGB and back.
You can see before and after with Avisynth filtering by serving the script with and without the filter into separate VirtualDub instances. Not quite as convenient, I'll grant you, but workable. That's what I do when I need to.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.