Clypra Version
0.1.0
Platform
macOS (Apple Silicon)
What happened?
As-salamu alaykum, Abdulkabir!
I’m a huge fan of Clypra—this Tauri + Rust video editor is incredibly snappy and well-built.
However, I recently ran into a critical barrier when installing Clypra via Homebrew on macOS. The export functionality completely blocked me with an "FFmpeg missing" error, even though I had FFmpeg configured in my system environment.
🔍 The Root Cause
After diagnosing the package script, I found that the current Homebrew Cask formula inside your homebrew-tap repository lacks an explicit dependency declaration for FFmpeg. If a user installs the app on a clean macOS environment via Brew without manually setting up the FFmpeg formula beforehand, the app cannot bridge the core binaries.
🛠 The Fix (PR Submitted)
I have successfully fixed this issue by adding depends_on formula: "ffmpeg" into the cask configuration and tested it locally.
Since your main repo handles the core application logic, I have submitted the actual code fix as a Pull Request directly over at your Tap repository.
👉 Here is the PR link: [https://github.com/AIEraDev/homebrew-tap/pull/1]
Whenever you have a moment, please check out the PR over there to merge it. This will completely automate the FFmpeg setup for all future macOS/Homebrew users!
Thank you again for your wonderful work on this project.
Barakallahu feek!
Steps to reproduce
To reproduce this issue, you can simulate a fresh macOS environment where Clypra is installed via Homebrew but ffmpeg is missing from the Homebrew dependencies.
Here are the step-by-step instructions:
1. Simulate an environment without Homebrew's FFmpeg
If you already have ffmpeg installed globally via Homebrew on your Mac, temporarily unlink it to mimic a clean user environment:
brew unlink ffmpeg
### Expected behavior
When a user runs `brew install --cask clypra`, Homebrew should automatically detect, download, and link `ffmpeg` as a strict pre-requisite before completing the Clypra installation.
Once installed, the user should be able to open Clypra and export their videos immediately without encountering any "FFmpeg missing" onboarding errors, ensuring a seamless, zero-config setup out of the box.
### Actual behavior
Currently, because the dependency is missing in the Cask formula, Homebrew installs Clypra as a standalone application without fetching `ffmpeg`.
When a user tries to export a video, the application throws a persistent error stating that FFmpeg is missing/required, completely blocking the core rendering and export pipeline. This forces users to manually figure out environment paths or troubleshoot system dependencies themselves, which breaks the seamless installation experience.
### Error logs (if any)
```shell
Additional context
No response
Clypra Version
0.1.0
Platform
macOS (Apple Silicon)
What happened?
As-salamu alaykum, Abdulkabir!
I’m a huge fan of Clypra—this Tauri + Rust video editor is incredibly snappy and well-built.
However, I recently ran into a critical barrier when installing Clypra via Homebrew on macOS. The export functionality completely blocked me with an
"FFmpeg missing"error, even though I had FFmpeg configured in my system environment.🔍 The Root Cause
After diagnosing the package script, I found that the current Homebrew Cask formula inside your
homebrew-taprepository lacks an explicit dependency declaration for FFmpeg. If a user installs the app on a clean macOS environment via Brew without manually setting up the FFmpeg formula beforehand, the app cannot bridge the core binaries.🛠 The Fix (PR Submitted)
I have successfully fixed this issue by adding
depends_on formula: "ffmpeg"into the cask configuration and tested it locally.Since your main repo handles the core application logic, I have submitted the actual code fix as a Pull Request directly over at your Tap repository.
👉 Here is the PR link: [https://github.com/AIEraDev/homebrew-tap/pull/1]
Whenever you have a moment, please check out the PR over there to merge it. This will completely automate the FFmpeg setup for all future macOS/Homebrew users!
Thank you again for your wonderful work on this project.
Barakallahu feek!
Steps to reproduce
To reproduce this issue, you can simulate a fresh macOS environment where Clypra is installed via Homebrew but
ffmpegis missing from the Homebrew dependencies.Here are the step-by-step instructions:
1. Simulate an environment without Homebrew's FFmpeg
If you already have
ffmpeginstalled globally via Homebrew on your Mac, temporarily unlink it to mimic a clean user environment:Additional context
No response