Transparent webm thread continued

Attached: Capture.png (852x478, 121K)

Your browser is shit

SJW browser?

>-quality best

wtf are you doing nigger
>-quality good -cpu-used 0
give better quality than "best" and is faster too.

>-qmin 30 -qmax 30

give it some breathing room

>-b:v 0

when using -crf, b:v is the max bitrate

so i got the script, but it's only working for images, how do i convert mp4s and webms into transparent webms?
do i need to convert webm to pngs and then transparent and stitch them back together??

nah, you just need to chroma key them and use in final weebum

I can't get the ffmpeg one to work tho

>you just need to chroma key
what does this mean?

>give better quality than "best" and is faster too.
wtf

Attached: How Is Babby Formed.webm (201x252, 442K)

Basically turn a green screen into transparent pixels in some kind of video editor and hopefully some day in ffmpeg

That's fucking creepy when you look at it that way. It's like a parasite taking over.

doesn't work in pale moon

try one of the other fury fox flavors, I know at least one of them threw the towel and added even webp support now.

I don't care, just giving OP feedback

>webmproject.org/docs/encoder-parameters/
>--good This will probably be what most users use most of the time. Within the scope of "good" quality there are 6 further speed steps that are set through the --cpu-used parameter (values from 0 to 5). Setting --good quality and --cpu-used=0 will give quality that is usually very close to and even sometimes better than that obtained with --best but the encoder will typically run about twice as fast. Setting --cpu-used=1 or --cpu-used=2 will give further significant boosts to encode speed, but will start to have a more noticeable impact on quality and may also start to effect the accuracy of the data rate control. Setting a value of 4 or 5 will turn off "rate distortion optimisation" which has a big impact on quality, but also greatly speeds up the encoder.

No, it works in firefox.
He must be using some applel shit.

-crf in combination with -b:v 0 activates constant quality mode.

wtf is wrong with freetards, why is this codec such an absolute half baked Frankenstein?

Attached: ASdLxTi.png (1080x1124, 1.15M)

Attached: Don't lose your head.webm (500x566, 81K)

.gifs are now 100% obsolete

>enormous buttons on top of the content
>mfw

iOS's volume icon still does this after like 5 years.

Attached: green lex luthor.png (321x306, 199K)

>boob gets bigger

Attached: 1538221201660.jpg (319x319, 16K)

script?

Attached: v slut.webm (410x542, 209K)

see

which one in that?

Attached: mother of nyaa.webm (1280x720, 256K)

Because Google never cared to improve it beyond its own needs.
>freetards
Some of the best encoders out there are free as in freedom. What's lacking are good open video standards.

Attached: 1455485990398.gif (1280x720, 3.02M)

noice

Attached: Yuki.webm (140x120, 89K)

First one that ended up bigger

Attached: 1439759808989.gif (140x120, 46K)

someone help me out?

Attached: tr.png (647x98, 49K)

ffmpeg -i "1493400165550.gif" -c:v libvpx -qmin 0 -qmax 18 -crf 9 -b:v 1400K -quality good -cpu-used 0 -auto-alt-ref 0 -pix_fmt yuva420p -an -sn -metadata title="Don't lose your head" "Don't lose your head.webm"

Attached: The great debate.webm (301x301, 277K)

lowercase "in"

That's for wangblows my man, here:
for f in *.{mp4,mkv,gif};
do ffmpeg -i "$f" -an -c:v libvpx -auto-alt-ref 0 -pix_fmt yuva420p "out/${f%.*}.webm"; done

Doesn't work on mobile

Working on brave mobile

GOOD

Attached: 5E844632970F44D98AE159FBF72458C2.jpg (750x706, 117K)

Attached: pol b8.webm (186x250, 43K)

Yeah, works in chromium too, but not clover.

Not all of them. Still cool tho.

Attached: Screenshot_2018-11-20-11-45-59.png (720x1280, 220K)

Attached: Koneko's Koneko'es.webm (250x385, 375K)

Hot as fuck

t. homo

Attached: 0001-0950wooooo.webm (640x360, 1.96M)

This is fucking hard. How are you nerds doing this shit?

Attached: Untitled.png (486x426, 37K)

Attached: Only god knows what she means by this.webm (400x606, 50K)

test

Attached: 1.webm (368x656, 46K)

trying out some different shit. not working.

Attached: miku a slut.webm (300x250, 144K)

Omg her organs are kill

pls work, pls work. pls work

Attached: 0001-0180wooooo.webm (640x360, 523K)

Reee.
Chrome with userscripts.

ikr look up eclampsia

try this out.

no dice lad, did you encode to ARGB or YUVA420?

On phone they both look the same

There's a (screencap floating around of a) write-up from the biologial perspective and it does turn out to be a pretty parasitic/hostile process.

android is trash but at least they're able to open webms natively

v2

Attached: 0001-0083wooooo.webm (640x360, 443K)

Attached: Notice me sempai.webm (125x75, 66K)

you deserve those sweet dubbs of truth.

Is it even possible to convert GIF to WebM without losses (speaking about VP9 not VP8)? I only see yuva420p as pixel format that supports transparency.

This is pretty cool but I wish we'd finally get sound webms on all boards.

Yes, vp9 supports fully lossless encoding

webmproject.org/vp9/profiles/
trac.ffmpeg.org/wiki/Encode/VP9#LosslessVP9

You must manually set profile to 1 or 3 and must include 4:4:4 pixel format in params

Actually scratch that, I'm not sure if yuva444 is possible on ffmpeg.

v3

Attached: 0001-0083wooooo.webm (640x360, 536K)

Still not working

works on my machine (tm)

Dumb phoneposter
The edges are worse on this one.

Chroma keying is hard desu senpai.

I wouldn't know.
What are your filesize gains compared to the original when making them transparent?

Original was 178KB VP9 360p yt stream

Did anybody do further tests with ffmpeg's chromakey filter?

Attached: 1532888322280.webm (1280x720, 283K)

I gave up desu, nothing makes that shit work. Usings nodes in blender was the only way to chroma key for me.

That's what happens with the default settings. Everything black should become fully transparent, but instead everything becomes transparent.

both play transparent but thumbnail has white background while thumbnail is transparent

Chr**e had transparent webms for a decade already

Attached: patchbounce3.webm (720x720, 597K)

never ever shantae fags.
never ever

Hey, that's pretty good

I'll be damned. Using colorkey instead of chromakey works at least partially.

Attached: 1520380522461.webm (1280x720, 350K)

Cancerous webM thread. You assholes should already be beaten senseless for doing that shit to images.

Making progress. ImageMagick can be used to replace transparency with a color that colorkey can detect. Unfortunately the process fucked up the GIF somewhat, but I'm getting there.

Attached: 1518937865541.webm (1280x720, 424K)

Found my old avisynth script for alpha memes

DirectShowSource("input.webm").ConvertToRGB32
ColorKeyMask($000000, 90)

Attached: output.webm (720x720, 2.14M)

It's chroma keying her hair

You're LUCKY we got bored of that as quick as we did.

Now continue it as a chest burster...

this crashed my chromium os browser

I think I've got it now.

Attached: 1526813296689.webm (1280x720, 309K)