all I am trying to --enable-protocol=SRT of ffmpeg. What I do as the following:
1.Check current configuration of ffmpeg which shows it doesn't suppport protocol of SRT.
2.So I trying to use msys64 to compile ffmpeg with --enable-protocol=SRT,and the command
$ ./configure --toolchain=msvc --arch=x64 --enable-yasm --enable-asm --enable-shared --enable-protocol=SRT
but the result as the following:
it's showing that the config is no use.Can you help me,thanks!
SRT is provided via an external library, so you'll need that library available for linking via pkg-config.
configure flags are --enable-protocol=libsrt --enable-libsrt. The former flag is only needed if you have disabled all components or protocols. Won't hurt to keep it, though.
Related
I'm building ffmpeg version 5.0.1 from source, but for some reason I don't get it to cross-compile against aarch64 as I want to run ffmpeg on a Khadas VIM4 which is a ARMv8 CPU, to be specific the CPU is an Amlogic A311D2 with non-free codecs..
To build ffmpeg from source, I have setup a build-suite put together from various sources which currently works fine with x86_64 and can be obtained here: https://github.com/venomone/ffmpeg_build_suite
Simply run trigger.sh from the terminal, make sure docker is installed on your host if you are interested. The script will output ffprobe and ffmpeg in a folder called /build
From my understanding, the ffmpeg configuration part must get extended by the following lines:
--enable-cross-compile \
--target-os=linux \
--arch=arm64 \
--cross-prefix=aarch64-linux-gnu- \
--enable-shared \
But even with these settings, I'm running into the following error:
#11 938.3 aarch64-linux-gnu-gcc is unable to create an executable file.
#11 938.3 C compiler test failed.
Is somebody able to provide me a hint, what might be the problem here?
I need ffmpeg with hardware acceleration.
I am compiling ffmpeg following this guide:
https://gist.github.com/Brainiarc7/eb45d2e22afec7534f4a117d15fe6d89
x264 never works after compile.
I follow the official guide, adding "--enable-shared", compile again, still no luck.
https://trac.ffmpeg.org/wiki/CompilationGuide/Ubuntu
Simply installing libx264-dev does not work as well.
$ ldd ~/bin/ffmpeg | grep x264 libx264.so.155 => not found
Does anyone know how to make x264 work?
Thanks.
Is there not any error message when you configure ffmpeg?
Or you can command ffmpeg, and show the configuration like
configuration: --enable-shared --enable-libx264 --enable-libx265 --enable-gpl --enable-nonfree
Maybe you can try install x264 from source.
You can use VCPKG to install ffmpeg with x264 support this project is avaliable on GIT.
Its a straight forward installation using VCPKG.
how to use vcpkg
https://www.youtube.com/watch?v=wRnjahwxZ8A&t=114s
I`m trying to compile ffmpeg in windows with nvidia libraries for hardware acceleration using MinGW/msys. tried to follow the instruction on nvidias website (section: Getting Started with FFmpeg/libav using NVIDIA GPUs). configured with --enable-nonfree --disable-shared --enable-nvenc --enable-cuda --enable-cuvid --enable-libnpp --extra-cflags=-Ilocal/include --extra-cflags=-I../common/inc --extra-ldflags=-L../common/lib/x64 --prefix=ffmpeg but stopped at "ERROR: libnpp not found." where common folder is downloaded from NVIDIA Video Codec SDK but there is no npp libs or header files. is there any solution for that? thanks for edvice.
I managed to successfuly cross compile ffmpeg under linux targeting Windows 64 bit with --enable-libnpp included.
My environment is Ubuntu Server 16.10 64bit.
After a fresh installation I installed MinGW using the command:
sudo apt-get install mingw-w64
First I successfully compiled the Linux version with the --enable-libnpp option activated following the instructions on the NVIDIA dev site Compile Ffmpeg with NVIDIA Video Codec SDK.
In order to do that you need to install the CUDA Toolkit. Just follow the instructions and the package installer will create the symbolic links (I have the CUDA Toolkit 8.0):
/usr/local/cuda/include/ -> /usr/local/cuda-8.0/targets/x86_64-linux/include
/usr/local/cuda/lib64/ -> /usr/local/cuda-8.0/targets/x86_64-linux/lib
This should provide Configure the right path to find the correct libraries and headers.
The command line I have used to compile the linux version of ffmpeg is:
./configure --enable-nonfree --disable-shared --enable-nvenc --enable-cuda --enable-cuvid --enable-libnpp --extra-cflags=-I/usr/local/cuda/include/ --extra-ldflags=-L/usr/local/cuda/lib64/
The problem you got is that when using cross-compilation you need to provide Configure the right path where to find headers and library for the Windows version of the libnpp library.
From the CUDA Toolkit Download page mentioned above I simply downloaded the exe(local) version of the Windows package.
Under the root of my working folder I created a folder called tmp where I copied the subfolders I found under npp_dev inside the package cuda_8.0.61_win10.exe:
cuda_8.0.61_win10.exe\npp_dev\lib -> tmp/lib
cuda_8.0.61_win10.exe\npp_dev\include -> tmp/include
As final step I launched Configure once again using the following parameters:
./configure --arch=x86_64 --target-os=mingw32 --cross-prefix=x86_64-w64-mingw32- --pkg-config=pkg-config --enable-nonfree --disable-shared --enable-nvenc --enable-cuda --enable-cuvid --enable-libnpp --extra-cflags=-I/usr/local/include --extra-cflags=-I/usr/local/cuda/include/ --extra-ldflags=-L/usr/local/cuda/lib64/ --extra-cflags=-I../tmp/include/ --extra-ldflags=-L../tmp/lib/x64/
The compilation completed successully. When I copied the ffmpeg.exe file to Windows and tried to execute it I got an errore message saying the executable was missing some npp_*.dll.
From the package cuda_8.0.61_win10.exe I copied all the dlls included into the folder npp\bin to the same directory I put ffmpeg.exe.
After that the application run normally and a simple conversion from a 4K file completed as expected.
Actually I went nuts about ffmpeg is not building with the same problem. I fianally managed to get it worked under Windows 10 x64:
Download msys2 from https://www.msys2.org/ and install all packages with Pacman
pacman -Su
pacman -S make
pacman -S diffutils
pacman -S yasm
pacman -S mingw-w64-x86_64-gcc
pacman -S mingw-w64-x86_64-toolchain
add pkgconfig to environment variable PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/usr/local/lib/pkgconfig
Add additional installed toolchain to path: PATH=$PATH:/opt/bin
Start mingw64 version: C:\msys64\msys2_shell.cmd -mingw64
Download and install Cuda from nVidia https://developer.nvidia.com/cuda-downloads?target_os=Windows&target_arch=x86_64&target_version=10&target_type=exenetwork
Extract the downloaded file e.g. cuda_11.2.2_461.33_win10.exe with 7zip locally
Copy cuda_nvcc\nvcc\include to your msys2 e.g. C:\msys64\tmp\nvidia_include
Copy libnpp\npp_dev\lib\x64 to your C:\msys64\tmp\nvidia_lib\x64
Copy libnpp\npp_dev\include to C:\msys64\tmp\nvidia_npp_include
git clone https://github.com/FFmpeg/FFmpeg.git to C:\msys64\home\<user>
git clone https://github.com/libav/libav to C:\msys64\home\<user>
Maybe optional step: git clone https://git.videolan.org/git/ffmpeg/nv-codec-headers.git to C:\msys64\home\<user>
make
make install
Optional because make install should have done this for you: Copy ffnvcodec.pc to C:\msys64\usr\local\lib\pkgconfig
Build libav avconv.exe and avprobe.exe are needed for ffmpeg later:
cd C:\msys64\home\<user>\libav
./configure
make
make install
Finally build ffmpeg:
cd C:\msys64\home\<user>\ffmpeg
./configure --enable-nonfree --disable-shared --enable-nvenc --enable-cuda --enable-cuvid --enable-libnpp --extra-cflags=-I/tmp/nvidia_npp_include --extra-cflags=-I/tmp/nvidia_include --extra-ldflags=-L/tmp/nvidia_lib/x64
make
make install
Copy avconv.exe and avprobe.exe to ffmpeg directory
Done.
Bugfixing:
Missing DLLs: find x64 missing DLLs on your harddisk or in internet.
Use dependency walker for analyzing errors
Download the newest nVidia drivers and use nSight making sure CUVID is supported for your graphic card.
This would seem to be caused by a broken configuration script in the FFmpeg code base. There is no library called npp in recent CUDA distributions, instead on Windows platforms you will have
nppc.lib
nppi.lib
npps.lib
and on linux
libnppc.so
libnppi.so
libnpps.so
You will either need to modify the configuration system yourself or file a bug request with the project developers to do it for you.
There might still be additional problems building the project with MinGW, but that is way beyond the scope of a Stack Overflow question.
If you check config.log, there may have a lot link warnings:
LINK : warning LNK4044: unrecognized option '/L...'; ignored
cause
ERROR: libnpp not found.
Since /L is not a correct argument for msvc linker, in order to include library path, the argument should as follow:
./configure .... --extra-cflags=-I/usr/local/cuda/... --extra-ldflags=-LIBPATH:/usr/local/cuda/...
This should able to solve the libnpp not found issue.
FYI, linker options are listed in the following link (included LIBPATH):
Linker Options
2022 Update
On this weekend I also managed to build latest ffmpeg with working scale_npp filter. Without any npp missing library error during compilation and building. But with some caveats (see below).
I followed this guide by NVIDIA with installed NVIDIA GPU Computing Toolkit v11.7 and latest driver display 473.47 for my video card GeForce GT 710 on Windows 10 21H2 x64
Changes (adaptations) for steps in the guide
I copied all headers including folders from directory path_to_CUDA_toolkit/include
I excluded pkg-config from pacman packages, because after recommended installation steps (step 7 in particular) of MSYS2 it conflicts with installed pkgconf package, i.e. use this command instead:
pacman -S diffutils make yasm
I added directories to Visual Studio C compiler to PATH environment variable in advance (using Windows GUI), in addition to declaring them in the MinGW64 terminal as specified in the guide:
export PATH="/c/Program Files (x86)/Microsoft Visual Studio/2017/BuildTools/VC/Tools/MSVC/14.16.27023/bin/Hostx64/x64/":$PATH
export PATH="/d/NVIDIA GPU Computing Toolkit/CUDA/v11.7/bin/":$PATH
After making (building) ffnvcodec headers, define PKG_CONFIG_PATH (where compiled file ffnvcodec.pc is located) before configure command.
Use absolute paths for --extra-cflags and --extra-ldflags options of configure command. It's probably the main thing in solving "not found" errors. But don't forget that these paths will be printed in ffmpeg banner with other explicit build options.
PKG_CONFIG_PATH="/d/_makeit/nv-codec-headers/" ./configure --enable-nonfree --disable-shared --enable-cuda-nvcc --enable-libnpp --toolchain=msvc --extra-cflags="-I/d/_makeit/ffmpeg/nv_sdk/" --extra-ldflags="-LIBPATH:/d/_makeit/ffmpeg/nv_sdk/"
And that's it. At least -vf scale_npp should work.
In my case still DO NOT WORK the following things from the guide:
cuda built-in resizer and cropper, i.e. -hwaccel_output_format cuda –resize 1280x720 and -hwaccel_output_format cuda –crop 16x16x32x32. I bet that this is due to my old video card is not in GPU Support Matrix. But NVENC and NVDEC works fine for me almost without crutches. And it seems I'm note alone.
UPD: resizer and cropper work! BUT in the mentioned guide commands are incorrect. I found correct way in another NVIDIA FFmpeg Transcoding Guide. Decoder h264_cuvid was missed, must be so:
ffmpeg.exe -y -vsync passthrough -hwaccel cuda -hwaccel_output_format cuda -c:v h264_cuvid -resize 1280x720 -i input.mp4 -c:a copy -c:v h264_nvenc -b:v 5M output.mp4
ffmpeg.exe -y -vsync passthrough -hwaccel cuda -hwaccel_output_format cuda -c:v h264_cuvid -crop 16x16x32x32 -i input.mp4 -c:a copy -c:v h264_nvenc -b:v 5M output.mp4
-vf scale_cuda fails with error. Maybe I used wrong C compiler version or didn't install DirectX SDK from here or installed wrong packages after installing MSYS2 and ignoring pkg-config
[Parsed_scale_cuda_0 # 000001A461479DC0] cu->cuModuleLoadData(cu_module, data) failed -> CUDA_ERROR_UNSUPPORTED_PTX_VERSION: the provided PTX was compiled with an unsupported toolchain.
there is no possibility to use -preset option for h264_nvenc with latest ffmpeg version where presets (enum) were updated. I noticed from ffmpeg report file, this is because using any preset causes "auto" enabling lookahead mode with log raw:
[h264_nvenc # 00000158EFC6E500] Lookahead enabled: depth 28, scenecut enabled, B-adapt enabled.
Even though the options -rc-lookahead and -temporal-aq are not supported by my device (video card). I have to use only one preset p4 (medium) which is by default. And I don't know how to workaround this issue. Value 0 for -rc-lookahead also does not help.
specifying -bf 2 only works with option -extra_hw_frames 6 (six in my case - number of extra frames can differ for your card). Or using only -bf 0. But this is due to constraints of my old video card.
ffmpeg.exe -v verbose -y -vsync passthrough -hwaccel cuda -hwaccel_output_format cuda -extra_hw_frames 6 -i input-1080p.mkv -map 0:v -map 0:a -c:a copy -c:v h264_nvenc -b:v 1M -bf 2 -bufsize 1M -maxrate 2M -qmin 0 -g 250 -b_ref_mode middle -i_qfactor 0.75 -b_qfactor 1.1 output.mp4
I hope my notes will help future Google and SO users.
While installing ffmpeg on Ubuntu 12.04
I am getting following error
libavcodec/libavcodec.a(libx264.o): In function `X264_init':
/root/ffmpeg/libavcodec/libx264.c:492: undefined reference to `x264_encoder_open_125'
collect2: ld returned 1 exit status
make: *** [ffmpeg_g] Error 1
I am following the instructions given at
http://ffmpeg.org/trac/ffmpeg/wiki/UbuntuCompilationGuide
Do anyone have idea about this error?
This is a typical problem for people who already have x264 installed through the package management system. You can solve this in at least 2 ways:
Uninstall the already existing x264 from your system, through the package management system:
# apt-get remove x264
and compile your new x264 from source
Don't uninstall the x264 package, but compile your new x264 and then compile your ffmpeg, telling it to use that newly compiled x264 library, by specifying that directory where your compiled x264 library is, using the mentioned LD_LIBRARY_PATH environment variable:
LD_LIBRARY_PATH=/path/to/my/compiled/x264/library ./configure --enable-libx264 ...
More info can be found on these links:
problem with --enable-libx264 option in ffmpeg
Compiling FFmpeg
add the header and lib path
gcc x264_test1.c -o x264_encoder -I/usr/local/include -L/usr/local/lib -lpthread -lm -lx264
Generally the error means that the library binary libx264.so picked up by the linker does not match the version in the header file x264.h. See the following lines of code in this header file:
/* Force a link error in the case of linking against an incompatible API version.
* Glue #defines exist to force correct macro expansion; the final output of the macro
* is x264_encoder_open_##X264_BUILD (for purposes of dlopen). */
#define x264_encoder_glue1(x,y) x##y
#define x264_encoder_glue2(x,y) x264_encoder_glue1(x,y)
#define x264_encoder_open x264_encoder_glue2(x264_encoder_open_,X264_BUILD)
The solution usually does not require building libx264 yourself,
just make sure that you installed libx264-dev properly without interference with other versions, which may also be in /usr/local/lib or the like.
I had the same issue with version 155:
undefined reference to 'x264_encoder_open_155'.
In my case this was because I had in /usr/lib/x86_64-linux-gnu and unsuitable copy of libx264.so (which I had produced myself and uncleanly copied there).
So all I had to do was sudo apt-get install --reinstall libx264-dev.
I am trying to build ffmpeg with libx264 support. Configure and compilation is successful but when I am running the ffmpeg the application is crashing.
ffmpeg configure option : ./configure --enable-static --enable-libx264 --enable-pthreads --enable-gpl --disable-doc --enable-memalign-hack --extra-ldflags="-L/usr/local/lib"
gcc --version 4.3.4
Here is gdb dump,
$gdb ffmpeg_g.exe
GNU gdb(GDB) 7.2
Copyright(c) 2010 Free Software Foundation
This GDB has configured as mingw32
Reading symbols from C:\work\ffmpeg25jan2011\ffmpeg\ffmpeg_g.exe.....done
(gdb) break main
BreakPoint 1 at 0x40a120 : file ffmpeg.c, line 4317
(gdb) run -V
Starting program: C:\work\ffmpeg25jan2011\ffmpeg\ffmpeg_g.exe
[New Thread]
gdb: Unknown Target exception 0xc0000022 at 0x7c96671e
**During startup program exited with code 0xc0000022**
Anybody has any clue, How this can be resolved?
Windows error code 0xc0000022 means "The Application Failed to initialize." It usually indicates that your build is broken. There are lots of things that could have gone wrong, but here are some things to check:
You should build all libraries you link to with the same toolchain. It may be possible to link a Cygwin-built ffmpeg to a VC++-built libx264, but since there's no good reason to do that, you shouldn't.
Try the "head" version of ffmpeg and its dependencies from the source repository
You show Windows paths, but claim to be using Cygwin. Try to use an all-Cygwin environment: build from a Cygwin bash shell, use POSIX paths, etc. In particular, this will help ensure that libraries get installed in places the build tools can find them.
You may need to install some libraries in /usr/lib, rather than the default, /usr/local/lib.
Try a complete rebuild: make clean && make