From: wenbin.chen-at-intel.com@ffmpeg.org To: ffmpeg-devel@ffmpeg.org Subject: [FFmpeg-devel] [PATCH v2] doc: Add libtoch backend option to dnn_processing Date: Mon, 25 Mar 2024 10:15:08 +0800 Message-ID: <20240325021508.371987-1-wenbin.chen@intel.com> (raw) From: Wenbin Chen <wenbin.chen@intel.com> Signed-off-by: Wenbin Chen <wenbin.chen@intel.com> --- doc/filters.texi | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/doc/filters.texi b/doc/filters.texi index 18f0d1c5a7..bfa8ccec8b 100644 --- a/doc/filters.texi +++ b/doc/filters.texi @@ -12073,11 +12073,21 @@ need to build and install the OpenVINO for C library (see @code{--enable-libopenvino} (--extra-cflags=-I... --extra-ldflags=-L... might be needed if the header files and libraries are not installed into system path) +@item torch +Libtorch backend. To enable this backend you need to build and install Libtroch +for C++ library. Please download cxx11 ABI version (see +@url{https://pytorch.org/get-started/locally}) +and configure FFmpeg with @code{--enable-libtorch +--extra-cflags=-I/libtorch_root/libtorch/include +--extra-cflags=-I/libtorch_root/libtorch/include/torch/csrc/api/include +--extra-ldflags=-L/libtorch_root/libtorch/lib/} + @end table @item model Set path to model file specifying network architecture and its parameters. -Note that different backends use different file formats. TensorFlow, OpenVINO backend can load files for only its format. +Note that different backends use different file formats. TensorFlow, OpenVINO +and Libtorch backend can load files for only its format. @item input Set the input name of the dnn network. -- 2.34.1 _______________________________________________ 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 reply other threads:[~2024-03-25 2:15 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-25 2:15 wenbin.chen-at-intel.com [this message] 2024-03-25 11:16 ` Guo, Yejun 2024-03-26 16:03 ` Leo Izen 2024-03-27 7:43 ` Chen, Wenbin
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=20240325021508.371987-1-wenbin.chen@intel.com \ --to=wenbin.chen-at-intel.com@ffmpeg.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