From: Timo Rothenpieler via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Timo Rothenpieler <timo@rothenpieler.org>
Subject: Re: [FFmpeg-devel] npp scaling
Date: Thu, 14 Aug 2025 16:00:28 +0200
Message-ID: <76897c6d-f267-4adb-96be-232114ef7f4e@rothenpieler.org> (raw)
In-Reply-To: <PAVPR01MB10371A989BDE4734004084155E135A@PAVPR01MB10371.eurprd01.prod.exchangelabs.com>
On 14/08/2025 15:17, Marco Oman via ffmpeg-devel wrote:
> Hi all,
> I am trying to compile FFmpeg with the --enable-libnpp flag configure on Ubuntu 24.04.
>
> but I am getting an error in file vf_scale_npp.c
>> CC libavfilter/vf_scale_npp.o
>> libavfilter/vf_scale_npp.c: In function 'nppscale_deinterleave':
>> libavfilter/vf_scale_npp.c:715:15: error: implicit declaration of function 'nppiYCbCr420_8u_P2P3R'; did you mean 'nppiYCbCr420_8u_P2P3R_Ctx'? [-Werror=implicit-function-declaration]
>> 715 | err = nppiYCbCr420_8u_P2P3R(in->data[0], in->linesize[0],
>
> After some investigation work I found that I have CUDA 13.0 on my machine and header file nppi_color_conversion.h installed by CUDA no have a 'double version' for each function, e.g. nppiYCbCr420_8u_P2P3R and nppiYCbCr420_8u_P2P3R_Ctx where the latter takes an extra argument of type NppStreamContext. It has only the latter, and so compilatioon breaks
>
> So it looks like sooner or later there will be the need to update vf_scale_npp.c to make it compile under these new conditions (without breaking the old).
>
> Anyone got the same problem? Anyone has plans for a fix?
I consider the npp based filters deprecated and have no plan to fix them.
I'll instead look into formalizing that, and making configure correctly
disable them with incompatible versions of the libraries.
Use scale_cuda instead.
_______________________________________________
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:[~2025-08-14 13:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 13:17 Marco Oman via ffmpeg-devel
2025-08-14 14:00 ` Timo Rothenpieler via ffmpeg-devel [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=76897c6d-f267-4adb-96be-232114ef7f4e@rothenpieler.org \
--to=ffmpeg-devel@ffmpeg.org \
--cc=timo@rothenpieler.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