From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH 4/6] doc/muxers: add mkvtimestamp_v2 Date: Tue, 16 Apr 2024 20:09:19 +0200 Message-ID: <AS8P250MB0744CF9D444E1991F256D8808F082@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM> (raw) In-Reply-To: <Zh658Tie4K5XhQVS@mariano> Stefano Sabatini: > On date Tuesday 2024-04-16 12:50:19 +0200, Andreas Rheinhardt wrote: >> Stefano Sabatini: >>> --- >>> doc/muxers.texi | 8 ++++++++ >>> 1 file changed, 8 insertions(+) >>> >>> diff --git a/doc/muxers.texi b/doc/muxers.texi >>> index f94513527d..490d5557bf 100644 >>> --- a/doc/muxers.texi >>> +++ b/doc/muxers.texi >>> @@ -2933,6 +2933,14 @@ MicroDVD subtitle format muxer. >>> >>> This muxer accepts a single @samp{microdvd} subtitles stream. >>> >>> +@section mkvtimestamp_v2 >>> +mkvtoolnix v2 timecode format muxer. >>> + >>> +Write the PTS rawvideo frame to the output, as supported by the >>> +@command{mkvextact} tool from the @command{mkvtoolnix} suite. >>> + >>> +This muxer accepts a single @samp{rawvideo} stream. >>> + >>> @section mp3 >>> >>> The MP3 muxer writes a raw MP3 stream with the following optional features: >> > >> This is wrong: MKVToolNix switched to "# timestamp format v2" a long >> time ago (we still write the old "# timecode format v2" header); >> furthermore, MKVToolNix actually uses pts (which it reorders to be >> ascending), not dts like our muxer. Furthermore MKVToolNix does not >> force a 1ms precision on timestamps. > > Correct. > > I compared the output of the muxer and of mkvtoolnix extract > timestamp_v2 and I'm not yet clear about the timestamp differences I'm > observing (the muxer output maps with the timestamps, the mkvtoolnix > timestamps differ by a few ms). But I think also mkvtoolnix use a 1ms > timebase. The accuracy of the timestamps output by mkvextract is determined by the TimestampScale of the file in question; it is most often 1ms when the file has video. You need to provide more details if you want these discrepancies to be analyzed. > > Also, IIRC there is no generic way to reorder PTSs, so this might > account for another difference which might be difficult to implement > generically. Write them into a buffer and reorder them at the end? (No, I have no intention to actually implement this. I am rather leaning to "this muxer should not exist".) - Andreas _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2024-04-16 18:44 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-16 8:29 [FFmpeg-devel] Apply misc doc/muxers fixes and extensions Stefano Sabatini 2024-04-16 8:29 ` [FFmpeg-devel] [PATCH 1/6] doc/muxers/matroskaenc: add missing options, apply misc style fixes Stefano Sabatini 2024-04-18 10:06 ` Andreas Rheinhardt 2024-04-16 8:29 ` [FFmpeg-devel] [PATCH 2/6] doc/muxers/md5: apply misc consistency fixes Stefano Sabatini 2024-04-16 8:29 ` [FFmpeg-devel] [PATCH 3/6] doc/muxers: add microdvd Stefano Sabatini 2024-04-16 8:29 ` [FFmpeg-devel] [PATCH 4/6] doc/muxers: add mkvtimestamp_v2 Stefano Sabatini 2024-04-16 10:50 ` Andreas Rheinhardt 2024-04-16 17:48 ` Stefano Sabatini 2024-04-16 18:09 ` Andreas Rheinhardt [this message] 2024-04-18 10:04 ` Stefano Sabatini 2024-04-16 8:29 ` [FFmpeg-devel] [PATCH 5/6] lavf/mkvtimestamp_v2: use name in place of description in long name Stefano Sabatini 2024-04-16 8:29 ` [FFmpeg-devel] [PATCH 6/6] doc/muxers: add mmf Stefano Sabatini
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=AS8P250MB0744CF9D444E1991F256D8808F082@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM \ --to=andreas.rheinhardt@outlook.com \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git