Schwartzvald
16th July 2012, 07:59
Final Edit: I was converting DVDs to MKV using MakeMKV, and parsing them in Avisynth. I wasn't fully understanding the process, or the tools I was using. When I finally figured out what was going on, it ended up having little to do with audio delay, and more with understanding the MKV container, and how it handles delay by changing a track's starting timecode. So I made a somewhat stupid post in the wrong forum.
What I finally discovered was that MakeMKV seemed to be putting a 67ms delay to the video track (audio delay was variable) when multiplexing the MKV.
The confusion was compounded when I decided to preview the file using FFMS2 in Avisynth. FFMS2 tended to throw away a frame or two (probably when generating the index), which may or may not have had anything to do with the video delay.
Moral of the story--I now use eac3to, MediaInfo and MKVInfo to carefully confirm the delays in MKV tracks before re-authoring. That, and I don't trust FFMS2 to accurate when I use it to preview interlaced MPEG2 in MKV.
What I finally discovered was that MakeMKV seemed to be putting a 67ms delay to the video track (audio delay was variable) when multiplexing the MKV.
The confusion was compounded when I decided to preview the file using FFMS2 in Avisynth. FFMS2 tended to throw away a frame or two (probably when generating the index), which may or may not have had anything to do with the video delay.
Moral of the story--I now use eac3to, MediaInfo and MKVInfo to carefully confirm the delays in MKV tracks before re-authoring. That, and I don't trust FFMS2 to accurate when I use it to preview interlaced MPEG2 in MKV.