You can check this after the build and install finished, by: With thes preparations, it should be possible to build OpenCV including CUDA support and FFMPEG. by:Įxport LD_LIBRARY_PATH=/home/username/ffmpeg-4.4/libavdevice:/home/username/ffmpeg-4.4/libavfilter:/home/username/ffmpeg-4.4/libavformat:/home/username/ffmpeg-4.4/libavcodec:/home/username/ffmpeg-4.4/libavformat:/home/username/ffmpeg-4.4/libswresample:/home/username/ffmpeg-4.4/libswscale:/home/username/ffmpeg-4.4/libavutil: You should also set LD_LIBRARY_PATH, e.g. In this file you add the paths to the ffmpeg libraries (assuming you built ffmpeg-4.4 under the folder /home/username/): configure -enable-shared -disable-static -prefix=/usr/localĪfterwards you should include the library paths to ld config by: Sudo apt-get -purge autoremove python-opencvĪfterwards, I downloaded latest FFMPEG sources from and build it with the following configuration: I was successful to get a CUDA accelerated build of OpenCV with FFMPEG, when I previously uninstalled all previous OpenCV and FFMPEG installations by: Reason is, that the FFMPEG test build during the CMake build fails (propably due to some static libraries). But usually, all these builds end up without FFMPEG support, although all required libraries are found. You can find several scripts, I used an aption of this. There is also an option to build OpenCV with CUDA support. There is also an easy way to get an up-to-date OpenCV (currently 4.5.3) with FFMPEG support using:īut this has no hardware accelaration at all (neither OpenCV nor the FFMPEG integration). Meanwhile there is an Option to get FFMPEG with hardware accelerated decoding as decribed here. FFMPEG: no hardware accelerated decoding/encoding.OpenCV (Python) aged (4.1.1) without CUDA acceleration, no FFMPEG support.Current situation with Jetpack 4.5.1 (after initial installation):
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |