>>1557812The console/command line doesn't bite. In fact it likes to be petted and fetches slippers.
It only looks scary at first sight until you actually understand the few elements of the command.
The typical cammand to convert to webm is sth like this
ffmpeg -i input.mp4 -c:v libvpx[-vp9] -c:a libvorbis -crf [q] -b:v [br] output.webm
Sounds scary? It's not once you understand the parameters. Let's break them down
-i: input, tells it that next comes a filename of the input file
-c:v: "c"odec for "v"ideo, tells it the codec to use, webm uses VP8 or VP9, which is in the library libvpx or libvpx-vp9
-c:a: "c"odec for "a"udio, vorbis is a free audio codec and standard for webm
-crf: Constant Rate Factor, a rough quality parameter, the LOWER q is the better the quality but the bigger the filesize. 20 is usually a good value.
-b:v: "b"itrate for "v"ideo, allows you to specify your target bitrate more exactly. Higher bitrate means higher quality but multiply the number by the duration in seconds to roughly get the filesize.Yes, there is also -b:a where you can for example specify that 64kbit/s is enough for the audio.
Obviously a chosen bitrate kinda collides with the CRF as a quality estimate. It's one or the other. if you specify the CRF br must be 0, otherwise just use CRF and don't add -b:v
Finally you give the filename for your output file with an extra parameter.
That is all! Once you know these few parameters and their meaning it is super easy.
Now all of these are for FINE-tuning. You CAN just input ffmpeg -i input.mp4 output.webm, then it recognises the extension "webm" and converts it with the values IT thinks are best, usually resulting a too large file to post on 4chan. So all those scary parameters were just OPTIONS to allow exact tailoring to your needs.
