3 ms·
The concept of this would be incredibly useful...I use FFmpeg every few weeks, which is not often enough to remember all the commands I need. But the execution
by Ansil849 4y ago
The concept of this would be incredibly useful...I use FFmpeg every few weeks, which is not often enough to remember all the commands I need.
But the execution here is a bit lacking. This only lets you input basically 10 parameters.
If this were to be expanded to include all FFmpeg params, it would be INCREDIBLY useful.
- mihaitodor 4y agoYou might find this tool useful: https://handbrake.fr/ https://handbrake.fr/
- Ansil849 4y agoI don't use FFmpeg for transcoding, more for stream manipulation and frame/stream/subtitle extraction and related tasks, so unfortunately Handbrake isn't really a viable solution.
- RealStickman_ 4y agoMaybe https://mkvtoolnix.download/ https://mkvtoolnix.download/ fits your usecase then. It allows you to select enabled streams, edit metadata and a lot of other things I haven't tried yet for mkv and other container formats.
- webmobdev 4y agoIf you have macOS, check out https://subler.org/ https://subler.org/ (free, open source).
- smcnally 4y agohttps://github.com/mifi/lossless-cut https://github.com/mifi/lossless-cut exposes more ffmpeg params.
- flemhans 4y agoWould be nice, but also a big task to make a user interface for everything. The filter chain system, for instance, is quite complicated. But of course there could be some compromise.
- smcnally 4y ago> I use FFmpeg every few weeks, which is not often enough to remember all the commands I need. Very Much this. Even the `ffmpeg` incantations I use frequently are tough to recall -- like creating a gif `ffmpeg -i input.mkv -vf "fps=8,scale=512:-1:flags=lanczos,split[s0][s1];[s0]palettegen[p];[s1][p]paletteuse" -loop 0 output.gif` The info will be in my notes and `.bash_history`, but less friction recalling it helps stay in context of the incantation called for at the moment that prompted the search. I'll tag, edit, and add notes to running *ffmpeg recipes*[0] when I'm being diligent. This helps reïnforce details for next time, as does reviewing and rubber-ducking here, but still with less-than total recall. What else works to recall more / more quickly? c.f. `awk`, `grep`, `find` and others. [0] https://smcnally.github.io/kb/ffmpeg%20recipes https://smcnally.github.io/kb/ffmpeg%20recipes