TimeStamp Correction Incompetence
|Reported by:||ilkertezcan||Owned by:|
|Blocking:||Reproduced by developer:||no|
|Analyzed by developer:||no|
While FFmpeg can reduce the file size to only certain amount of downloaded real data by triming gap bytes in the played audio / video files, The output (remux) file's the timestamp remains same with the original file.
ffmpeg -i ElephantsDream_only_a_few_scenes.mkv -c:a copy -c:v copy Remuxed.mkv
FFmpeg's report: https://paste.ee/r/5Zwci
ElephantsDream_only_a_few_scenes.mkv's file-size: 193 MB
Remuxed.mkv's file-size: 23 MB
FFmpeg is deprived of timestamp correction but MEncoder isn't. How can MEncoder can manage things while FFMpeg cannot?
MEncoder ElephantsDream_only_a_few_scenes.mkv -ni -ovc copy -oac copy -fafmttag 0x706D -of lavf -lavfopts format=mkv -o Corrected_by_MEncoder.mkv
MEncoder's report: https://paste.ee/r/LzO4M
Corrected_by_MEncoder.mkv's new timestamp:
Also, The Meteorite Project (A MKV Repair Engine) software able to correct timestamp. (But Meteorite has its own issue which it has stuck at final stage -99%-. Order to overcome this, it will be necessary to re-mux the sample file with FFmpeg-3.1.5. In later versions of FFmpeg-3.1.5, the Meteorite directly crash without fix to the file).
The sources codes of Meteorite CLI version (I think, Meteoirite.cpp & MeteoireCLI.cpp files is enough):
FFmpeg -i ElephantsDream_only_a_few_scenes.mkv -c:a copy -c:v copy ElephantsDream_only_a_few_scenes-ffmpeg-3-1-5-remuxed.mkv Meteoritecli ElephantsDream_only_a_few_scenes-ffmpeg-3-1-5-remuxed.mkv
Meteorite's report: https://paste.ee/r/VJWCS
(Download for final fixed file):