With bitrate between 1000K-2000K depending on the type of the video. However, the resulting file is still way too big. For example, the settings above produce a 10mb video 40 seconds long. Whereas if I encode it into x264 with the slowest preset, I can get it down to 4mb.
Yeah, sucks that there is no crf setting. When I encode memes to post here I just kind of aim for the highest bitrate that could fit within 3 or 4 mb. Also, Hiro should add support for h264, vp9, av1 and opus. Others already have.
Cameron Thomas
>I'm so smart for using ffmpeg command line to encode my webms >But I also don't know that VP8 supports CRF.
Bitrate and size are changed as needed per video/board. I know it can be improved greatly, but I rarely make webms so I haven't invested the time in refining it.
Leo Robinson
Ah shit i guess i was using an old build of ffmpeg or something and couldn't use crf then. Well now i know.
webm is just bait to hook people to watch your youtube video, no need to provide quality
Aiden Johnson
I am impressed
Nathan Brown
What is the source?
Gavin Williams
I just use the webm script for mpv. It just werks.
Aaron Wilson
Might as well ask here.
With x264 and x265 you can use a constant rate factor (crf) or constant quantization parameter (qp). libvpx on the other hand offers a cq level for constant/constrained quality mode. My question is, what is cq supposed to represent? A factor for perceived quality (crf) or rather strictly mathematical loss (qp)? vpxenc's help text doesn't help me either. --cq-level is described as constant/constrained quality level, but --min-q and --max-q as min/max quantizer and they use the same same scale from what I can tell.
>For example, the settings above produce a 10mb video 40 seconds long. Like expected >2000Kbps * 40s / (8 * 1024) ~= 10MB x264 shouldn't produce a smaller file size. For a target bitrate slower presets will provide a better quality, for a target quality slower presets will provide a smaller size.
Parker Morris
>It just werks. Except when you want to hardsub bitmap-based subtitles. Both encode.lua and webm.lua use simple filters exclusively.
Isaiah Reed
>he uses bloatware media player to encode his videos Nigger what are you doing
Robert Ross
>mpv >bloatware IIRC works fine for me, I'll check later when I'm home if thread hasn't 404d
Christian Howard
I thought this was the official Jow Forums webm converter ;^)
>Wanting to fast forward straight to the product instead of learning a bunch of stupid ffmpeg calls is considered "dumb" the absolute state of autismos
Brody Ross
Text-based subtitles work fine. Bitmap-based subtitles require the overlay filter though, which is a complex filter as it takes two input streams. You'd need to add it via -filter_complex or --lavfi-complex (depending on whether you call ffmpeg directly or mpv), which neither script does. >encode.lua if #filters > 0 then append_args({ "-filter:v", table.concat(filters, ",") }) end
>webm.lua (master) or webm.lua (ffmpeg-support) with mpv backend for _index_0 = 1, #filters do local f = filters[_index_0] append(command, { "--vf-add=" .. tostring(f) }) end
It's made for non-gentoomen who want to shitpost but are too dumb to use cli. >faster >gives more control >cross-platform >bleeding edge encoders >cli baaaaaaaad
Jayden Smith
I like webm for retards. How the fuck can you accurately crop, trim, etc. with only CLI this easily?
Here you go. You could also use any subtitle track ripped directly from a DVD/Blu-Ray. x0.at/sD4.mkv As a heads-up, these subtitles are a bitch to work with. Trimming included (and I had to trim them as I can't easily upload a >1GB video with my shit internet connection). If you want to hardsub this file with overlay, you need to use overlay=shortest=1, because the timestamps got fucked up when I trimmed it. Hardsubbing directly from the original file works fine with the default overlay filter.