>>15511
>Is it quick to encode audio webms?
Yes, certainly much more than videos even with VP9 enabled. There's a couple of details i forgot how to handle but the recipe i found always gives me decent results. In my PC for example the first webm, Play on the Sands, took me 10 seconds to encode.
ffmpeg -r 1 -loop 1 -i A.jpg -i 1.mp3 -c:v libvpx-vp9 -c:a libopus -b:a 96k -t 4:45 1.webm
I do have to set the specific time because the option to finish encoding at the end of the audio is pretty buggy as it continues indefinitely sometimes or abruptly finishes before.
I suppose you know the parameters but for anyone who doesn't and wants to try out:
"-r 1" is the desired framerate per second, 1 is the basic for just a single image i think, there might be another option to make the image stream static
"A.jpg" is the name of the image file you want.
"1.mp3" is the name of the audio file accompanying it.
"-c:v libvpx-vp9" is the video encoder, it's either "libvpx-vp9" or "libvpx", the difference i think it's the latter being VP8 and the former the VP9 checkmark in the "WEBM for Retards/Bakas" GUI, which makes it more lightweight but takes longer.
"-c:a libopus" is the audio encoder, it's either "libopus" or "libvorbis". Opus is, in very broad terms, the upgrade from Vorbis but i think both are recognized as .ogg at the end of the day.
"-b:a 96k" is the audio bitrate. While the bare minimum should be 128k i found that 96k is more than enough for these preview purposes unless the original audio is a very contemporary production like a WavPack or a kinky ASMR.
"-t 4:45" is the total runtime of the audio, there's an option to detect it automatically but like mentioned it's not very reliable.
"1.webm" is the name of the desired final product.
Obviously these commands are injectePost too long. Click here to view the full text.
