>encoding WebMs in VP9 on ffmpeg is slow as fuck compared to VP8
Send me the video you're trying to encode and the settings on libvpx, because the last time someone claimed that vp9 is impossible to encode in I tried a random video and got 4 fps single threaded on a laptop CPU. That's definitely slow, but it's not that bad.
I'm using WebM for Retards, though, which is basically a frontend for ffmpeg plus AviSynth.
The source is a few MB-large AVI that's not even 1 minute long. It took a few minutes to convert.
I think the exact line I used wasffmpeg -i input.mp4 -c:v libvpx-vp9 -b:v 1M -na -threads 1 output.webm
With the files obviously changed. Let me try it again with a short video and see what happens.
libvpx encoders are just slow in general compared to H.264 & H.265. Of course VP9 is slower due to being a more complex & efficient codec, but building a codec without violating patents is kinda difficult.
Interesting, single threaded was around ~5 fps, but doing -threads 3 seemed to only spike my CPU to like 60%, and still it said 6 fps, which seems too low for using at least double the resources.
I'm not sure how the stdout works with ffmpeg but the 3 threaded test seemed to finish much quicker. I don't know if it was 3x quicker though.
Oh fuck yes finally a Zeranoe binary for Windows which includes libvpx 1.5.0.
I remember getting 0.7 frames a second encoding on practically the highest possible quality two pass encodes with VP9. I'll try those placebo-level settings with this new library. It's supposed to hold some performance and quality improvements but I have no idea if they will make any difference here.