https://github.com/steelbrain/ffmpeg-over-ip Skip to content Navigation Menu Toggle navigation Sign in * Product + Actions Automate any workflow + Security Find and fix vulnerabilities + Codespaces Instant dev environments + GitHub Copilot Write better code with AI + Code review Manage code changes + Issues Plan and track work + Discussions Collaborate outside of code Explore + All features + Documentation + GitHub Skills + Blog * Solutions By size + Enterprise + Teams + Startups By industry + Healthcare + Financial services + Manufacturing By use case + CI/CD & Automation + DevOps + DevSecOps * Resources Topics + AI + DevOps + Security + Software Development + View all Explore + Learning Pathways + White papers, Ebooks, Webinars + Customer Stories + Partners * Open Source + GitHub Sponsors Fund open source developers + The ReadME Project GitHub community articles Repositories + Topics + Trending + Collections * Enterprise + Enterprise platform AI-powered developer platform Available add-ons + Advanced Security Enterprise-grade security features + GitHub Copilot Enterprise-grade AI features + Premium Support Enterprise-grade 24/7 support * Pricing Search or jump to... Search code, repositories, users, issues, pull requests... Search [ ] Clear Search syntax tips Provide feedback We read every piece of feedback, and take your input very seriously. [ ] [ ] Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly Name [ ] Query [ ] To see all available qualifiers, see our documentation. Cancel Create saved search Sign in Sign up Reseting focus 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 {{ message }} steelbrain / ffmpeg-over-ip Public * Notifications You must be signed in to change notification settings * Fork 1 * Star 149 Connect to remote ffmpeg servers License MIT license 149 stars 1 fork Branches Tags Activity Star Notifications You must be signed in to change notification settings * Code * Issues 0 * Pull requests 0 * Actions * Projects 0 * Security * Insights Additional navigation options * Code * Issues * Pull requests * Actions * Projects * Security * Insights steelbrain/ffmpeg-over-ip This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository. main BranchesTags Go to file Code Folders and files Last Last Name Name commit commit message date Latest commit History 35 Commits bin bin lib lib src src typings typings .gitignore .gitignore .npmignore .npmignore CHANGELOG.md CHANGELOG.md LICENSE.md LICENSE.md README.md README.md biome.json biome.json package-lock.json package-lock.json package.json package.json template.ffmpeg-over-ip.client.jsonc template.ffmpeg-over-ip.client.jsonc template.ffmpeg-over-ip.server.jsonc template.ffmpeg-over-ip.server.jsonc tsconfig.json tsconfig.json View all files Repository files navigation * README * MIT license ffmpeg over IP Connect to remote ffmpeg servers. Are you tired of unsuccessfully trying to pass your GPU through to a docker container running in a VM? So was I! ffmpeg-over-ip allows you to run an ffmpeg server on a machine with access to a GPU (Linux, Windows, or Mac) and connect to it from a remote machine. The only thing you need is Node.js installed and a shared filesystem (could be NFS, SMB, etc.) between the two machines. Installation ffmpeg-over-ip consists of two main parts, the server and the client. Both are packed neatly into single JS files. You can download these from the npm interface or by npm install ffmpeg-over-ip and then copying them to the relevant places. You don't need any node_modules to run the server or the client. The javascript files require Node.js runtime to work. If you want standalone files that you can mount in a docker container, you can find these in the Github Releases. On the releases page, you may have to click "Show all assets" to see the files. Configuration The server and the client are both configured using JSONC (JSON with comments) configuration files. The paths of these files can be flexible. To identify which paths are being used, you can invoke either with --debug-print-search-paths. Template/example configuration files are provided in this repository for your convinience. Unless the server and the client share the same filesystem, you may have to specify rewrites in the server configuration file. Usage Both the server and the client files are executable, so long as there is a Node.js installation available. If you intend to use this in a docker container, you can directly mount the client file to where the container would expect a regular ffmpeg executable to be, ie docker run -v ./path/to/client-bin:/usr/lib/jellyfin-ffmpeg/ffmpeg .... The server and the client communicate commands over HTTP, so make sure that whatever port you specify on the server is allowed through the firewall. Assuming you download one of the release files, here's what the usage would look like On the client side $ ./ffmpeg-over-ip-client --debug-print-search-paths # See the places where it'll look for config $ cp template.ffmpeg-over-ip.client.jsonc ffmpeg-over-ip.client.jsonc # Add config to one of the places $ nano ffmpeg-over-ip.client.jsonc # Change the stuff you want $ ./ffmpeg-over-ip-client On the server side $ ./ffmpeg-over-ip-server --debug-print-search-paths # See the places where it'll look for config $ cp template.ffmpeg-over-ip.server.jsonc ffmpeg-over-ip.server.jsonc # Add config to one of the places $ nano ffmpeg-over-ip.server.jsonc # Change the stuff you want, especially the rewrites $ ./ffmpeg-over-ip-server Assuming you want to download these from npm, here's how you would do it On the client side: $ npm install ffmpeg-over-ip $ ./node_modules/.bin/ffmpeg-over-ip-client --debug-print-search-paths # See the places where it'll look for config $ cp template.ffmpeg-over-ip.client.jsonc ffmpeg-over-ip.client.jsonc # Add config to one of the places $ nano ffmpeg-over-ip.client.jsonc # Change the stuff you want $ ./node_modules/.bin/ffmpeg-over-ip-client On the server side: $ npm install ffmpeg-over-ip $ ./node_modules/.bin/ffmpeg-over-ip-server --debug-print-search-paths # See the places where it'll look for config $ cp template.ffmpeg-over-ip.server.jsonc ffmpeg-over-ip.server.jsonc # Add config to one of the places $ nano ffmpeg-over-ip.server.jsonc # Change the stuff you want, especially the rewrites $ ./node_modules/.bin/ffmpeg-over-ip-server License The contents of this project are licensed under the terms of the MIT License. About Connect to remote ffmpeg servers Topics ffmpeg gpu emby jellyfin Resources Readme License MIT license Activity Stars 149 stars Watchers 2 watching Forks 1 fork Report repository Releases 3 v3.0.0 Latest Oct 4, 2024 + 2 releases Languages * JavaScript 57.4% * TypeScript 42.6% Footer (c) 2024 GitHub, Inc. Footer navigation * Terms * Privacy * Security * Status * Docs * Contact * Manage cookies * Do not share my personal information You can't perform that action at this time.