From: "Xiang, Haihao" <haihao.xiang-at-intel.com@ffmpeg.org>
To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] FFmpeg patch to add idr_interval option to libavcodec/qsvenc_mpeg2.c
Date: Tue, 12 Jul 2022 10:23:32 +0000
Message-ID: <7cb937b21730146001dd5210e5229fd229896954.camel@intel.com> (raw)
In-Reply-To: <SJ0P221MB082058614B556CEC2931CBB6EEB89@SJ0P221MB0820.NAMP221.PROD.OUTLOOK.COM>
On Tue, 2022-06-28 at 15:26 +0000, Greg Stewart wrote:
> Hello,
>
> Please find attached a base64 encoded patch. This patch exposes the
> "idr_interval" option to the mpeg2_qsv encoder (libavcodec/qsvenc_mpeg2.c)
> identically to how was done for the h264_qsv encoder
> (libavcodec/qsvenc_h264.c).
For mpeg2, `IdrInterval` in the SDK defines the sequence header interval, not
IDR frame interval [1]. Could you update the help string for this option and add
a description about this option in mpeg2_qsv section in encoders.texi ?
[1]
https://github.com/Intel-Media-SDK/MediaSDK/blob/master/doc/mediasdk-man.md#mfxinfomfx
Thanks
Haihao
>
> Thank you,
>
> Greg Stewart
> greg.stewart@edisen.com
> _______________________________________________
> 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".
prev parent reply other threads:[~2022-07-12 10:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SJ0P221MB08206B0737FA743F06E0F834EEB99@SJ0P221MB0820.NAMP221.PROD.OUTLOOK.COM>
2022-06-28 15:26 ` Greg Stewart
2022-07-12 10:23 ` 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=7cb937b21730146001dd5210e5229fd229896954.camel@intel.com \
--to=haihao.xiang-at-intel.com@ffmpeg.org \
--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