From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avfilter: add libvmaf_cuda
Date: Thu, 21 Sep 2023 00:54:48 +0200
Message-ID: <aea416f1-e377-411b-a31a-02bf0e2efeae@rothenpieler.org> (raw)
In-Reply-To: <CALbjROKgfMt7PHXy6=EBf7MU4Znm-ov5toDaSHNLYa2p6eSV+g@mail.gmail.com>
On 20.09.2023 22:06, Kyle Swanson wrote:
> Hi,
>
> On Mon, Sep 18, 2023 at 2:39 PM Kyle Swanson <k@ylo.ph> wrote:
>>
>> Hi,
>>
>> On Mon, Sep 18, 2023 at 12:41 PM Timo Rothenpieler
>> <timo@rothenpieler.org> wrote:
>>> On 18.09.2023 21:21, Marvin Scholz wrote:
>>>> I am far from an expert with the configure script but won't that cause --enable-libvmaf to fail when
>>>> libvmaf is built without cuda support? Which seems undesirable to me…
>>>
>>> Yeah, hence my suggested change of
>>>
>>>> enabled libvmaf_cuda && require_pkg_config libvmaf_cuda "libvmaf >= 2.0.0" libvmaf_cuda.h vmaf_cuda_state_init
>>
>> This only works if I add `libvmaf_cuda` to EXTERNAL_LIBRARY_LIST,
>> otherwise running `./configure --enable-libvmaf-cuda` will fail with
>> `Unknown option "--enable-libvmaf-cuda".` I'm not sure that's the
>> right thing to do given there is no such thing as `libvmaf_cuda`. If
>> you are aware of a different way of handling this, let me know. Most
>> of the other libraries we link with optional configurations (see
>> libopus, libvpx, ...) seem to have the pattern I used in this previous
>> patch [0], which does avoid the problem pointed out by Marvin.
>>
>> Thanks,
>> Kyle
>>
>> [0] http://ffmpeg.org/pipermail/ffmpeg-devel/2023-September/314409.html
>
> Timo, any NAKs regarding this earlier patch? If you're at VDD this
> week, maybe we can chat about it if you'd like.
The only remaining issue is the configure situation really.
No other obvious issues from my side.
It definitely needs to be sorted out properly.
Either configure needs to treat libvmaf_cuda like it is an entirely
independent library (it's being added to --help output after all, which
indicates to me that this is the intended approach).
Or it needs to be a sub-feature of libvmaf, where if libvmaf is enabled,
support for CUDA is checked for, and then the vmaf_cuda filter needs to
depend on that check.
All current patches had some kind of mix between the two.
_______________________________________________
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-09-20 22:55 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 17:50 Kyle Swanson
2023-08-14 16:29 ` Kyle Swanson
2023-08-14 17:09 ` Timo Rothenpieler
2023-08-23 20:39 ` Kyle Swanson
2023-08-28 18:54 ` Kyle Swanson
2023-08-28 18:59 ` Timo Rothenpieler
2023-08-28 20:16 ` Kyle Swanson
2023-08-29 17:09 ` Kyle Swanson
2023-08-29 22:14 ` Andreas Rheinhardt
2023-08-30 16:44 ` Kyle Swanson
2023-08-31 18:39 ` Kyle Swanson
2023-09-05 17:16 ` Kyle Swanson
2023-09-11 17:53 ` Kyle Swanson
2023-09-11 18:51 ` Timo Rothenpieler
2023-09-14 18:59 ` Kyle Swanson
2023-09-14 19:10 ` Timo Rothenpieler
2023-09-15 20:31 ` Kyle Swanson
2023-09-15 22:33 ` Timo Rothenpieler
2023-09-18 16:42 ` Kyle Swanson
2023-09-18 19:21 ` Marvin Scholz
2023-09-18 19:41 ` Timo Rothenpieler
2023-09-18 21:39 ` Kyle Swanson
2023-09-20 20:06 ` Kyle Swanson
2023-09-20 22:54 ` Timo Rothenpieler [this message]
2023-09-23 9:50 ` Kyle Swanson
2023-09-23 11:02 ` Timo Rothenpieler
2023-09-25 12:18 ` Kyle Swanson
2023-09-25 16:09 ` Timo Rothenpieler
2023-09-27 17:26 ` Kyle Swanson
2023-08-28 19:05 ` Paul B Mahol
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=aea416f1-e377-411b-a31a-02bf0e2efeae@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