>>4916
breddy good. You're not really doing anything wrong as far as I can tell, but I still have plenty to learn about ffmpeg so I might be missing shit. Try using VP9 and opus instead (for video/audio respectively), VP9 used to be slow as fuck but it got multithreading support a few months ago and it's actually pretty useable now. It's still slower than VP8 (a third to a half the speed), but the quality difference is quite significant and the conversion like that one will still be over within ~5-10 minutes. As far as general quality of videos you can use on 8ch go, VP8/vorbis webm<h264/aac mp4<VP9/opus webm. Here's an example of some commands to use:
ffmpeg -ss 00:02:15 -i input.mkv -vf scale=1280:-1 -to 00:03:14 -c:v libvpx-vp9 -pass 1 -b:v 1000k -threads 4 -speed 4 -tile-columns 2 -frame-parallel 0 -auto-alt-ref 1 -lag-in-frames 25 -c:a libopus -b:a 96k -f webm NUL
ffmpeg -ss 00:02:15 -i input.mkv -vf scale=1280:-1 -to 00:03:14 -c:v libvpx-vp9 -pass 1 -b:v 1000k -threads 4 -speed 1 -tile-columns 2 -frame-parallel 0 -auto-alt-ref 1 -lag-in-frames 25 -c:a libopus -b:a 96k -f webm papa_look.webm
-vf scale just scales the resolution according to the source video (-1 scales according to aspect ratio, so a 16:9 video will give an output resolution of 1280 by 720 in this case)
Replace NUL with /dev/null if you use linux. And try -ss in different positions if the original arrangement doesn't work (before or after -i like in your commands, I can't remember which one you're supposed to go with).
Using VP9 you should be able to get rid of the majority of the artifacting. Check out the official guide (http://wiki.webmproject.org/ffmpeg/vp9-encoding-guide) to learn more.