From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avfilter/vf_libvmaf: update filter for libvmaf v2.0.0
Date: Fri, 24 Dec 2021 21:54:21 +0100
Message-ID: <e3bc1bd1-9af6-71dc-c2b5-b5ad4c4bfa99@rothenpieler.org> (raw)
In-Reply-To: <CALbjROK0dZq0oQyh8eZHJb5D2yo7bUB-bnoD55L00zcS8EJ+Tg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 745 bytes --]
On 24.12.2021 21:51, Kyle Swanson wrote:
> Hi,
>
> Never followed through on this vf_libvmaf patch from last June, and
> I've had several people asking about its status lately. Rebased patch
> attached. It's been a while, so I guess let's start the review again.
> Would be nice if we could get this in before 5.0.
>
> Thanks,
> Kyle
>
> On Wed, Jun 30, 2021 at 6:55 AM Moritz Barsnick <barsnick@gmx.net> wrote:
>>
>> Hi,
>>
>>> -enabled libvmaf && require_pkg_config libvmaf "libvmaf >= 1.5.2" libvmaf.h compute_vmaf
>>> +enabled libvmaf && require_pkg_config libvmaf "libvmaf >= 2.0.0" libvmaf.h vmaf_init
The primary question remains.
Is dropping <2.0 support okay, when there's distros out there not having
2.0 yet?
[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4494 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:[~2021-12-24 20:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALbjROLP4=3xmpvM8EW1A3fA4==oo=YpK+vjeB-ueoQSpomoKA@mail.gmail.com>
[not found] ` <CALbjROJOuyUN8gL6eJ2KGHQV4VRQ5-kcdkOUNg2SC8L4wF-hUA@mail.gmail.com>
[not found] ` <YNx3sBpzP3r6p++p@sunshine.barsnick.net>
2021-12-24 20:51 ` Kyle Swanson
2021-12-24 20:54 ` Timo Rothenpieler [this message]
2021-12-31 1:01 ` Kyle Swanson
2021-12-25 9:24 ` Paul B Mahol
2021-12-31 1:03 ` Kyle Swanson
2022-01-02 18:24 ` Kyle Swanson
2022-01-03 5:21 ` Andreas Rheinhardt
2022-01-03 22:32 ` Kyle Swanson
2022-01-08 22:08 ` Kyle Swanson
2022-01-10 18:22 ` Andreas Rheinhardt
2022-01-14 2:38 ` Kyle Swanson
2022-01-19 18:23 ` Kyle Swanson
2022-01-20 21:06 ` Kyle Swanson
2022-01-23 21:22 ` Kyle Swanson
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=e3bc1bd1-9af6-71dc-c2b5-b5ad4c4bfa99@rothenpieler.org \
--to=timo@rothenpieler.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