• Hey, guest user. Hope you're enjoying NeoGAF! Have you considered registering for an account? Come join us and add your take to the daily discourse.

webm |OT| Welcome to the world of superior gifs

Status
Not open for further replies.

-SD-

Banned
Meh at webm.

I'll take reduced amount of colors over even more compression artifacts added into the source video due to recompression when converting to webm. GIF still reigns supreme despite the huge file sizes and the 256-color palette.
 

gohepcat

Banned
Meh at webm.

I'll take reduced amount of colors over even more compression artifacts added into the source video due to recompression when converting to webm. GIF still reigns supreme despite the huge file sizes and the 256-color palette.

...really? It's so far superior in quality in every possible aspect. I just...Are you looking at the same thing I'm looking at?

It's so vastly improved...just...what are you looking at?
 

jediyoshi

Member
I'll take reduced amount of colors over even more compression artifacts added into the source video due to recompression when converting to webm. GIF still reigns supreme despite the huge file sizes and the 256-color palette.

I understand how you feel about my preference, but I just don't like more compression artifacts added on top of existing compression artifacts.

I'm not seeing the distinction here, what is it about GIFs you like? You realize webm files exist outside of ones converted from GIFs, right?
 

lednerg

Member
Webm is a good video codec, but it's too harsh on current CPUs to replace GIFs as they are used now. It's also lacking IE and Safari support (no surprise there), which is kind of a big deal.
 

TheDanger

Banned
I'm completely in love with webm. E3 is gonna be fucking amazing with this

Why is everyone looking forward to GAF on E3? It's not like we can use it during E3. Last year it was down for pretty much the entire day wasn't it?

Webm is a good video codec, but it's too harsh on current CPUs to replace GIFs as they are used now. It's also lacking IE and Safari support (no surprise there), which is kind of a big deal.

http://www.webmproject.org/ie/ not lacking at all

Turn auto play off and it works fine, even on my shitty work cpu.

Hopefully someone will release something for Safari. Maybe in Cydia for iOs.
 

-SD-

Banned
I'm not seeing the distinction here, what is it about GIFs you like?
Image quality has always been the most important thing for me. Making a GIF does not require the use of video codecs and re-encoding, like WebM does. Re-encoding adds compression artifacts. With GIFs, you can just extract an image sequence out of a video to BMPs and make a GIF out of that. So, with GIFs, there's no loss in quality other than the low amount of colors you can use.

While GIF is good, it surely is not what an animated image format can be, these days. What I want is an animated image format like GIF but with full color palette (and better transparency support). GIF is old and lacking in features for high-quality, so it needs to die already. Animated PNG's quality is the best out there but file sizes are enormous. WebP or animated JPG or a smarter APNG format seems to be the way to go?
 

lednerg

Member
http://www.webmproject.org/ie/ not lacking at all

Turn auto play off and it works fine, even on my shitty work cpu.

Hopefully someone will release something for Safari. maybe in Cydia for iOs.

Webm is a replacement for embedded flash and mp4 videos, not GIFs. It's a video codec after all, not an image format. That's why you need to turn off autoplay in this thread - otherwise, it's like playing several embedded YouTube videos at the same time.

For a similarly capable image format that doesn't tax the CPU so much, webp (from the webm people) is one possible alternative - although that has a while to go in terms of gaining support.
 
Tried encoding a webm with VP9 instead of VP8, does it work for anyone?
http://a.pomf.se/jqvguz.webm

Works fine for me in FF + greasemonkey script.
edit: but in general my FF sometimes crashes in this thread with the script enabled (no auto-play).

We can even directly embed *.mp4 with H.264/AAC codec, right?
Would embed VP9/H.264 profit from the hardware acceleration?

I noticed the H264 source videos are actually even a bit smaller than the VP8 webm (with sound).
 

TheDanger

Banned
Webm is a replacement for embedded flash and mp4 videos, not GIFs. It's a video codec after all, not an image format. That's why you need to turn off autoplay in this thread - otherwise, it's like playing several embedded YouTube videos at the same time.

