Troubleshooting FFmpeg Installation on Apple M1 Devices

Troubleshooting FFmpeg Installation on Apple M1 Devices

5 April 2024 Stephan Petzl Leave a comment Tech-Help

When working with video processing on Apple M1 devices, users may encounter certain errors that can hinder the functionality of important tools like FFmpeg. This guide is designed to help you resolve a common issue related to library dependencies which can occur when running the FFmpeg command.

The Problem

Some users have reported encountering an error when trying to run the ffmpeg command after installing it through Homebrew. The error message typically looks like this:

            dyld[XXXXX]: Library not loaded: '/opt/homebrew/opt/mbedtls/lib/libmbedcrypto.13.dylib'
            Referenced from: '/opt/homebrew/Cellar/librist/XXXX/lib/librist.4.dylib'
            Reason: tried: '/opt/homebrew/opt/mbedtls/lib/libmbedcrypto.13.dylib' (no such file), '/usr/local/lib/libmbedcrypto.13.dylib' (no such file), '/usr/lib/libmbedcrypto.13.dylib' (no such file), ...
            zsh: abort      ffmpeg -version
        

This error indicates that the required library libmbedcrypto.13.dylib is not found in the expected locations on the file system, which can prevent FFmpeg from functioning correctly.

The Solution

The following steps have been identified as a reliable solution to resolve the issue:

  1. Uninstall the librist package, which is a dependency that might be causing the conflict. Use the following command to uninstall it without removing its dependencies:
  2. brew uninstall librist --ignore-dependencies
  3. Uninstall the mbedtls package using a similar approach:
  4. brew uninstall mbedtls --ignore-dependencies
  5. Reinstall FFmpeg, which should also reinstall any necessary dependencies including a fresh version of mbedtls that should not conflict with FFmpeg:
  6. brew reinstall ffmpeg

By following these steps, the FFmpeg installation should be corrected, and the command should run without the previously encountered error.

Conclusion

Errors like the one discussed can be frustrating, but they are often due to conflicts between library versions or missing dependencies. Reinstalling the problematic components usually resolves these issues. If you’re experiencing similar problems on your Apple M1 device, the outlined steps should help get your FFmpeg installation back on track.

Like this article? there’s more where that came from!