This is really useful, thanks. Especially the duration point ... I knew duration obviously affected size, but I hadn’t thought about actually showing the user what they gain by trimming instead of just letting the optimizer keep sacrificing quality.
The 14s to 360px , 6s to 456px ... kind of message is a really good idea because it makes the tradeoff obvious.
I am also going to look at the search order. Right now it searches a mix of width,fps,colors based on a quality score, but I agree that letting fps fall too low can make the game itself look bad. A 12 fps floor for the normal preset probably makes sense.
Crop is something I was already considering, but your point about it being basically free resolution pushes it much higher on the list. I’d probably start with manual crop before trying automatic border detection.
And thanks for giving me an actual benchmark. I am going to run a few comparable clips through mine and see where it lands.
Also good catch on the utm parameter. I will clean that up.
This is exactly the kind of feedback I was hoping to get from releasing it early.
... If you want to try the current build, I can give you a free copy . I would be interested to see how it performs against your own FFmpeg setup
Here’s a download key[:https://rodian1.itch.io/gif/download/y39VApmbxTzglqgGpHcoxvojUPwoeQOF5IYKH7T1]
No pressure, but if you test it I’d really like to know where mine performs worse/better than yours.