From 45070eec4c089b06947f07e25cdb1bc8b2102553 Mon Sep 17 00:00:00 2001 From: Lynne Date: Mon, 7 Sep 2020 02:41:19 +0200 Subject: libwavpackenc: remove libwavpackenc wrapper The manual states "there is virtually no reason to use that encoder.". It supports less sample formats than the native encoder, is less efficient than the native encoder and is also slower and pretty much remains untested. libwavpack also isn't being fuzzed, which given that we plug the parameters without any sanitizing them looks concerning. --- doc/general_contents.texi | 8 -------- 1 file changed, 8 deletions(-) (limited to 'doc/general_contents.texi') diff --git a/doc/general_contents.texi b/doc/general_contents.texi index c125fd0c21..598e0e74da 100644 --- a/doc/general_contents.texi +++ b/doc/general_contents.texi @@ -278,14 +278,6 @@ Due to security concerns, Vapoursynth scripts will not be autodetected so the input format has to be forced. For ff* CLI tools, add @code{-f vapoursynth} before the input @code{-i yourscript.vpy}. -@section WavPack - -FFmpeg can make use of the libwavpack library for WavPack encoding. - -Go to @url{http://www.wavpack.com/} and follow the instructions for -installing the library. Then pass @code{--enable-libwavpack} to configure to -enable it. - @section x264 FFmpeg can make use of the x264 library for H.264 encoding. -- cgit v1.2.3