I know what most of the tar command line parameters do from memory and how to use it.
I can also do pretty much everything which ffmpeg.c is capable of doing, as long as hacks aren't being resorted to.
I think I've got a thing for complex command line interfaces.
Its simple interfaces like imagemagick/tragick with which I have to look at stuff, and that's only if I really have no choice but to use it instead of ffmpeg.
@lynne c-can we easily do video glitch with ffmpeg? I heard there is a glitch “codec” but it doesn’t work last time I tried it
@duponin ffmpeg -i <input> -c:v copy -bsf:v noise=amount=1 -c:a copy -y <output>
Produces the following (transcoded because I don't know how browsers/devices will handle streams with corrupt bitstreams).
There are more advanced things you can do like drop every I-frame, but I didn't bother with it. You can adjust the random bits flipped with the amount parameter.
Original is at youtube://Sqw4Q6t3Jls
@lynne oh heck you got a 1up on me for understanding how tar works from memory lol, haven’t quite mastered that one yet
>I think I’ve got a thing for complex command line interfaces same. i too have no idea how imagemagick works but can shit out huge arcane ffmpeg commands to make it do what i wish
@Illya Same, but most of the time unless I'm writing some code myself I'll use the CLI. Its just convenient.
Though if I do have to change filters at specific time I'll use the CLI.
I don't know much of ffmpeg - only -i -f -acodec -vcodec -ss -t
But I do know most tar options I need from memory, same with iptables.
What these things have in common is a highly regular, orthogonal CLI.
A Mastodon instance for people interested in multimedia, codecs, assembly, SIMD, and the occasional weeb stuff.