As of Handbrake 1.3.0 update, WebM support was added. This renders this whole script useless. Just use this.
Automation of HandbrakeCLI and FFmpeg to render most video formats and gifs into webm.
More as a personal use thing. It's definitely in no condition to be released to public. If anything, I'd rather not have anyone even look at this trainwreck.
As we know, Discord's file sharing limit is 8MB. That means, you either use some sort of file-sharing service (like MEGA or Firefox Send), or you squash that file down.
Seeing gifs going over 30MB on some websites is also frustrating. With this, you can squash it down to 80% of it's size (depending on the settings of course, but generally, defaults are good). If it says anything, I used batch processed a lot of debatable hentai gifs. Here's some comparisons. (Don't judge. I know you ain't any better.)
Ironically, I actually hated webms. A LOT. Prejudice, perhaps.
Currently, it uses python, because doing all of this in batch was just straight up pain in the ass.
For Gituwe.py, after launching, you wanna drag-drop the file you wanna convert into the window. From there on, you go through the settings. Pretty much self explanatory. File name, video bitrate, audio bitrate, if you wanna resize, and then it starts the conversion.
Kinda broken. I'm unsure what keeps throwing an error. So far, the folder name should have no spaces. Not too sure about filenames.
Batch processing works on folder, rather than file. Anything you wanna convert, add to that folder, and then throw it into it. Thing is, you're gonna have to edit the code yourself, as I found out, python imports are just annoying.
The line you need to edit is where "merge" variable is.
To my surprise, video 1000kb/s seems to hold itself up pretty well. Going down seems to start giving artifacts. As for audio, it's using Opus, and even if you set that to "1", you'll feel like living in 90's, but it's understandable. Usually, 16kb/s is even good. As much as I know, mp3 would have failed hard at that point.
** If you can't take chances with audio glitching and so forth, 64kbps should be good. 32kbps seems to hold up hentai well with little glitches (tested on 128kbps AAC with lots of changes in audio) **
Either way, you're just gonna have to try yourself. Do keep in mind, that the point isn't super-ultra-clear quality. Anything that ever steers from original material, can never be as good as the original.
Fuck that. Snag it, if ya find any value in this. As of 19-09-2019, it will probably not get any updates. So go ahead.