processing / processing/processing4
Issues with FFmpeg (and Movie Maker) - need chmod and the binary is the wrong CPU type
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 494
- Forks
- 183
- Avg merge
- 4h 39m
- Merged PRs (30d)
- 3
Description
Most appropriate sub-area of Processing 4?
Utilities
Processing version
4.4.4
Operating system
MacOS 11.7.10 (Big Sur)
Steps to reproduce this
1.Install 'Movie Maker II' via Tools > Manage Tools.
2.Run Movie Maker.
3. Movie Maker gives the error 'Creating the QuickTime movie failed. Cannot run program "... frmpeg": error=13, Permission denied'
4. Use 'ls' in Terminal to view ffmpeg's permissions. They are '-rw-r--r--'.
5. Use 'chmod' in Terminal to change ffmpeg's permissions to '-rwxr--r-'.
6. Run Movie Maker again.
7. Movie Maker gives the error 'Creating the QuickTime movie failed. Cannot run program "... frmpeg": error=86, bad CPU type in executable.'
8. If I download the 'static FFmpeg binary for macOS 64-bit Intel' from https://evermeet.cx/ffmpeg/ and replace the existing 'ffmpeg', Movie Maker works okay.
snippet
Additional context
Thanks!
Would you like to work on the issue?
No
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing Movie Maker II installation and movie creation on macOS 11.7.10, then inspect the installed ffmpeg permissions and CPU architecture. Done means the bundled executable can run without manual chmod or replacement and Movie Maker successfully creates a QuickTime movie.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100