Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Gyan Doshi <ffmpeg@gyani.pro>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] doc/filters: Add CUDA Video Filters section for CUDA-based and CUDA+NPP based filters.
Date: Tue, 4 Feb 2025 11:10:09 +0530
Message-ID: <d4a48c0d-6dea-44fe-8d88-483d8cfbaca2@gyani.pro> (raw)
In-Reply-To: <20250202132332.730-1-danyaschenko@gmail.com>

Hi Danil,

See notes below.

On 2025-02-02 06:53 pm, Danil Iashchenko wrote:
> ---
>   doc/filters.texi | 1323 ++++++++++++++++++++++++----------------------
>   1 file changed, 700 insertions(+), 623 deletions(-)
>
> diff --git a/doc/filters.texi b/doc/filters.texi
> index c2817b2661..7460b7ef18 100644
> --- a/doc/filters.texi
> +++ b/doc/filters.texi

> @@ -26890,6 +26280,693 @@ value.
>   
>   @c man end VIDEO FILTERS
>   
> +@chapter CUDA Video Filters
> +@c man begin CUDA Video Filters
> +
> +To enable compilation of these filters you need to configure FFmpeg with
> +@code{--enable-cuda-nvcc} and/or @code{--enable-libnpp} and Nvidia CUDA Toolkit must be installed.


1) cuda-llvm also suffices and doesn't require non-free.
2) Identify what npp is and make clear that only npp filters require 
libnpp. For either cuda-nvcc and npp, nonfree is also required.

> +@section CUDA
> +Below is a description of the currently available Nvidia CUDA video filters.
> +
> +To enable compilation of these filters you need to configure FFmpeg with
> +@code{--enable-cuda-nvcc} and Nvidia CUDA Toolkit must be installed.

Same note about cuda-llvm.

> +@section CUDA NPP
> +Below is a description of the currently available NVIDIA Performance Primitives (libnpp) video filters.
> +
> +To enable compilation of these filters you need to configure FFmpeg with @code{--enable-libnpp} and Nvidia CUDA Toolkit must be installed.
Note that it is "configure FFmpeg with libnpp" in addition to cuda, and 
with nonfree.
> +@end table
> +
> +@c man end CUDA Video Filters

Rest all looks ok.

Regards,
Gyan
_______________________________________________
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".

      reply	other threads:[~2025-02-04  5:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250116004751.56789-1-danyaschenko@gmail.com>
2025-01-26 10:55 ` [FFmpeg-devel] [PATCH 1/1] [doc/filters] add nvidia cuda and cuda npp sections Gyan Doshi
2025-01-28 19:12   ` [FFmpeg-devel] [PATCH 1/2] doc/filters: Add CUDA Video Filters section for CUDA-based and CUDA+NPP based filters Danil Iashchenko
2025-01-28 19:12     ` [FFmpeg-devel] [PATCH 2/2] doc/filters: Remove redundant *_cuda and *_npp filters since they are already in CUDA Video Filters section Danil Iashchenko
2025-02-02  6:58       ` Gyan Doshi
2025-02-02 13:23         ` [FFmpeg-devel] [PATCH] doc/filters: Add CUDA Video Filters section for CUDA-based and CUDA+NPP based filters Danil Iashchenko
2025-02-04  5:40           ` Gyan Doshi [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=d4a48c0d-6dea-44fe-8d88-483d8cfbaca2@gyani.pro \
    --to=ffmpeg@gyani.pro \
    --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