phin
14th March 2005, 00:59
My audio seems to be about 1 second ahead of the video and appears to be consistent throughout the timeline. Here are the steps I'm using:
- Rip VOB files using DVD Decrypter
- Load 2 VOB files into DGIndex
- Set Field Operation to None since it's NTSC
- Save d2v project
- Create a simple avs file that uses LoadPlugin and mpeg2source
- Compress the AC3 file to MP3 (CBR) using BeLight
- Open the avs file in VirtualDubMod
- Add the MP3 file as an audio stream
- Set video compression to Divx5 (default settings)
- Choose Fast Recompress
- Save the avi file
The audio is always 1 second ahead of the video regardless if I:
- Use Divx or Xvid
- Use CBR or VBR MP3 settings in BeLight
- Use Fast Compress or Full Processing Mode
- Save Project and Demux Video in DGIndex and process the m2v file in VirtualDubMod instead of creating an avs file.
Note: The generated AC3 filename indicates there is a 0 ms delay so I've not applied an offset in BeLight.
Edit: I've tried both version 1.2.1 and the latest beta of DGIndex.
My questions are, Is this a common problem? Am I doing something wrong in my steps? Is the obvious answer just to apply an 1000 ms offset in BeLight? Is there an alternative to DGIndex for this process?
I'll greatly appreciate any advice you guys can give me.
- Rip VOB files using DVD Decrypter
- Load 2 VOB files into DGIndex
- Set Field Operation to None since it's NTSC
- Save d2v project
- Create a simple avs file that uses LoadPlugin and mpeg2source
- Compress the AC3 file to MP3 (CBR) using BeLight
- Open the avs file in VirtualDubMod
- Add the MP3 file as an audio stream
- Set video compression to Divx5 (default settings)
- Choose Fast Recompress
- Save the avi file
The audio is always 1 second ahead of the video regardless if I:
- Use Divx or Xvid
- Use CBR or VBR MP3 settings in BeLight
- Use Fast Compress or Full Processing Mode
- Save Project and Demux Video in DGIndex and process the m2v file in VirtualDubMod instead of creating an avs file.
Note: The generated AC3 filename indicates there is a 0 ms delay so I've not applied an offset in BeLight.
Edit: I've tried both version 1.2.1 and the latest beta of DGIndex.
My questions are, Is this a common problem? Am I doing something wrong in my steps? Is the obvious answer just to apply an 1000 ms offset in BeLight? Is there an alternative to DGIndex for this process?
I'll greatly appreciate any advice you guys can give me.