Troubleshoot
Fixes for the problems people hit most with Ampliflare Audio, from a missing ffmpeg to the weekly limit. Start with the one that matches what you see.
Where to get help
Section titled “Where to get help”Stuck, or found a bug? Open an issue on GitHub. Say what you did, what you expected, and what happened instead.
The fixes below cover the problems people hit most, so you may find your answer right here.
“ffmpeg was not found”
Section titled ““ffmpeg was not found””Ampliflare Audio uses ffmpeg to read and write audio, and it is installed separately. Install it, then quit and reopen the app.
- macOS:
brew install ffmpeg, with Homebrew. - Windows:
winget install ffmpeg, then make sure it is on yourPATH. - Linux: your package manager, like
sudo apt install ffmpeg.
“Weekly limit reached”
Section titled ““Weekly limit reached””Free use allows 20 files a week. The sidebar says when the count resets. A license removes the limit, and is needed for work anyway. See personal and commercial use.
“This key is already on as many computers as it allows”
Section titled ““This key is already on as many computers as it allows””Remove the key from a computer you no longer use: open Commercial license in its sidebar and click Remove from This Computer. Then activate it again here.
Windows says the file is not safe
Section titled “Windows says the file is not safe”The Windows files are not code-signed yet, so SmartScreen shows a warning. Click More info, then Run anyway.
macOS says the app is damaged
Section titled “macOS says the app is damaged”Download the disk image again with your browser, and open it without copying the app through another tool first.