FFmpeg Auto-Install
Medix needs ffmpeg and ffprobe to do actual conversion, but you don’t
have to install them first. On every run, Medix checks whether both binaries
are on PATH. If not, it:
- Detects your operating system and architecture
- Probes for a supported package manager
- Offers to run the right install command for you
You can always say no and install manually.
Supported managers
Section titled “Supported managers”| Platform | Detected managers |
|---|---|
| macOS | Homebrew, MacPorts |
| Debian / Ubuntu | APT |
| Fedora / RHEL / CentOS | DNF, YUM |
| Arch Linux / Manjaro | Pacman |
| Windows | winget, Chocolatey, Scoop |
Manual install reference
Section titled “Manual install reference”If you’d rather install FFmpeg yourself:
brew install ffmpegUbuntu / Debian
Section titled “Ubuntu / Debian”sudo apt updatesudo apt install ffmpegFedora
Section titled “Fedora”sudo dnf install ffmpegRHEL / CentOS
Section titled “RHEL / CentOS”Enable RPM Fusion first, then:
sudo dnf install ffmpegArch Linux
Section titled “Arch Linux”sudo pacman -S ffmpegWindows — winget
Section titled “Windows — winget”winget install Gyan.FFmpegWindows — Chocolatey
Section titled “Windows — Chocolatey”choco install ffmpegWindows — Scoop
Section titled “Windows — Scoop”scoop install ffmpegVerifying the install
Section titled “Verifying the install”ffmpeg -versionffprobe -versionBoth should print version info. If either says “command not found”, make
sure your shell has re-loaded PATH after install (open a new terminal).
Troubleshooting
Section titled “Troubleshooting”“FFmpeg is installed but Medix can’t find it” — make sure it’s on
PATH. On Windows, check Environment Variables → PATH. On macOS/Linux,
run which ffmpeg — it should print a path.
“Package manager not detected” — Medix falls back to printing manual install instructions for your platform. File an issue if you think a manager should be supported.