March 10, 2026
GPU drama, one port to rule them
FFmpeg-over-IP – Connect to remote FFmpeg servers
Send your video jobs to a remote GPU — and the comments exploded
TLDR: A new tool lets you send video conversions to a remote computer’s graphics card without messy setup or shared drives. Commenters split between cheering the simplicity, grilling it against rffmpeg, waxing nostalgic about Plan 9, and debating whether the post sidestepped “Show HN” etiquette — and why that matters.
FFmpeg-over-IP just dropped into the tech forums and the crowd lit up. In simple terms: it lets your media app pretend to run a video converter locally while secretly sending the heavy lifting to another machine’s graphics card. No clunky network drives, no hardware gymnastics — just one open port and your files never leave your own computer. There’s basic security (shared-secret sign-in), prebuilt tools, and it runs on Mac, Windows, and Linux. The pitch? “Use your gaming rig’s GPU from anywhere,” and the audience heard it loud and clear.
Then came the drama. Performance hawks immediately asked how it stacks up against rffmpeg — will this be faster, or just easier? Nostalgia hit when one commenter declared this basically Plan 9 in a trench coat, lamenting the OS that “should’ve been.” Others poked at etiquette: is this a stealth “Show HN” post? Meanwhile, fans celebrated the “no network drive” life with memes like “one port to rule them all,” while skeptics worried about latency and real-world speed. The vibe: half cheering a clever shortcut, half demanding benchmarks and a roadmap. Love it or side-eye it, the thread turned a niche utility into a full-on spectator sport.
Key Points
- •ffmpeg-over-ip enables remote GPU-accelerated FFmpeg transcoding by tunneling file I/O over a TCP connection.
- •A client binary replaces local FFmpeg and forwards commands to a server running a patched FFmpeg; files remain on the client.
- •Releases include pre-built FFmpeg and ffprobe with NVENC, QSV, VAAPI, AMF, and VideoToolbox support via jellyfin-ffmpeg.
- •Security uses HMAC-SHA256 for authenticated commands and a single listening port on the server; clients initiate outbound connections.
- •Supported platforms include Linux (x86_64, arm64), macOS (x86_64, arm64), and Windows (x86_64), with docs for setup, Docker, and upgrades.