From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 6/9] ffprobe: use AVFrame.duration instead of AVFrame.pkt_duration
Date: Thu, 14 Jul 2022 08:50:04 -0300
Message-ID: <f0dd1aec-21a8-6064-7207-3dc715de91cd@gmail.com> (raw)
In-Reply-To: <165779127304.25016.8703565613875448010@lain.khirnov.net>
On 7/14/2022 6:34 AM, Anton Khirnov wrote:
> Quoting James Almer (2022-07-13 14:39:20)
>> You should probably add new entries to the schema file instead.
>>
>> https://git.videolan.org/?p=ffmpeg.git;a=blob;f=doc/ffprobe.xsd;h=3af621a17ae884adfeacb7cd50c60e1553808188;hb=HEAD#l93
>>
>> Once frame->pkt_duration is gone, ffprobe shouldn't keep printing a
>> frame->duration value as "pkt_duration" and "pkt_duration_time".
>> Also, if frame->duration is supposed to be able to have values other
>> than those we wrote to pkt_duration, maybe keep printing the latter with
>> the existing schema entries until it's all gone (You can use
>> AV_NOWARN_DEPRECATED() to shut compilers up).
>
> Well, the whole idea that values printed by ffprobe should precisely
> mirror the libav* API, up to the field names of our structs, seems quite
> questionable to me, IMO it makes more sense for it to provide a layer of
> abstraction over the libraries. But then again I neither maintain
> ffprobe, nor use it very much, so I wanted to keep changes to a minimum.
> If nobody has other plans for dealing with this then I can certainly
> make the changes you're sugesting.
ffprobe used to print pkt_pts until it was removed, so printing a field
that does not exist (once it's removed) where the new values assigned to
it have potentially slightly different semantics than the old ones does
not seem like a good idea.
_______________________________________________
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:[~2022-07-14 11:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 9:17 [FFmpeg-devel] [PATCH 1/9] lavu/frame: add a duration field to AVFrame Anton Khirnov
2022-07-13 9:17 ` [FFmpeg-devel] [PATCH 2/9] lavc: use AVFrame.duration instead of AVFrame.pkt_duration Anton Khirnov
2022-07-13 9:17 ` [FFmpeg-devel] [PATCH 3/9] lavfi: " Anton Khirnov
2022-07-13 15:02 ` Nicolas George
2022-07-14 8:46 ` Anton Khirnov
2022-07-13 9:17 ` [FFmpeg-devel] [PATCH 4/9] lavf: " Anton Khirnov
2022-07-13 9:17 ` [FFmpeg-devel] [PATCH 5/9] lavd: " Anton Khirnov
2022-07-13 9:17 ` [FFmpeg-devel] [PATCH 6/9] ffprobe: " Anton Khirnov
2022-07-13 12:39 ` James Almer
2022-07-14 9:34 ` Anton Khirnov
2022-07-14 11:50 ` James Almer [this message]
2022-07-18 7:34 ` [FFmpeg-devel] [PATCH] " Anton Khirnov
2022-07-18 8:23 ` Nicolas George
2022-07-18 8:44 ` Anton Khirnov
2022-07-18 11:49 ` James Almer
2022-07-18 11:54 ` Anton Khirnov
2022-07-13 9:17 ` [FFmpeg-devel] [PATCH 7/9] ffmpeg: " Anton Khirnov
2022-07-13 9:17 ` [FFmpeg-devel] [PATCH 8/9] tests/api: " Anton Khirnov
2022-07-13 9:17 ` [FFmpeg-devel] [PATCH 9/9] lavfi/vf_showinfo: print frame durations Anton Khirnov
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=f0dd1aec-21a8-6064-7207-3dc715de91cd@gmail.com \
--to=jamrial@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