From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avutil/opt: add AV_OPT_FLAG_FORCE_CONST
Date: Tue, 16 Apr 2024 02:07:17 +0200
Message-ID: <20240416000717.GE6420@pb2> (raw)
In-Reply-To: <40a79338-4d02-4c69-b69d-f0f0009f6334@rothenpieler.org>
[-- Attachment #1.1: Type: text/plain, Size: 1300 bytes --]
On Sun, Apr 14, 2024 at 10:35:57PM +0200, Timo Rothenpieler wrote:
> On 14.04.2024 22:30, Marton Balint wrote:
> >
> >
> > On Sun, 14 Apr 2024, Timo Rothenpieler wrote:
> >
> > > ---
> > > doc/APIchanges | 3 +++
> > > libavutil/opt.c | 14 ++++++++++++++
> > > libavutil/opt.h | 5 +++++
> > > libavutil/version.h | 2 +-
> > > 4 files changed, 23 insertions(+), 1 deletion(-)
> >
> > Where do you intend to use this flag? So some justification or
> > description of your plans is missing from the commit message.
>
> Some options in nvenc could be greatly simplified with it, where right now
> there's multiple if/switch-trees in the code, just to weed out invalid
> values.
This doesnt feel right.
The code would need to validate the actual value the same way it
checks min/max at least
avoptions allows the user to obtain a parameters address and set
it directly as well as set it without any AVOption
iam still not sure thats a good idea.
Why are the values not in a continous sequence of integers that can
be checked with min/max ?
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
While the State exists there can be no freedom; when there is freedom there
will be no State. -- Vladimir Lenin
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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:[~2024-04-16 0:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-14 19:57 Timo Rothenpieler
2024-04-14 20:30 ` Marton Balint
2024-04-14 20:35 ` Timo Rothenpieler
2024-04-16 0:07 ` Michael Niedermayer [this message]
2024-04-16 8:30 ` Timo Rothenpieler
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=20240416000717.GE6420@pb2 \
--to=michael@niedermayer.cc \
--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