/pone/ - My Little Pony★

but webm's take soooooo long to encode

endchan have 100MB

8ch on twitter

>>297613

then you should go back there

>>297618

Wasn't endchan seized by the FBI?

I've successfully made a 30MB episode. That means I'm close, right?

Maybe tomorrow I'll have it chopped enough.

>>297669

I'd like to see you create a 16MB and relevant reaction image on such a short notice.

>>297677

Checked, and thank you.

*cough*cough*

>>297633

I don't think so, it was working properly for me last couple of months. Maybe you meant some other site?

>>297757

Hey, it's PinkieDash ship fuel! I haven't seen any of that since Season One.

>>297757

It is an actually legitimately funny episode. Several of the jokes landed.

>>297764

Plus she hates washing anyway.

>>297770

Confirming that Rainbow Dash is disgusting was indeed the best part, but I also got a laugh out of Pinkie Pie's slow burn.

>>297757

Try cutting out the intro song and bring the quality up a little.

>>297785

He could stand to cut the credits as well.

>>297794

FFmpeg CLI, 2-pass. 42K/s video, 32K/s audio (opus, 12K sample rate, mono)

I've re-done it in 8Khz audio, 46K/s video. It looks about the same.

>>297785

>>297788

That would require splicing the intro scene back into the creditless segment; I haven't looked into how to do that. But I'll keep it in mind.

>>297795

I keep meaning to dick around with ffmpeg. I have it downloaded but I'm a lazy fat fuck. I'm just used to Xmedia Recode.

Is there a steep learning curve?

>>297796

kinda.

There's a command, and some arguments for everything you want it to do. If you tell it not to do those things, it will do nothing … so you might wind up with a file that has no video, or no audio.

Of course, I had xmedia recode do that to me more times than I can count.

Just do web searches for the thing you want ffmpeg to do, such as resize the video, and add that to the command.

Gimme a minute and I'll post my "cheat sheet" I've accrued on converting .mp4 into .webm

FFmpeg 2-pass

Ffmpeg.exe -i INfile.mp4 -c:v libvpx-vp9 -b:v 500K -speed 4 -frame-parallel 1 -tile-columns 6 -auto-alt-ref 1 -lag-in-frames 20 -c:a libopus -ar 8000 -b:a 36K -threads 6 -ac 1 -pass 1 -f webm OUT.webm

-i = input, -c:v codec of video; -b:v bitrate of video; -speed how careful to be about decisions (lower numbers take more time); -lag gives VP9 some room to shuffle quality; -ar audio sample rate; -threads how much CPU to use; -ac 1 encode in mono; -pass 1 = replace with pass 2 to make the actual file; everything but speed (change to 1, or so) should stay the same.

Also: -ss 0H:0M:0S (accepts decimal seconds) to specify Starting Spot. -t to specify run time (from the starting spot. So, to take one hour of media, and extract the section from 1:1:0.2 to 1:03:1.7 you’d add -ss 61:0.2 -t 0:0:1.5 to any of the above arguments

>>297801

>not maximum allowed value of -lag-in-frames 25

also, do note, that -tile-columns, -tile-frames -frame-parallel and -threads are used to speed up encoding and actually worsen quality of the webm by some amount.

Also don't know exactly i know that's the case with libx264, but ffmpeg should accept all of the options vpxenc exposes, and if you're interested in what they actually do, as opposed to how to use them, this is the way to go about learning them, i.e vpxenc --help

>>297796

>Is there a steep learning curve?

Might be, but, ffmpeg is one of the best documented piece of software out there, if you're not a total retard and can read a good read of manpage/docs will get you 90% of answers you need

>>297757

>we 240p with sever artifacting now

this is still way better than cuckchan can manage