I wanted to see if you offer an option to save the cmdline equivalent so I can use the UI to test drive, and then save a script to re-run in command shells
While not as complex as the full FFmpeg CLI options, the MKVToolnix suite has a large option set and having the GUI create usable CLI snippets is very handy for setting up large batch jobs on hundreds and thousands of AV files.
`sudo xattr -d com.apple.quarantine $BINARY_NAME`
Edit:
file FFMPEG-UI.AppImage
FFMPEG-UI.AppImage: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, BuildID[sha1]=4b12022a0a60af0d4b7920deac219fcbd1d92080, stripped
It was compiled for 64 bit ARM...I'm curious, what is used as the UI toolkit.
#!/bin/bash
# Set the input file name
input_file="input.mp4"
# Trim the videos
ffmpeg -i $input_file -ss 00:01:08.5 -to 00:01:11.05 -c copy shot1.mp4
ffmpeg -i $input_file -ss 00:01:13.3 -to 00:01:22 -c copy shot2.mp4
ffmpeg -i $input_file -ss 00:01:24 -c copy shot3.mp4
# Prepare the list of files to concatenate
echo "file 'shot1.mp4'" > files.txt
echo "file 'shot2.mp4'" >> files.txt
echo "file 'shot3.mp4'" >> files.txt
# Concatenate the video segments
ffmpeg -f concat -safe 0 -i files.txt -c copy output.mp4I use MacBook Air 2017 running Monterey. Hmmm...
Update: Just noticed the app name after running the dmg: "FFMPEG UI 1.0.0-arm64"
Operating system user interface guidelines exist for a reason. They make sure that software is accessible for users and consistent on the platform. Sure it's fine to get creative if you're making a game or something, but this thing is a tool.
And it's a proprietary app, so I can't change this stuff.