Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] vvcdec: Mark as experimental
Date: Wed, 13 Mar 2024 18:34:20 -0300
Message-ID: <969f5344-d252-4737-82ca-260aeade59a9@gmail.com> (raw)
In-Reply-To: <CAK+ULv59tq6CN0XyVVRQP+Uwpqz+ghT8ffBfm_y7cTLW103tQA@mail.gmail.com>

On 2/14/2024 10:41 AM, Kieran Kunhya wrote:
> On Wed, 14 Feb 2024 at 11:47, Andreas Rheinhardt <
> andreas.rheinhardt@outlook.com> wrote:
> 
>> Kieran Kunhya:
>>>  From 15c9311c49ebbe87fc4517b67cb73b3079ec3510 Mon Sep 17 00:00:00 2001
>>> From: Kieran Kunhya <kierank@obe.tv>
>>> Date: Wed, 7 Feb 2024 21:10:08 +0000
>>> Subject: [PATCH] vvcdec: Mark as experimental
>>>
>>> ---
>>>   libavcodec/vvc/vvcdec.c | 2 +-
>>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/libavcodec/vvc/vvcdec.c b/libavcodec/vvc/vvcdec.c
>>> index 8163b5e..e0554c6 100644
>>> --- a/libavcodec/vvc/vvcdec.c
>>> +++ b/libavcodec/vvc/vvcdec.c
>>> @@ -1011,7 +1011,7 @@ const FFCodec ff_vvc_decoder = {
>>>       .close          = vvc_decode_free,
>>>       FF_CODEC_DECODE_CB(vvc_decode_frame),
>>>       .flush          = vvc_decode_flush,
>>> -    .p.capabilities = AV_CODEC_CAP_DR1 | AV_CODEC_CAP_DELAY |
>> AV_CODEC_CAP_OTHER_THREADS,
>>> +    .p.capabilities = AV_CODEC_CAP_DR1 | AV_CODEC_CAP_DELAY |
>> AV_CODEC_CAP_OTHER_THREADS | AV_CODEC_CAP_EXPERIMENTAL,
>>>       .caps_internal  = FF_CODEC_CAP_EXPORTS_CROPPING |
>> FF_CODEC_CAP_INIT_CLEANUP |
>>>                         FF_CODEC_CAP_AUTO_THREADS,
>>>       .p.profiles     = NULL_IF_CONFIG_SMALL(ff_vvc_profiles),
>>
>> Did you run FATE with that? If I am not mistaken, all the VVC decoding
>> tests (and probably also tests where the VVC decoder is only used to get
>> stream parameters) will fail (in avcodec_open2()) now, because
>> strict_std_compliance does by default not allow experimental codecs.
>>
> 
> I am aware, it was more to see if there were any objections to the FOSDEM
> decision to make it experimental.
> 
> Kieran

I'll apply this patch soon (with the addition of forcing the vvc decoder 
and -strict experimental for the tests).
_______________________________________________
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".

      reply	other threads:[~2024-03-13 21:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07 21:13 Kieran Kunhya
2024-02-07 22:06 ` Paul B Mahol
2024-02-07 22:55   ` Kieran Kunhya
2024-02-08  6:00     ` Nuo Mi
2024-02-08 18:16       ` Kieran Kunhya
2024-02-09  3:54         ` Nuo Mi
2024-02-13  2:56           ` Nuo Mi
2024-02-14  2:57             ` Nuo Mi
2024-02-14  9:41               ` Kieran Kunhya
2024-03-14 22:54     ` Michael Niedermayer
2024-03-15 10:22       ` Kieran Kunhya
2024-03-15 15:00         ` Frank Plowman
2024-03-15 15:04           ` Andreas Rheinhardt
2024-03-16 14:50             ` Nuo Mi
2024-03-16 14:49           ` Nuo Mi
2024-02-14 11:49 ` Andreas Rheinhardt
2024-02-14 13:41   ` Kieran Kunhya
2024-03-13 21:34     ` James Almer [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=969f5344-d252-4737-82ca-260aeade59a9@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