For a similarly capable image format that doesn't tax the CPU so much, webp (from the webm people) is one possible alternative - although that has a while to go in terms of gaining support.

who the fuck cares if it's technically a video? It's looped, embedded and looks great. I don't care it's not a real replacement. It' just better.
 

strata8

Member
Image quality has always been the most important thing for me. Making a GIF does not require the use of video codecs and re-encoding, like WebM does. Re-encoding adds compression artifacts. With GIFs, you can just extract an image sequence out of a video to BMPs and make a GIF out of that. So, with GIFs, there's no loss in quality other than the low amount of colors you can use.

While GIF is good, it surely is not what an animated image format can be, these days. What I want is an animated image format like GIF but with full color palette (and better transparency support). GIF is old and lacking in features for high-quality, so it needs to die already. Animated PNG's quality is the best out there but file sizes are enormous. WebP or animated JPG or a smarter APNG format seems to be the way to go?

Lossless VP9 or H264 should be around the same size as a GIF. But completely lossless is a bit silly, because you can create a lossy video that's indistinguishable at 1/2 the size, and another that's almost indistinguishable at a 1/4 of the size. It's only once you start getting to 1/8-1/16 of the GIF size that artifacts start to become visible.

Works fine for me in FF + greasemonkey script.
edit: but in general my FF sometimes crashes in this thread with the script enabled (no auto-play).

We can even directly embed *.mp4 with H.264/AAC codec, right?
Would embed VP9/H.264 profit from the hardware acceleration?

I noticed the H264 source videos are actually even a bit smaller than the VP8 webm (with sound).

H264 is significantly more efficient than VP8. It's slightly better than VP9, even:
9F1ST1Z.png

nzMvLP0.png


H265 destroys both H264 and VP9 though :p

That's the whole problem with VP9. How could you possibly convince manufacturers to adopt it when it's inferior to the existing standard, and doesn't hold a candle to the next standard?

And because H264/H265 is an international, collaborative effort, it is literally Google vs. everyone else.
 

Trickster

Member
Why is everyone looking forward to GAF on E3? It's not like we can use it during E3. Last year it was down for pretty much the entire day wasn't it?


Well, E3 isn't 1 day, it's 3. And it was only really down/slow during the big press conferences.
 
Can anyone let me know if this is working?

https://dl.dropboxusercontent.com/u/56311839/Amazing Spider-Man.webm

I'm trying to use Dropbox, but for some reason it destroyed the quality of the clip I was using. It's in HD when I play the original webm file in VLC.

Dropbox download seems slow to me. It works though and its in (full) HD, but the bitrate is way too low, resulting in horrible quality. Better to reduce it to 960x540 (or lower) with a better bitrate. 1080p is really overkill for forums.
 
H265 destroys both H264 and VP9 though :p
IIRC this test used some wrong settings for VP9, all intra setting or something. Reading on Doom9, VP9s main efficieny disadvantage are less prediction angles (due to patents).

Edit: Found it:
http://forum.doom9.org/showthread.php?t=165839&page=21
VP9 vs HM vs x264 in playback/random-access config. TLDR: The paper found that VP9 needs 80% more bitrate than HEVC, 8% more than x264. Unfortunately, VP9 was ran with min-q=max-q=$QP. If that's what that sounds like, their results for VP9 are almost certainly invalid.
 

Phoenix

Member
H265 destroys both H264 and VP9 though :p

That's the whole problem with VP9. How could you possibly convince manufacturers to adopt it when it's inferior to the existing standard, and doesn't hold a candle to the next standard?

And because H264/H265 is an international, collaborative effort, it is literally Google vs. everyone else.

The issue is one of getting away from the patent/royalty encumbrance that comes with H.26x. As consumers its not a big deal for us, but for content creators/publishers/broadcasters it can be a huge thing for them.
 
The following will make a good reaction webm:
http://a.pomf.se/bcefvs.webm

Amazing. It's small clips like this that will benefit most. Youtube will have a lot to worry about if this becomes the norm:

