View Single Post
Old 6th December 2009, 17:43   #1283  |  Link
Mosu
MKVToolNix author
 
Mosu's Avatar
 
Join Date: Sep 2002
Location: Braunschweig, Germany
Posts: 4,278
Have you made sure with mkvinfo that the video track timestamps are REALLY not adjusted by that 1024? Because it's working just fine for me:

Quote:
[0 mosu@tionne ~/prog/video/mkvtoolnix/data] mkvmerge -i v.avi
File 'v.avi': container: AVI
Track ID 0: video (DIV3)
Track ID 1: audio (MP3)
[0 mosu@tionne ~/prog/video/mkvtoolnix/data] mkvmerge -o v.mkv --sync 0:1000 v.avi
mkvmerge v2.9.9 ('Tutu') built on Dec 5 2009 19:04:14
'v.avi': Using the AVI demultiplexer. Opening file. This may take some time depending on the file's size.
'v.avi' track 0: Using the video output module.
'v.avi' track 1: Using the MPEG audio output module.
The file 'v.mkv' has been opened for writing.
Progress: 100%
The cue entries (the index) are being written...
Muxing took 0 seconds.
[0 mosu@tionne ~/prog/video/mkvtoolnix/data] mkvinfo -s v.mkv | grep -i 'track 1' | head -n 2
Track 1: video, codec ID: V_MS/VFW/FOURCC (FourCC: DIV3, 0x33564944), default duration: 41.708ms (23.976 fps for a video track), language: und, pixel width: 640, pixel height: 352, display width: 640, display height: 352
I frame, track 1, timecode 1000 (00:00:01.000), size 13424, adler 0x6e3488a8
I can see two possiblities:

1. Your command line is wrong. This could even be the case if you're using mmg; though in that case it would obviously be a bug in mmg.

2. The process is working fine, but playback doesn't honor that 1s offset. In this case there's nothing I can do about it.
__________________
Latest MKVToolNix is v83.0

If I ever ask you to upload something, please use my file server.
Mosu is offline