rffmpeg is a remote FFmpeg wrapper used to execute FFmpeg commands on a remote server via SSH. It is most useful in situations involving media servers such as Jellyfin (our reference user), where one might want to perform transcoding actions with FFmpeg on a remote machine or set of machines which can better handle transcoding, take advantage of hardware acceleration, or distribute transcodes across multiple servers for load balancing.
-
Install the required Python 3 dependencies:
click,yamlandsubprocess(sudo apt install python3-click python3-yaml python3-subprocessin Debian). -
Create the directory
/etc/rffmpeg. -
Copy the
rffmpeg.yml.samplefile to/etc/rffmpeg/rffmpeg.ymland edit it to suit your needs if required. -
Install
rffmpegsomewhere useful, for instance at/usr/local/bin/rffmpeg. -
Create symlinks for the command names
ffmpegandffprobetorffmpeg, for examplesudo ln -s /usr/local/bin/rffmpeg /usr/local/bin/ffmpegandsudo ln -s /usr/local/bin/rffmpeg /usr/local/bin/ffprobe. -
Initialize the database and add a target host, for example
sudo rffmpeg init && rffmpeg add myhost.domain.tld. -
Set your media program to use
rffmpegvia theffmpegsymlink name created above, instead of any otherffmpegbinary. -
Profit!
rffmpeg does require a little bit more configuration to work properly however. For a comprehensive installation tutorial based on a reference setup, please see the SETUP guide.
The rffmpeg configuration file located at rffmpeg.yml.sample is an example that shows all default options. Even though this file is effectively "empty", it must be present at /etc/rffmpeg/rffmpeg.yml or at an alternative location specified by the environment variable RFFMPEG_CONFIG; the latter is only useful for testing, as media programs like Jellyfin provide no way to specify this.
To override a default option, simply uncomment the relevant line and adjust it to suit your needs. For those using Jellyfin and following the SETUP guide, no default options will need to be changed.
NOTE: If you are running into problems with rffmpeg, please adjust logging -> debug to true to obtain more detailed logs before requesting help.
Each option has an explanatory comment above it detailing its purpose.
Since the configuration file is YAML, ensure that you do not use "Tab" characters inside of it, only spaces.
After first installing rffmpeg, ensure you initialize the database with the sudo rffmpeg init command. Note that sudo is required here to create the required data paths, but afterwards, rffmpeg can be run by anyone in the configured group (by default the sudo group).
rffmpeg is a Click-based application; thus, all commands have a -h or --help flag to show usage and additional options that may be specified.
Once installed and initialized, the status of the rffmpeg system can be viewed with the command rffmpeg status. This will show all configured target hosts, their states, and any active commands being run.
To add a target host, use the command rffmpeg add. This command takes the optional -w/--weight flag to adjust the weight of the target host (see below). A host can be added more than once.
To remove a target host, use the command rffmpeg remove. This command takes either a target host name/IP, which affects all instances of that name, or a specific host ID. Removing an in-use target host will not terminate any running processes, though it may result in undefined behaviour within rffmpeg. Before removing a host it is best to ensure there is nothing using it.
The rffmpeg CLI offers a convenient way to view the log file. Use rffmpeg log to view the entire logfile in the current pager (usually less), or use rffmpeg log -f to follow any new log entries after that point (like tail -0 -f).
If one of the configured target hosts is called localhost or 127.0.0.1, rffmpeg will run the ffmpeg/ffprobe commands locally without SSH. This can be useful if the local machine is also a powerful transcoding device, but you still want to offload some transcoding jobs to other machines.
In addition, rffmpeg will fall back to localhost automatically, even if it is not explicitly configured, should it be unable to find any working remote hosts. This helps prevent situations where rffmpeg cannot be run due to none of the remote host(s) being available.
In both cases, note that, if hardware acceleration is configured, it must be available on the local host as well, or the ffmpeg commands will fail. There is no easy way around this without rewriting arguments, and this is currently out-of-scope for rffmpeg. You should always use a lowest-common-denominator approach when deciding on what additional option(s) to enable, such that any configured host can run any process, or accept that fallback will not work if all remote hosts are unavailable.
The exact path to the local ffmpeg and ffprobe binaries can be overridden in the configuration, should their paths not match those of the remote system(s).
When more than one target host is present, rffmpeg uses the following rules to select a target host. These rules are evaluated each time a new rffmpeg alias process is spawned based on the current state (actively running processes, etc.).
-
Any hosts marked
badare ignored. -
All remaining hosts are iterated through in an indeterminate order (Python dictionary with root key as the host ID). For each host:
a. If the host is not
localhost/127.0.0.1, it is tested to ensure it is reachable (responds toffmpeg -versionover SSH). If it is not reachable, it is markedbadfor the duration of this processes' runtime and skipped.b. If the host is
idle(has no running processes), it is immediately chosen and the iteration stops.c. If the host is
active(has at least one running process), it is checked against the host with the current fewest number of processes, adjusted for host weight. If it has the fewest, it takes over this role. -
Once all hosts have been iterated through, at least one host should have been chosen: either the first
idlehost, or the host with the fewest number of active processes.rffmpegwill then begin running against this host. If no valid target host was found,localhostis used (see section Localhost and Fallback above).
When adding a host to rffmpeg, a weight can be specified. Weights are used during the calculation of the fewest number of processes among hosts. The actual number of processes running on the host is floor divided (rounded down to the nearest divisible integer) by the weight to give a "weighted count", which is then used in the determination. This option allows one host to take on more processes than other nodes, as it will be chosen as the "least busy" host more often.
For example, consider two hosts: host1 with weight 1, and host2 with weight 5. host2 would have its actual number of processes floor divided by 5, and thus any number of processes under 5 would count as 0, any number of processes between 5 and 10 would count as 1, and so on, resulting in host2 being chosen over host1 even if it had several processes. Thus, host2 would on average handle 5x more ffmpeg processes than host1 would.
Host weighting is a fairly blunt instrument, and only becomes important when many simultaneous ffmpeg processes/transcodes are occurring at once across at least 2 remote hosts, and where the target hosts have significantly different performance profiles. Generally leaving all hosts at weight 1 would be sufficient for most use-cases.
Furthermore, it is possible to add a host of the same name more than once in the rffmpeg add command. This is functionally equivalent to setting the host with a higher weight, but may have some subtle effects on host selection beyond what weight alone can do; this is probably not worthwhile but is left in for the option.
As mentioned above under Target Host Selection, a host can be marked bad if it does not respond to an ffmpeg -version command in at least 1 second if it is due to be checked as a target for a new rffmpeg alias process. This can happen because a host is offline, unreachable, overloaded, or otherwise unresponsive.
Once a host is marked bad, it will remain so for as long as the rffmpeg process that marked it bad is running. This can last anywhere from a few seconds (library scan processes, image extraction) to several tens of minutes (a long video transcode). During this time, any new rffmpeg processes that start will see that the host is marked as bad and thus skip it for target selection. Once the marking rffmpeg process completes or is terminated, the bad status of that host will be cleared, allowing the next run to try it again. This strikes a balance between always retrying known-unresponsive hosts over and over (and thus delaying process startup), and ensuring that hosts will eventually be retried.
If for some reason all configured hosts are marked bad, fallback will be engaged; see the above section Localhost and Fallback for details on what occurs in this situation. An explicit localhost host entry cannot be marked bad.
My virtualization setup (multiple 1U nodes with lots of live migration/failover) didn't lend itself well to passing a GPU into my Jellyfin VM, but I wanted to offload transcoding because doing 4K HEVC transcodes with a CPU performs horribly. I happened to have another machine (my "base" remote headless desktop/gaming server) which had a GPU, so I wanted to find a way to offload the transcoding to it. I came up with rffmpeg as a simple wrapper to the ffmpeg and ffprobe calls that Jellyfin (and Emby, and likely other media servers too) makes which would run them on that host instead. After finding it quite useful myself, I released it publicly as GPLv3 software so that others may benefit as well!
This depends on what "layer" you're asking at.
- Media Servers: Jellyfin is officially supported; Emby seems to work fine, with caveats (see Issue #10); no others have been tested to my knowledge.
- Operating Systems (source): Debian and its derivatives (Ubuntu, Linux Mint, etc.) should all work perfectly; other Linux operating systems should work fine too as the principles are the same; MacOS should work since it has an SSH client built in; Windows will not work as
rffmpegdepends on some POSIX assumptions internally. - Operating Systems (target): Any Linux system which
jellyfin-ffmpegsupports, which is currently just Debian and Ubuntu; Windows might work if you can get an SSH server running on it (see Issue #17). - Install Methods for Jellyfin: Native packages/installers/archives are recommended; a set of Jellyfin Docker containers integrating
rffmpeghas been created by @Shadowghost. - Install Methods for
rffmpeg: Direct installation is recommended; a Docker container to act as an ffmpeg transcode target has been created by @BasixKOR.
Explicitly no. rffmpeg is not designed to interact with the arguments that the media server passes to ffmpeg/ffprobe at all, nor will it. This is an explicit design decision due to the massive complexity of FFMpeg - to do this, I would need to create a mapping of just about every possible FFMpeg argument, what it means, and when to turn it on or off, which is way out of scope.
This has a number of side effects:
rffmpegdoes not know whether hardware acceleration is turned on or not (see above caveats under Localhost and Fallback).rffmpegdoes not know what media is playing or where it's outputting files to, and cannot alter these paths.rffmpegcannot turn on or off specialffmpegoptions depending on the host selected.
Thus it is imperative that you set up your entire system correctly for rffmpeg to work. Please see the SETUP guide for more information.
Right now, no. I've thought about implementing this more than once (most recently, in response to Issue #21) but ultimately I've never though this was worth the complexity and delays in spawning that it would add to the tool. That issue does provide one example of a workaround wrapper script that could accomplish this, but I don't see it being a part of the actual tool itself.
First, run though the setup guide again and make sure that everything is set up correctly.
If the problem persists, please check the closed issues and see if it's been reported before (if it's regarding Emby and you get an "error 127", see Issue #10).
If it hasn't, you can ask in our chat or open a new issue. Ensure you:
-
Enable debug logging in
rffmpeg.yml(logging->debugtotrue) and re-run any failing or incorrect command(s) to obtain debug-level logs for analysis. -
For issues, use a descriptive and useful title that quickly explains the problem.
-
Clearly explain (in the body of the issue or in your chat message) your setup, what is going wrong, and what you expect should be happening. Don't fret if English isn't your first language or anything like that, as long as you are trying to be clear that's what counts!
-
Include your
rffmpeg.logand Jellyfin/Emby transcode logs as these are absolutely critical in determining what is going on. Use triple-backticks ("```") to enclose logs inline, both in chat and in issues.
I will probably ask clarifying questions as required; please be prepared to run test commands, etc. as requested and paste the output.
Absolutely - I'm happy to take pull requests for just about any bugfix or improvement. There is one exception: please refer to the "Can rffmpeg mangle/alter FFMPEG arguments?" entry above; unless it's really good work with a very explicitly defined limitation, I probably don't want to go down that route, but I'm more than willing to look at what you've done and consider it on its merits.
I'm always happy to help, though please ensure you try to follow the setup guide first - that's why I wrote it! Support can be found on Matrix or via email at joshua@boniface.me. Please note though that I may be unresponsive sometimes, though I will get back to you eventually I promise! Please don't open Issues here about setup problems; the Issue tracker is for bugs or feature requests instead.