-
-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ Versions and Compatibility
← Back to FAQ
Answer. As of v3.0.0, the integration patches cover FFmpeg 6.0, 6.1, 7.0,
7.1, 8.0, and 8.1 (libavcodec 60–62).
scripts/ffpatch.sh
auto-detects the version of a checked-out FFmpeg tree and applies the matching
patch, idempotently.
Retired versions. FFmpeg 4.2 and 4.4 (libavcodec 58) were supported in v2.x releases but are retired as of v3.0.0. Users on Nano/TX1 hardware that cannot run FFmpeg 6.0+ should use v2.10.0.
Why it varies. FFmpeg's codec API drifted across these releases
(AVCodec→FFCodec at v60, the receive_packet encode API, the
FF_PROFILE_*→AV_PROFILE_* rename at v62.11). With 4.x dropped, the remaining
version logic is minimal — only the AV_PROFILE rename at 62.11 needs a guard.
See the Development Guide.
References. Keylost#6, Keylost#13, Keylost#28, Keylost PR#19. Full matrix: Compatibility.
Symptom. Streaming HEVC (H.265) over RTMP fails or is rejected by the muxer on older FFmpeg.
Cause. HEVC-in-RTMP requires the Enhanced RTMP specification, which landed in FFmpeg ≥ 6.1. Earlier FFmpeg cannot carry HEVC over RTMP at all — this is an FFmpeg/muxer capability, not an nvmpi limitation.
Resolution. Use one of the FFmpeg 6.1 / 7.x / 8.x patches (or a matching release build) and an endpoint that speaks Enhanced RTMP.
References. Keylost#35.
🏠 Home · 📦 Repository · 🐞 Issues · 🏷 Releases · 📋 README · 📝 CHANGELOG
Documentation lives in this wiki. To change a doc, edit the relevant wiki page (clone jetson-ffmpeg.wiki.git) — the docs/ folder in the repo has been retired.
📦 Usage & Runtime
❓ FAQ
- Overview
- Hardware & Platform
- Versions & Compatibility
- Build & Install
- Performance
- Features & Fork Differences
🛠 Development
⚙️ CI / Infrastructure
- GitHub Actions
- GitLab CI
- GitHub Runner — Manual
- GitHub Runner — Kubernetes
- GitLab Runner — Manual
- GitLab Runner — Kubernetes
- Release Process
🔬 Project / Fork Analysis