FFmpeg_Malin
FFmpeg_Malin est un conteneur FFmpeg + SSH/SFTP entièrement automatisé et prêt à l’emploi.
Platform availability
Available on 1 of 10 platforms
- Unraid
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
84/100 Excellent
- Maintained
- 100last commit 21 days ago
- Popular
- 9666,153 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- No data
Based on 3 of 4 factors.
Availability: platform listings confirmed today, links checked 28 days ago
- GitHub stars
- 66,153
- Open issues
- 3
- Last commit
- 2026-10-31
- Activity
- rising
Checked 21 days ago - source: GitHub (FFmpeg/FFmpeg)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is not supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Install the npm package first Run `npm install @mmomtchev/ffmpeg` in the folder where your app lives. npm is the package installer that comes with Node.js, and this step gives the app the FFmpeg code it needs; without it, media processing will fail immediately. source
- Let the install finish The install can also trigger building the actual FFmpeg programs the app runs, so let it finish before testing. Cancelling early can leave missing pieces and make media processing fail later. source
- Use real file paths When trying the examples, replace the sample file names with paths to files that actually exist on your machine. A missing or mistyped input or output path is the most common first-run mistake and will stop the example from working. source
- No configuration required The container is fully automated and needs no manual setup: persistent Secure Shell (SSH) host keys are generated on first start, users are created from the users.conf file (automatic or manual), and SFTP transfers are stored in /data/home. GPU hardware acceleration (NVENC or VAAPI) is enabled automatically when the hardware supports it. source
Fetched 45 days ago - each note links to its source
Variants
Alternatives (9)
- Adobe Media Encoder - Standalone media encoding tool with a streamlined interface, Adobe suite integration, direct export capabilities, and extensive format supp…
- Avidemux - Avidemux is a free video editor designed for simple cutting, filtering, and encoding tasks.
- File Converter - File Converter is a self-hosted, module-based .NET application that converts files between formats and generates documentation for archivin…
- Freemake Video Converter - Freemake Video Converter is video converter that lets convert videos to avi, wmv, mp4 (iPhone, iPod, iPad, PSP, xBox), 3gp, rip dvd, extrac…
- HandBrake - HandBrake is a lightweight Docker container that lets homelab users transcode video from nearly any format into widely supported codecs thr…
- MKVToolnix - MKVToolNix is a Docker container that provides a web-based graphical interface to the MKVToolNix suite for creating, altering, and inspecti…
- Shutter Encoder - Shutter Encoder is a free professional encoding and conversion software for everyone, developed with video editors.
- StaxRip - StaxRip is a video encoding app for Windows with a unrivaled feature set and usability.
- Video Compression - Compress Videos for Free.
Checked 54 days ago - source: AlternativeTo
Common questions
Why does a FFmpeg process in the container stop or wait after showing a tty output message?
The FAQ says the problem is that FFmpeg checks console input when it runs. The OS can suspend the process until it is in the foreground.
What resource issue appears first when self-hosting FFmpeg for many conversions?
The article says memory comes first because FFmpeg does not stream video and loads the file. The author stopped self-hosting and built an API instead.
Why can a FFmpeg command succeed manually but fail when scheduled in the container?
The troubleshooting page covers why a command can work in the shell but fail under cron. It lists errors with the real cause ordered by likelihood.
Can I ask interactive FFmpeg command-line usage questions on Stack Overflow?
The tag page notes that interactive use of the command-line tool is off-topic.
Answers sourced from ffmpeg.org, stackoverflow.com, www.ahosting.net, www.rendrift.io
Community
- ffmpegX general discussion - VideoHelp Forum (forum)
- Newest 'ffmpeg' Questions - Stack Overflow (forum)
Collected 53 days ago - public community threads