From: Stefano Sabatini <stefasab@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 2/3] lavf/mkvtimestamp_v2: review implementation to match mkvextract behavior Date: Sat, 20 Apr 2024 18:56:45 +0200 Message-ID: <ZiPzzRuEjXkWprlx@mariano> (raw) In-Reply-To: <AS8P250MB074437D5B61645309C3C25588F0C2@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM> On date Saturday 2024-04-20 18:47:58 +0200, Andreas Rheinhardt wrote: > Stefano Sabatini: > > On date Saturday 2024-04-20 15:18:39 +0200, Andreas Rheinhardt wrote: > >> Stefano Sabatini: > >>> Harmonize internal implementation with the mkvextract behavior: > >>> - print PTS in place of DTS values > >>> - ignore NOPTS values > >>> - sort PTS values > >>> --- > >>> libavformat/mkvtimestamp_v2.c | 69 +++++++++++++++++++++++++++++++++-- > >>> 1 file changed, 65 insertions(+), 4 deletions(-) [...] > >> 3. I still don't think that this muxer should exist at all. > > > > I tend to agree. But: > > > > We don't really know why this weird muxer was added, today we have > > better tools for that (we could use ffprobe, or even a bitstream > > filter similar to showinfo to get the same result), but if it was > > added probably there was a reason. So my plan is to make the format a > > bit more useful (DTS => PTS+sort), and possibly deprecate it and point > > to better available tools and drop this in two major releses. > > > > I don't think the point of the format was to really make the behavior > > exactly equal to mkvextract, the thing with TimeScale is probably not > > very important, at least for the original author that was not really > > an issue, he was probably only looking for some way to dump timestamps > > and took free inspiration from mkvtoolnix. > > > > This thing has been added in 1c5670dbb204369477ee1b5d967f9e8b4f4a33b8. I > can't find any discussion in the mailing list archives for this, but the > file description was "extract pts as timecode v2, as defined by > mkvtoolnix" at the time. Furthermore, its author is the one who started > the Matroska muxer. So I think its aim was really to mimic mkvextract. > (I am not certain wrt MKVToolNix handling of fractional millisecond; old > versions of mkvextract may really have simply rounded/truncated to > milliseconds.) > > > If this is true, we might point that this format is not exactly > > equivalent to timestamp_v2 in the doc. > > Which makes this thing even more pointless. I'm not against removing this muxer, but it is something we should do? Removing a working component (even if suboptimal) even without deprecation. Probably if there is agreement about this, especially given that there are better alternatives at this time. If not, I can fix the missing bits so we have a better implementation, but we might want to deprecated and drop later. _______________________________________________ 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-20 16:56 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-20 11:48 [FFmpeg-devel] lavf/mkvtimestamp_v2: review mkvtimestamp_v2 implementation, add documentation Stefano Sabatini 2024-04-20 11:48 ` [FFmpeg-devel] [PATCH 1/3] lavf/mkvtimestamp_v2: use name in place of description in long name Stefano Sabatini 2024-04-20 11:48 ` [FFmpeg-devel] [PATCH 2/3] lavf/mkvtimestamp_v2: review implementation to match mkvextract behavior Stefano Sabatini 2024-04-20 13:18 ` Andreas Rheinhardt 2024-04-20 16:00 ` Stefano Sabatini 2024-04-20 16:47 ` Andreas Rheinhardt 2024-04-20 16:56 ` Stefano Sabatini [this message] 2024-04-22 13:55 ` Stefano Sabatini 2024-04-22 16:48 ` Andreas Rheinhardt 2024-04-20 11:48 ` [FFmpeg-devel] [PATCH 3/3] doc/muxers: add mkvtimestamp_v2 Stefano Sabatini 2024-04-20 11:53 ` 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=ZiPzzRuEjXkWprlx@mariano \ --to=stefasab@gmail.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