From: "\"zhilizhao(赵志立)\"" <quinkblack@foxmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] ffprobe: use pkt->dts to compute interval ts when pts is missing
Date: Tue, 17 Jan 2023 10:57:58 +0800
Message-ID: <tencent_742AB5130DDC4D4B99261F108126EDA7E706@qq.com> (raw)
In-Reply-To: <20230116234141.GB54302@mariano>
> On Jan 17, 2023, at 07:41, Stefano Sabatini <stefasab@gmail.com> wrote:
>
> On date Monday 2023-01-16 11:01:51 +0800, "zhilizhao(赵志立)" wrote:
>>
>>> On Jan 1, 2023, at 03:26, Stefano Sabatini <stefasab@gmail.com> wrote:
>>>
>>> On date Wednesday 2022-07-13 02:02:17 +0200, Stefano Sabatini wrote:
>>>> For some samples the pkt->pts is always missing, use the pkt->dts
>>>> instead.
>>
>> If some pkt->pts is missing but isn’t always missing, isn’t it mixed
>> the use of pts and dts? I don’t have a particular case in mind yet.
>
> In the ticket sample, it was missing all the PTSs, so the only time
> reference was provided by the DTSs (note that this only affects the
> -read_intervals option). I have no better ideas.
Looks like there is no better choices, patch LGTM.
>
>>>>
>>>> Fix trac issue http://trac.ffmpeg.org/ticket/4427.
> _______________________________________________
> 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".
_______________________________________________
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:[~2023-01-17 3:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 0:02 Stefano Sabatini
2022-12-31 19:26 ` Stefano Sabatini
2023-01-15 1:25 ` Stefano Sabatini
2023-01-15 17:05 ` Michael Niedermayer
2023-01-16 3:01 ` "zhilizhao(赵志立)"
2023-01-16 23:41 ` Stefano Sabatini
2023-01-17 2:57 ` "zhilizhao(赵志立)" [this message]
2023-01-25 0:19 ` 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=tencent_742AB5130DDC4D4B99261F108126EDA7E706@qq.com \
--to=quinkblack@foxmail.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