Francesco Romani wrote:
Stefan <[EMAIL PROTECTED]> wrote:
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?
transcode should do this correction automatically, yes.
Hmm... I experimented with some (vob-)files where there was async
detected by transcode. First I extracted without any -D, -M or
--av_fine_ms argument (so transcode should correct the async
automatically as you say) and then added a '-D 0' to disable the
correction. The resulting files did not differ.
I think there was no correction at all because there never was an output
telling '[transcode] A: AV shift ...'.
async detection depends first on source material. Some source material
isn't supported.
I was always using vob-files with PAL 25fps.
So let's assume transcode does not correct anything and/or I force it to
disable any correction with -D 0 and --av_fine_ms 0. Is then the value I
should tell mkvmerge the second one in the output:
[transcode] (probe) suggested AV correction -D 2 (80 ms) | AV 87 ms | 7 ms
'--sync 0:87' or '--sync 0:-87' ?
Thanks for your explanations! I know in most cases nobody would
recognize the shifts but if I /can/ correct this, I would like to do so.
Stefan
