steelbrain/ffmpeg-over-ip

Health v2 · maintenance only

Flags: no_license

Adoption not part of the score

1176 stars · 37 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

A client/server tool that lets applications use GPU-accelerated ffmpeg on a remote machine over a single TCP connection, without GPU passthrough or shared filesystems. The client masquerades as the ffmpeg binary, forwarding arguments to a server running a patched ffmpeg that tunnels all file I/O back to the client.

Use cases

• use GPU transcoding from a Docker container without nvidia runtime passthrough
• share one GPU across multiple VMs for video transcoding
• let Jellyfin or Emby transcode on a remote GPU machine without NFS
• avoid shared filesystem setup for remote ffmpeg jobs
• run ffmpeg on a machine that has files but no GPU
• expose NVENC or QSV transcoding over the network

When to choose

• your media server runs in a container or VM without GPU access
• you want to centralize GPU transcoding on one host
• you need ffmpeg/ffprobe access to files that must stay on the client machine
• you want prebuilt ffmpeg binaries with broad hardware acceleration support

When to avoid

• client and server can share the same filesystem and GPU directly
• you need low-latency local transcoding with no network hop
• you require features beyond what the patched ffmpeg tunnel supports

Facets

application · maturity active

video-processing networking security gpu-computing cli media self-hosted networking gpu-computing windows self-hosted go ffmpeg transcoding gpu-acceleration jellyfin emby media-server remote-transcoding nvenc hardware-acceleration linux macos docker

Member repositories

For agents

markdown · JSON · MCP: product_card(name="steelbrain/ffmpeg-over-ip")