Topic: My webm uploads are borked

Posted under General

My webm files keep getting deleted due to them apparently being broken for some people. They work on-site from my perspective after being uploaded but for most others they're corrupt. It seems random. What am I doing wrong? I've tried different setting combinations but the result is usually the same. I have one successful webm upload which used the same program and settings which makes it extra confusing.

Also, when I press upload the preview displays a broken image icon.
Also, also, if I render a gif instead of webm it uploads fine.

Images of my adobe premier webm settings: https://imgur.com/a/69R3het

If you think its an adobe issue, what program do the rest of yall use for turning sets of images into a webby?

Updated

bipface said:
well it looks like mairo already mentioned that your bitrate is way too high
regardless of whether they're playable or not, i doubt anyone will be happy downloading 90MB for 10 seconds of footage

otherwise post #2184974 seems okay, and i can't comment on post #2234152 or post #2210803 since i have no way of accessing them
but Mairo appears to have cited the yuv444p pixel format as the issue, so i'd suggest sticking to yuv420p

Interesting, thanks. It's probably because I'm using constant quality. I'll try CRF.

Edit: nevermind. I figured out how to view my deleted posts so I could see the helpful comments. I'm useless. :p

https://trac.ffmpeg.org/wiki/Encode/VP9#compatibility
e621:supported_filetypes: Should be YUV420

We are not video hosting site, so we rely on uploads being proper as is instead of encoding everything consistantly. Additionally we aren't a filehost, so we would also want the uploads to be viewable as wide audience as possible without issue (excluding apple devices, because they do not want to support webm so that they can use their userbase as means to force their MP4 codecs and licensing, but that's another rant).
As you can see in the comments section, people are having issues playing the file or getting problems like full on green screens and such. Additionally these cases have tendency to snowball fast and everyone starting pointing fingers in wrong directions.

Software and hardware can have differend level of support or work with material in differend manner. Just because something works on your machine and software, doesn't mean there isn't something wrong, just that your configuration is differend enough to not trigger things. Playing PC games over the years makes this extremely painfully obvious, when stuff like having dualshock 4 controller connected into a USB port will make the games camera to rotate fast for no apparent reason.
In this case, majority of browsers and players will assume yuv420 colorspace to be used with the video file to be played back, pretty much all videos online will use this format from youtube to pornhub. However where VP8 was limited for this, VP9 does allow usage of higher colorspaces, which does increase color accuracy and quality, but at the same time will make tons of browsers and players just stop working completely. This is because VP9 has become extremely widely used format, even new games like Assassins creed Odyssey or Half life Alyx have in game cutscenes and enviromental videos in WebM VP9 format, because it is open standard, so the possibility for more features is necessary, but simply doesn't work everywhere.

e621 upload form will show a broken thumbnail, that is fine, currently it only works with image formats, even on old site it would just show a "VIDEO" on white box.

I've lowered the quality of my webm uploads as suggested, but they're still getting flagged as broken. Can anyone advise me to what I'm still doing wrong? I'm trying to learn but since everything works on my end it's hard to test things out. Sorry for all the hassle. Is it because I use VP9 instead of VP8?

Latest anim here: https://e621.net/posts/2263082

severalbaps said:
I've lowered the quality of my webm uploads as suggested, but they're still getting flagged as broken. Can anyone advise me to what I'm still doing wrong? I'm trying to learn but since everything works on my end it's hard to test things out. Sorry for all the hassle. Is it because I use VP9 instead of VP8?

Latest anim here: https://e621.net/posts/2263082

You are using yuv420p12le which is 10-bit colorspace instead of yuv420p or yuva420p.
You are using Profile 2 which means the video is 10-12-bit instead of regular 8-bit. Use Profile 0 and 8-bit (especially as huge majority of people only have 8-bit monitors or TVs).

So the issue is still the exactly the same that I mentioned in previous message: "e621:supported_filetypes: Should be YUV420"

Like mentioned in previous message, VP9 has more versatile use, so that's why it supports more features like higher color profiles and chroma subsampling. For compatibility and filesize reasons (because we have pretty strict filesize limits and most users will stream the video instead of downloading it) you should stick to YUV420P and 8-bit video files.
Most people having issues with your files are using software which assumes the videos are standard and plays them as such, which can result into black screens, stretched videos, rainbow colored messes, etc. Technically the file is fine, but anyone using anything else than newest chrome or chromium based browser on desktop will be complaining and considering how huge amount of people do browser with their phone that doesn't sound good.
Technically you can make YUV444P 10-bit video file and the quality will be so much higher for those who can view it (because color data will be pixel perfect and all pixels have 1024 scale instead of 256 scale), but for everyones mental health link it externally.

VP8 is allowed, but it is older format, so you do need to dial up the bitrate a bit to get same quality that VP9 provides. However it is also brute force solution to the problem because VP8 only supports YUV420P and 8-bit and nothing above that, so even if you tried to fuck up the file you cannot (unless you use resolution that cannot be divided by factor of 2, but most software should warn or prevent that).

Updated