Shailsic
10/11/21 06:02PM
Converting videos to gifs/webm?
Would love to post someone of my favorite videos and clips here but don’t know how to make them the right file
Lemons22
01/19/22 04:25PM
Phew...late response here I know, but you don't necessarily have to convert an MP4 to a WEBM. The site can do that for you. Just upload your MP4. The site's conversion isn't perfect though, but it's good enough.

I personally use FFMPEG, but there is a steep learning curve and it must be ran from the command line. I honestly have had it installed on my computer forever so I don't remember the exact steps to get it up and running, but if you do manage to install it the command I use and what I've found gets the best-quality WEBBMs is:

ffmpeg -i "in.mp4" -b:v 3000k -b:a 128k -threads 6 out.webm

(And you have to use this command in the same folder as your input file (aka the file you're trying to convert into a WEBM), so you'll either need to navigate to that folder in the command prompt OR just take the file you want to convert and move it to the folder that your command prompt defaults to.)

But what does all that shit mean? I'll tell you.

-i = input. This would be the file name. If I had a video called "sexytime" I wanted to convert then the input command would look like this: -i "sexytime.mp4" (assuming it's an MP4 and most modern video files are. If you're dealing with older files it could be like an MPEG or a WMV)

-b:v = bitrate variable. This is basically the "quality" of the video. I usually just match the quality in the source file. So if you right click an MP4 on your desktop and go properties > details you'll see under the "Video" section the "Data Rate" and "Total Bitrate". I usually place my bitrate slightly below the "Total Bitrate" number. So if the total bitrate is 2,566 I would make my bitrate 2,500 or 2,400. I've found weird shit happens if I place that number ABOVE the total bitrate even a little bit...so rounding 2,566 up to 2,600 wouldn't be a good idea.

If your video ends up being too large for the site (over 100 MB) this is probably the variable you're going to want to mess with. The lower the number the lower the file size, but it also lowers the video quality. I've found you can go as low as 1500k...any lower than that and the video starts looking like shit.

-b:a this is just the bitrate of the audio. Doesn't matter too much in a porn video. Again this number is dependant on the audio bitrate of the input file, so just liek with the -b:v again go into the file's details, but this time look in the audio section. Like I said porn audio doesn't matter much so you can probably just leave this number at 128k at all times and be fine...even files from major porn studios don't usually have audio quality higher than that anyways.

-threads 6 This option is HUGE. I didn't know about it at first and thus conversion took FOREVER, however with this option the time to convert a file becomes somewhat bearable. It allows FFMPEG to utilize more threads of your computer when converting so the conversion goes much faster. For me about 6 seems to be good, I don't notice much of a boost beyond that. If you have a beefy CPU with a ton of cores, and thus a ton of threads, you may get better results by upping this number.

out.webm This is the output file. You can name it whatever you want really. Out is just what I default to, but it coudl be datass.webm deeznuts.webm...whatever you want. The important part of the command is the ".webm" at the end cause that's the file type it will convert to.

That's it
1


Reply | Forum Index