From: Stefano Sabatini <stefasab@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: Nil Fons Miret <nilf@netflix.com>, Kyle Swanson <kswanson@netflix.com> Subject: Re: [FFmpeg-devel] [PATCH] doc/filters: expand documentation on libvmaf filter Date: Sun, 10 Dec 2023 01:28:53 +0100 Message-ID: <ZXUGRWi3oKjOXto4@mariano> (raw) In-Reply-To: <CAPf3GFnSQKNR=iY4GzB8M95W_0xA79UVxgrnYhCi3ZHoMgiu5Q@mail.gmail.com> On date Friday 2023-12-08 18:47:28 +0000, ffmpeg-devel Mailing List wrote: > Attached. > From e2b98c2dec1248f5000a9291bd6f1177de2a4d0f Mon Sep 17 00:00:00 2001 > From: nilfm <nilf@netflix.com> > Date: Fri, 8 Dec 2023 14:28:12 +0000 > Subject: [PATCH] doc/filters: expand documentation on libvmaf filter > > Signed-off-by: nilfm <nilf@netflix.com> > --- > doc/filters.texi | 26 ++++++++++++++++++++------ > 1 file changed, 20 insertions(+), 6 deletions(-) > > diff --git a/doc/filters.texi b/doc/filters.texi > index 6d00ba2c3f..232bd6405b 100644 > --- a/doc/filters.texi > +++ b/doc/filters.texi > @@ -16929,19 +16929,33 @@ The first input is the distorted video, and the second input is the reference vi > > The obtained VMAF score is printed through the logging system. > > -It requires Netflix's vmaf library (libvmaf) as a pre-requisite. > +It requires Netflix's VMAF library (libvmaf) as a pre-requisite. > After installing the library it can be enabled using: > @code{./configure --enable-libvmaf}. > > -The filter has following options: > +The filter has the following options: > > @table @option > @item model > -A `|` delimited list of vmaf models. Each model can be configured with a number of parameters. > +A `|` delimited list of VMAF models. Each model can be configured with the following parameters: This is still ambiguous since it is not defining how the parameters must be specified. IIUC it should be: Each model can be configured with a sequence of key=value parameters, separated by @code{:}. Note that the @code{:} characters is special and needs to be escaped. The following parameters are supported: [...] While at it, it might be good to extend the options with a "models" alias to clarify plurality. > +@table @option > +@item version > +Built-in model version. Example: @code{vmaf_v0.6.1}. > +@item name > +Name that will be associated with this model in the output logs. > +@item path > +Path to a model in the local filesystem. > +@item enable_transform > +If true, a model-defined transform will be applied to the final score. Default value: @code{false}. > +@item disable_clip > +If true, model-defined score clipping will be disabled. Default value: @code{false}. > +@end table > Default value: @code{"version=vmaf_v0.6.1"} > > @item feature > -A `|` delimited list of features. Each feature can be configured with a number of parameters. > +A `|` delimited list of features. Each feature can be configured with a number > +of parameters. The parameter @code{name} should be set to the name of the > +feature. Other key-value parameter pairs will be passed in to the feature extractor. ditto > > @item log_path > Set the file path to be used to store log files. > @@ -16982,9 +16996,9 @@ ffmpeg -i distorted.mpg -i reference.mpg -lavfi libvmaf='model=version=vmaf_v0.6 > @end example > > @item > -Example with multiple additional features: > +Example with multiple additional features and feature options: > @example > -ffmpeg -i distorted.mpg -i reference.mpg -lavfi libvmaf='feature=name=psnr|name=ciede' -f null - > +ffmpeg -i distorted.mpg -i reference.mpg -lavfi libvmaf='feature=name=psnr\\:enable_mse=true|name=ciede' -f null - > @end example looks good otherwise _______________________________________________ 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-12-10 0:29 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-08 18:47 Nil Fons Miret via ffmpeg-devel 2023-12-10 0:28 ` Stefano Sabatini [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=ZXUGRWi3oKjOXto4@mariano \ --to=stefasab@gmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=kswanson@netflix.com \ --cc=nilf@netflix.com \ /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