You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I ran across a practical case that seems relevant to this wishlist item while looking at moving TubeSync conversion work to my NVIDIA A2000.
The GPU is passed through to the TubeSync container correctly and the current bundled FFmpeg lists the NVENC encoders, but attempting to use h264_nvenc fails with:
Driver does not support the required nvenc API version. Required: 13.1 Found: 13.0
The minimum required Nvidia driver for nvenc is 610.00 or newer
The host is running NVIDIA 595.99.02, which is the current Production Branch I'm intentionally tracking. It looks like the current yt-dlp FFmpeg autobuild bundled by TubeSync has moved to NVENC API 13.1 ahead of NVIDIA's Production Branch.
I hadn't looked at ffmpeg-over-ip before seeing this issue, but this seems like a good example of the host/container FFmpeg and driver coupling it could potentially avoid. Mostly adding this as a real-world data point for the wishlist item.
Activity
rockymtngeek commentedon Sep 16, 2026
I ran across a practical case that seems relevant to this wishlist item while looking at moving TubeSync conversion work to my NVIDIA A2000.
The GPU is passed through to the TubeSync container correctly and the current bundled FFmpeg lists the NVENC encoders, but attempting to use
h264_nvencfails with:The host is running NVIDIA 595.99.02, which is the current Production Branch I'm intentionally tracking. It looks like the current yt-dlp FFmpeg autobuild bundled by TubeSync has moved to NVENC API 13.1 ahead of NVIDIA's Production Branch.
I hadn't looked at ffmpeg-over-ip before seeing this issue, but this seems like a good example of the host/container FFmpeg and driver coupling it could potentially avoid. Mostly adding this as a real-world data point for the wishlist item.