NVIDIA Jetson AGX Orin 64GBでのハードウェアアクセラレーションFFmpegの構築

Abstract This guide provides a comprehensive walkthrough for installing FFmpeg with hardware acceleration (NVENC/NVDEC) on an NVIDIA Jetson AGX Orin 64GB running Ubuntu 22.04 LTS and JetPack 6.2.2 (CUDA 12.6) . It also explores the high-performance video processing capabilities unlocked by this hardware configuration, comparing raw FFmpeg workflows against advanced Edge AI frameworks like NVIDIA DeepStream. 1. Why Hardware Acceleration Matters on Jetson Installing the stock FFmpeg package from the Ubuntu repositories ( sudo apt install ffmpeg ) is quick, but it lacks optimization for NVIDIA hardware. It forces all video encoding and decoding tasks onto the ARM CPU cores via software implementations (like libx264 ). By compiling FFmpeg from source with NVENC/NVDEC support, you offload these heavy mathematical operations to the Jetson's dedicated hardware video codecs and Ampere GPU architecture. This leaves the CPU completely free for application logic, automation scripts, or multi-agent orchestration. 2. Guide: Compiling FFmpeg with NVENC/NVDEC Support This method links FFmpeg with your local JetPack 6.2.2 components (CUDA 12.6 and cuDNN 9.3.0) to enable deep hardware utilization. 2.1. Install System Dependencies & NVIDIA Codec Headers First, ensure your environment has the required build tools and download the official NVIDIA hardware codec headers: sudo apt update && sudo apt install -y build-essential yasm cmake libtool libc6 libc6-dev unzip wget git # Clone and install NVIDIA codec headers globally git clone https://git.videolan.org/git/ffmpeg/nv-codec-headers.git cd nv-codec-headers sudo make install cd .. 2.2. Clone and Configure FFmpeg Clone the upstream FFmpeg repository and configure the build flags to target the specific library paths found on JetPack 6 hardware. git clone https://git.ffmpeg.org/ffmpeg.git ffmpeg/ cd ffmpeg # Configure with explicit paths for CUDA 12.6 ./configure \ --enable-cuda-nvcc \ --enable-cuvid \ --enable-nvenc \ --enable-nvdec \ --enable-libnpp \ --extra-cflags = "-I/usr/local/cuda/include" \ --extra-ldflags = "-L/usr/local/cuda/lib64" \ --enable-nonfree \ --enable-gpl 💡 Note: If your workflows require software fallbacks or audio libraries, append flags such as --enable-libx264 or --enable-libmp3lame after installing their respective development packages ( sudo apt install libx264-dev libmp3lame-dev ). 2.3. Compile and Install The AGX Orin Dev Kit features a 12-core ARMv8 CPU. You can speed up compilation significantly by utilizing all 12 threads: make -j12 sudo make install 2.4. Verifying the Hardware Codecs To confirm that the compilation successfully integrated the Jetson GPU capabilities, query the available encoders and decoders: ffmpeg -encoders | grep nv ffmpeg -decoders | grep nv Verify that entries like h264_nvenc , hevc_nvenc , and their corresponding cuvid decoders appear in the output. 3. High-Performance Video Processing Capabilities With an AGX Orin 64GB module, the hardware goes far beyond simple file transcoding. The table below outlines the architectural options available depending on your exact deployment goals. Video Architecture Matrix Use Case Recommended Tool Core Advantage Data Path Performance Batch Transcoding & Streaming FFmpeg (Custom Build) Highly portable, simple script integration, standardized CLI. Excellent for standard file/network streams. Minimal CPU overhead. Real-Time AI & Video Analytics NVIDIA DeepStream SDK Zero-copy memory architecture. Native TensorRT engine integration. Peak Edge AI performance. Capable of $>30$ concurrent 1080p @ 30 FPS streams. Low-Level Control & Custom Pipelines GStreamer (with L4T plugins) Granular buffering, dynamic pipeline manipulation, microsecond synchronization. High efficiency using nvv4l2decoder and memory surfaces directly. Computer Vision Pre-processing OpenCV (CUDA Compiled) Direct structural image manipulation ( cv2.cuda ) within Python/C++. Bypasses host memory bottlenecks by keeping frames on GPU memory blocks. 4. Architectural Recommendations When to use the Compiled FFmpeg Pipeline FFmpeg is ideal for standard ingestion, media distribution, and storage-saving operations. If you are building a media gateway, converting high-resolution 4K H.265 RTSP streams from IP cameras down to lightweight web formats (H.264, HLS, or WebRTC), or implementing basic archival systems, the custom FFmpeg build provides a clean, unified workflow. When to switch to DeepStream / TensorRT If your ultimate goal involves Deep Learning inference —such as object tracking, automated license plate recognition (ANPR), industrial quality control, or maritime logistics monitoring—FFmpeg should not be the primary pipeline infrastructure. Instead, deploy NVIDIA DeepStream . Because DeepStream builds on GStreamer and utilizes NVIDIA's unified physical memory architecture, video frames stay inside the GPU memory space from ingestion ( NVDEC ), through inference ( TensorRT ), up to the final output rendering. This eliminates host-to-device memory serialization bottlenecks completely. 5. Conclusion Compiling FFmpeg with native GPU support ensures your NVIDIA Jetson AGX Orin functions as a highly optimized media node rather than relying on generic CPU execution. Whether paired with automated Python microservices or embedded inside heavy multi-agent analytics frameworks, maximizing hardware codec acceleration is a fundamental requirement for stable edge deployments. Abstract This guide provides a comprehensive walkthrough for installing FFmpeg with hardware acceleration (NVENC/NVDEC) on an NVIDIA Jetson AGX Orin 64GB running Ubuntu 22.04 LTS and JetPack 6.2.2 (CUDA 12.6) . It also explores the high-performance video processing capabilities unlocked by this hardware configuration, comparing raw FFmpeg workflows against advanced Edge AI frameworks like NVIDIA DeepStream. 1. Why Hardware Acceleration Matters on Jetson Installing the stock FFmpeg package from the Ubuntu repositories ( sudo apt install ffmpeg ) is quick, but it lacks optimization for NVIDIA hardware. It forces all video encoding and decoding tasks onto the ARM CPU cores via software implementations (like libx264 ). By compiling FFmpeg from source with NVENC/NVDEC support, you offload these heavy mathematical operations to the Jetson's dedicated hardware video codecs and Ampere GPU architecture. This leaves the CPU completely free for application logic, automation scripts, or multi-agent orchestration. 2. Guide: Compiling FFmpeg with NVENC/NVDEC Support This method links FFmpeg with your local JetPack 6.2.2 components (CUDA 12.6 and cuDNN 9.3.0) to enable deep hardware utilization. 2.1. Install System Dependencies & NVIDIA Codec Headers First, ensure your environment has the required build tools and download the official NVIDIA hardware codec headers: sudo apt update && sudo apt install -y build-essential yasm cmake libtool libc6 libc6-dev unzip wget git # Clone and install NVIDIA codec headers globally git clone https://git.videolan.org/git/ffmpeg/nv-codec-headers.git cd nv-codec-headers sudo make install cd .. 2.2. Clone and Configure FFmpeg Clone the upstream FFmpeg repository and configure the build flags to target the specific library paths found on JetPack 6 hardware. git clone https://git.ffmpeg.org/ffmpeg.git ffmpeg/ cd ffmpeg # Configure with explicit paths for CUDA 12.6 ./configure \ --enable-cuda-nvcc \ --enable-cuvid \ --enable-nvenc \ --enable-nvdec \ --enable-libnpp \ --extra-cflags = "-I/usr/local/cuda/include" \ --extra-ldflags = "-L/usr/local/cuda/lib64" \ --enable-nonfree \ --enable-gpl 💡 Note: If your workflows require software fallbacks or audio libraries, append flags such as --enable-libx264 or --enable-libmp3lame after installing their respective development packages ( sudo apt install libx264-dev libmp3lame-dev ). 2.3. Compile and Install The AGX Orin Dev Kit features a 12-core ARMv8 CPU. You can speed up compilation significantly by utilizing all 12 threads: make -j12 sudo make install 2.4. Verifying the Hardware Codecs To confirm that the compilation successfully integrated the Jetson GPU capabilities, query the available encoders and decoders: ffmpeg -encoders | grep nv ffmpeg -decoders | grep nv Verify that entries like h264_nvenc , hevc_nvenc , and their corresponding cuvid decoders appear in the output. 3. High-Performance Video Processing Capabilities With an AGX Orin 64GB module, the hardware goes far beyond simple file transcoding. The table below outlines the architectural options available depending on your exact deployment goals. Video Architecture Matrix Use Case Recommended Tool Core Advantage Data Path Performance Batch Transcoding & Streaming FFmpeg (Custom Build) Highly portable, simple script integration, standardized CLI. Excellent for standard file/network streams. Minimal CPU overhead. Real-Time AI & Video Analytics NVIDIA DeepStream SDK Zero-copy memory architecture. Native TensorRT engine integration. Peak Edge AI performance. Capable of $>30$ concurrent 1080p @ 30 FPS streams. Low-Level Control & Custom Pipelines GStreamer (with L4T plugins) Granular buffering, dynamic pipeline manipulation, microsecond synchronization. High efficiency using nvv4l2decoder and memory surfaces directly. Computer Vision Pre-processing OpenCV (CUDA Compiled) Direct structural image manipulation ( cv2.cuda ) within Python/C++. Bypasses host memory bottlenecks by keeping frames on GPU memory blocks. 4. Architectural Recommendations When to use the Compiled FFmpeg Pipeline FFmpeg is ideal for standard ingestion, media distribution, and storage-saving operations. If you are building a media gateway, converting high-resolution 4K H.265 RTSP streams from IP cameras down to lightweight web formats (H.264, HLS, or WebRTC), or implementing basic archival systems, the custom FFmpeg build provides a clean, unified workflow. When to switch to DeepStream / TensorRT If your ultimate goal involves Deep Learning inference —such as object tracking, automated license