Hi,

I have experimented a time now with transcode and mkvmerge, but I did
not find out, what exactly the output

> [transcode] (probe) suggested AV correction -D 2 (80 ms) | AV 87 ms | 7 ms

(or similar values) is trying to tell me.
I guess, the audiostream begins 80ms too early (or too late?) and the
videostream 7ms, leading to a difference of 80ms. Does this mean, I have
to add an offset of 80ms (or -80ms? or ±7ms?) when merging these
streams? Or does the output mean, that transcode corrects the streams
automatically and I do not have to bother anymore?

I recognized, sometimes (why not every time when an async is detected?)
transcode seems to correct these shifts, when something like

> [transcode] A: AV shift         | -1891 ms [ -47 (A) | -11 ms ]

appears (I did not use any -D or -M argument then). With one file I
could not merge the resulting ac3-file with mkvmerge, because it did not
find the ac3-header. So I had to disable this with the '-D 0' argument,
but then again, sometimes there still is (with -D 0) a (different) shift
made by transcode. What is the difference between -D and --av_fine_ms ?

I would be happy if someone could explain to me these values and
transcode's behavior. And finally I want to know, what in the end the
offset of the audio and video stream is which I then can give to mkvmerge.

Thanks in advance.

Stefan


Reply via email to