Fix ffmpeg Not Found in Universal Modder Video Tools

Make ffmpeg available to the same terminal or agent process that runs um, then run ffmpeg -version there. The Universal Modder Python package does not by itself supply a general ffmpeg executable for every operating system.

If the shell cannot start um at all, use Universal Modder CLI discovery checks first. This page applies once the CLI runs and its video operation reports a missing media executable.

The error message

In Universal Modder 0.2.0, the traceback ends with this line:

text

Select code

FileNotFoundError: [Errno 2] No such file or directory: 'ffmpeg'

You can select the code to copy it manually.

um video probe raises it when neither ffprobe nor ffmpeg is discoverable on the executable search path. The command fails before it opens any media, so no recording, conversion or game interaction takes place. The video probing fallback shows the lookup order.

Quick fix

Use the FFmpeg project's download page to select an installation route for your operating system. Then open a new terminal and check:

Select code

ffmpeg -version
ffprobe -version

You can select the code to copy it manually.

A version banner shows that this shell can start the program. If the command remains missing, check where the executable was installed and add its containing directory through your operating system's normal PATH configuration. Preserve the other existing entries.

Find the environment that is failing

On PowerShell:

powershell

Select code

Get-Command ffmpeg -All
Get-Command ffprobe -All

You can select the code to copy it manually.

On Bash or Zsh:

Select code

command -v ffmpeg
command -v ffprobe

You can select the code to copy it manually.

Run these checks in the same environment as the failure. A Windows installation is separate from tools available inside WSL, and a desktop agent launched earlier may still have its old PATH. Reopen the affected terminal or agent after changing that configuration.

If the normal terminal passes but an agent fails, ask it to report executable discovery and version output without starting a recording. Compare those paths with your terminal's result. Reinstalling the agent skill is unlikely to repair a missing media executable.

Distinguish ffprobe from ffmpeg

In version 0.2.0, um video probe prefers ffprobe. When ffprobe is absent, it tries to read a media banner with ffmpeg. If both are missing, that fallback produces the error above. Install a suitable FFmpeg distribution that includes the tools your workflow needs.

A message saying that an input file cannot be read is a later stage: the program was found, but the chosen file or format failed. Check the file path instead of repeatedly editing PATH. The um video reference shows valid argument order for probe, contact sheets and compilation.

Windows recording has an extra requirement

um win uses Windows capture tooling. It searches for a Windows ffmpeg with gfxcapture, and its own setup command can download a checksum-verified build. A generic ffmpeg version banner does not mean capture support is present.

Inspect the setup options before choosing that route:

text

Select code

um win setup --help

You can select the code to copy it manually.

If you run setup, it changes your local tool installation. Use the Windows command reference to distinguish screenshot/recording requirements from ordinary video editing. To point um win at a specific Windows executable, set UM_FFMPEG_WIN; the Windows implementation shows how it is used.

Verify the original operation

After executable discovery succeeds, retry the original command with a small media file you own. Review any new error separately. See installation requirements, the troubleshooting index and the Universal Modder tutorial for the surrounding workflow. When requesting help, include the command, redacted error, CLI version and relevant ffmpeg version output.