Sound.

Cicumvent youtube ads.

No need to open new tabs.

Forumers will get their point across to ppl much more efficiently.

Higher "view rates" as ppl can access the point being made with less hassle.

60fps.

Custom video resolution.

Content more easily controllable from content providers (60fps viral trailers for example).

Downsides:

copyright holders might get seriously pissed and take "action". Dey be like. . .

ibuxhzyrgbnco51s3v.gif


60fps MP4 (H.264) with no sound. Anyone want to try it out on their tablets/phones? Chrome plays it in a new tab but IE tries to open Windows Media Player.

http://a.pomf.se/nyxkxe.mp4

Created this with VidCoder. Really easy to use.

Amazing. dat 60fps. So much better than an enormous gif equivalent.
 

strata8

Member
IIRC this test used some wrong settings for VP9, all intra setting or something. Reading on Doom9, VP9s main efficieny disadvantage are less prediction angles (due to patents).

Edit: Found it:
http://forum.doom9.org/showthread.php?t=165839&page=21

In that case, I guess we'll have to see. If VP9 can get fairly close to H265 it'd be neat to see it widespread.

The issue is one of getting away from the patent/royalty encumbrance that comes with H.26x. As consumers its not a big deal for us, but for content creators/publishers/broadcasters it can be a huge thing for them.

Not as much as you'd think. For H.265 at least it's something like 20c per device sold capable of encoding/decoding H.265. There are no fees for content, broadcasting, etc.
 

strata8

Member
Made a couple of bookmarklets that will convert all the .MP4 links on the page into videos.

Autoplay and no controls:

javascript:(function() {var links = document.getElementsByTagName("a"); for (var i = 0; i < links.length; ++i) { var item = links; var extension = ""; var a = item.href.split(".");if( a.length === 1 || ( a[0] === "" && a.length === 2 ) ) {extension = "";}else { extension = a.pop(); }if (extension=="mp4") {var video = document.createElement("video");video.src = item.href;video.muted = true;video.loop = true;video.autoplay = true;video.preload = "metadata";video.controls = false;item.parentNode.replaceChild(video, item);}}})();

No autoplay and with controls:

javascript:(function() {var links = document.getElementsByTagName("a"); for (var i = 0; i < links.length; ++i) { var item = links; var extension = ""; var a = item.href.split(".");if( a.length === 1 || ( a[0] === "" && a.length === 2 ) ) {extension = "";}else { extension = a.pop(); }if (extension=="mp4") {var video = document.createElement("video");video.src = item.href;video.muted = true;video.loop = true;video.autoplay = false;video.preload = "metadata";video.controls = true;item.parentNode.replaceChild(video, item);}}})();

Both loop and mute the audio by default.

edit: Working fine on the Surface, Chrome, and desktop IE. Also works on iPhone 5 but doesn't AutoPlay obviously.

edit2: Stress test:

http://a.pomf.se/nyxkxe.mp4

http://a.pomf.se/lootci.mp4

http://zippy.gfycat.com/VictoriousSimilarCanadagoose.mp4

http://fat.gfycat.com/DecisiveSleepyCoral.mp4

http://zippy.gfycat.com/FlusteredSoulfulBee.mp4

http://fat.gfycat.com/RelievedAcademicBasil.mp4
 

jediyoshi

Member
Image quality has always been the most important thing for me. Making a GIF does not require the use of video codecs and re-encoding, like WebM does. Re-encoding adds compression artifacts. With GIFs, you can just extract an image sequence out of a video to BMPs and make a GIF out of that. So, with GIFs, there's no loss in quality other than the low amount of colors you can use.

Can you define exactly what "compression" means to you? I'm not reading anything other than an arbitrary, semantic distinction that doesn't logically follow. If you're taking any 'thing' as a source and ultimately end up with a GIF, a single frame is an objectively worse IQ than if it were done in webm, save for a situation in which maybe that frame already only had 256 colours.
 
Status
Not open for further replies.
Top Bottom