From: "Xiang, Haihao" <haihao.xiang-at-intel.com@ffmpeg.org>
To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>,
"Rogozhkin, Dmitry V" <dmitry.v.rogozhkin@intel.com>
Subject: Re: [FFmpeg-devel] [PATCH] lavfi/vf_vpp_qsv: set the right timestamp for AVERROR_EOF
Date: Mon, 20 Mar 2023 02:13:32 +0000
Message-ID: <8ffc08022b536b826958287b42e561d000cf27b4.camel@intel.com> (raw)
In-Reply-To: <2b347b470433a117421d39f22ecf5c5446a34952.camel@intel.com>
On Sa, 2023-03-18 at 00:37 +0000, Rogozhkin, Dmitry V wrote:
> On Fri, 2023-03-17 at 10:38 +0800, Xiang, Haihao wrote:
> > From: Haihao Xiang <haihao.xiang@intel.com>
> >
> > Rescale the timestamp for AVERROR_EOF. This can fix tickets 10261 and
> > 10262.
> >
> > Signed-off-by: Haihao Xiang <haihao.xiang@intel.com>
> > ---
> > libavfilter/vf_vpp_qsv.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/libavfilter/vf_vpp_qsv.c b/libavfilter/vf_vpp_qsv.c
> > index ac77f7bb4b..b4dd7a4191 100644
> > --- a/libavfilter/vf_vpp_qsv.c
> > +++ b/libavfilter/vf_vpp_qsv.c
> > @@ -602,6 +602,7 @@ not_ready:
> > return FFERROR_NOT_READY;
> >
> > eof:
> > + pts = av_rescale_q(pts, inlink->time_base, outlink->time_base);
> > ff_outlink_set_status(outlink, status, pts);
> > return 0;
> > }
>
> This patch works for us and addresses issues reported in
> https://trac.ffmpeg.org/ticket/10261 and
> https://trac.ffmpeg.org/ticket/10262. Please, help to merge.
Pushed and cherry-picked to release/6.0 branch.
Thanks
haihao
_______________________________________________
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".
prev parent reply other threads:[~2023-03-20 2:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 2:38 Xiang, Haihao
2023-03-18 0:37 ` Rogozhkin, Dmitry V
2023-03-20 2:13 ` Xiang, Haihao [this message]
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=8ffc08022b536b826958287b42e561d000cf27b4.camel@intel.com \
--to=haihao.xiang-at-intel.com@ffmpeg.org \
--cc=dmitry.v.rogozhkin@intel.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