From: "Tomas Härdin" <git@haerdin.se>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2 1/3] avformat/imfdec: remove the experimental flag
Date: Fri, 06 Jan 2023 16:45:23 +0100
Message-ID: <6ab5b9a6f29ccdbd5165cc53e9c3846c3cefa8f6.camel@haerdin.se> (raw)
In-Reply-To: <20230105232946.21950-1-pal@sandflow.com>
tor 2023-01-05 klockan 15:29 -0800 skrev pal@sandflow.com:
> From: Pierre-Anthony Lemieux <pal@palemieux.com>
>
> ---
> libavformat/imfdec.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavformat/imfdec.c b/libavformat/imfdec.c
> index 03de9ce151..a92686e93b 100644
> --- a/libavformat/imfdec.c
> +++ b/libavformat/imfdec.c
> @@ -1018,7 +1018,7 @@ static const AVClass imf_class = {
> const AVInputFormat ff_imf_demuxer = {
> .name = "imf",
> .long_name = NULL_IF_CONFIG_SMALL("IMF (Interoperable
> Master Format)"),
> - .flags = AVFMT_EXPERIMENTAL | AVFMT_NO_BYTE_SEEK,
> + .flags = AVFMT_NO_BYTE_SEEK,
> .flags_internal = FF_FMT_INIT_CLEANUP,
> .priv_class = &imf_class,
> .priv_data_size = sizeof(IMFContext),
This demuxer is really limited though, right?
/Tomas
_______________________________________________
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-06 15:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 23:29 pal
2023-01-05 23:29 ` [FFmpeg-devel] [PATCH v2 2/3] doc: improve IMF demuxer documentation pal
2023-01-05 23:29 ` [FFmpeg-devel] [PATCH v2 3/3] fate/imfdec: remove imf experimental flag pal
2023-01-06 15:45 ` Tomas Härdin [this message]
2023-01-06 15:50 ` [FFmpeg-devel] [PATCH v2 1/3] avformat/imfdec: remove the " Pierre-Anthony Lemieux
2023-01-06 16:09 ` Tomas Härdin
2023-01-06 16:18 ` Pierre-Anthony Lemieux
2023-02-20 17:55 ` Anton Khirnov
2023-02-20 19:34 ` Pierre-Anthony Lemieux
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=6ab5b9a6f29ccdbd5165cc53e9c3846c3cefa8f6.camel@haerdin.se \
--to=git@haerdin.se \
--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