Support NeoGAF

[Canis lupus]

So does it work on firefox? Some links work and others dont.

 

[b&jy77VjiKn$#F]

http://a.pomf.se/nsznyr.webm
First test. Too bad my laptop can't play bluray, I have to use the DVD version instead. Still trying to mess around with ffmpeg, so that I can find a setting that suits my liking when it comes to file size and overall quality. But as of now, this will do.

Compare to the same sequence made in gif: this one is 854x360 and around 2.5Mb vs 480x200 and more than 9Mb. Yet one's quality is almost the same, while the other's is really hideous (in order to reduce the file size to less then 10Mb). Damn.

From the OT.

 

[KaiserBecks]

So does it work on firefox? Some links work and others dont.

Some links are probably offline (threads on 4chan usually don't last long), so I guess that's why they only show as a black screen.

 

[SJRB]

Try turning off autoplay... in fact I think that option should be off by default

God bless you.

So is this a coding thing that can be ironed out eventually or are these webm's inherently heavy on the cpu?

 

[Magwik]

Had to disable the extension as well for the sake of my processor.

 

[ragon]

NeoGAF really needs to adopt WebM/HTML5. It's something I've been pondering recently.

gyfcat.com does a great job of converting gifs to HTML5 videos with no audio.

Look at this GIF:

GIF Version: 4.5 MB
HTML 5 Version: 286 KB

View HTML5 version here: http://gfycat.com/about

GIFs are resource heavy and outdated.

Tried this website after i failed to use webm converter

http://gfycat.com/QuarrelsomePreciousIlsamochadegu

 

[close to the edge]

God bless you.

So is this a coding thing that can be ironed out eventually or are these webm's inherently heavy on the cpu?

If I had to guess, it's both. WebM is a new format, so it's possible that decoders aren't yet as efficient as they could be. On the other hand, because WebM has much, much better compression, it's probably also more taxing on the CPU. Like everything, it's a tradeoff. You get images that are much smaller and look way better but you need some more CPU muscle to decode it.

 

[SquiddyCracker]

Yeah, this won't replace gif anytime soon.
It's way too CPU intensive, and will seriously harm your computer if you start wholesale using webm instead of GIF.

 

[Hazaro]

Thanks for the addon, turned off autoplay and enabled sound be default.

8D

 

[Portugeezer]

Are images meant to show up as links or embedded into posts like gifs?

So far every webm is just a link, not on the neogaf page.

NeoGAF really needs to adopt WebM/HTML5. It's something I've been pondering recently.

gyfcat.com does a great job of converting gifs to HTML5 videos with no audio.

Look at this GIF:

http://giant.gfycat.com/AlertSpicyBlueandgoldmackaw.gif[IMG]

GIF Version: 4.5 MB
HTML 5 Version: 286 KB

View HTML5 version here: [url]http://gfycat.com/about[/url]

GIFs are resource heavy and outdated.[/QUOTE]

Gifs simply weren't made to be used the way people use them today.

 

[giancarlo123x]

Beyonetta 60 fps webm: http://i.4cdn.org/wsg/src/1396794276453.webm

My eyes. Amazing.

 

[strata8]

If I had to guess, it's both. WebM is a new format, so it's possible that decoders aren't yet as efficient as they could be. On the other hand, because WebM has much, much better compression, it's probably also more taxing on the CPU. Like everything, it's a tradeoff. You get images that are much smaller and look way better but you need some more CPU muscle to decode it.

The real reason is that no GPUs support hardware decoding of VP8 (WebM's codec), unlike H264 which has widespread support. CPUs are shitty at decoding video and for that reason WebM's never going to be viable as a GIF replacement, especially for mobile devices.

In contrast I'm able to have 10 gfys open at the same time on the Surface 2 and IE's CPU usage sits at 15%.

 

[Portugeezer]

Adding to this list.

http://a.pomf.se/aamkor.webm (this one has sound)

Hmmm... they don't play as 60fps in my firefox. I downloaded it and it's 60fps when using MPC

 

[ElbowRocket]

You can also upload WebM to Gfycat, just FYI.

Here's some Titanfall.

EDIT: Seems to have resized mine, though. Weird.

Here's the full size version I uploaded to /v/.

Is the game suppose to be fast forwarded and so smooth?? cant be

 

[OTIX]

The real reason is that no GPUs support hardware decoding of VP8 (WebM's codec), unlike H264 which has widespread support. CPUs are shitty at decoding video and for that reason WebM's never going to be viable as a GIF replacement, especially for mobile devices.

In contrast I'm able to have 10 gfys open at the same time on the Surface 2 and IE's CPU usage sits at 15%.

So why aren't we embedding h264 instead?

 

[GoldenEye 007]

Yeah, this won't replace gif anytime soon.
It's way too CPU intensive, and will seriously harm your computer if you start wholesale using webm instead of GIF.

What?

Aren't processors made to... process information? How will this harm your computer?

 

[level44]

Doesn't work for safari.

 

[plank]

If I had to guess, it's both. WebM is a new format, so it's possible that decoders aren't yet as efficient as they could be. On the other hand, because WebM has much, much better compression, it's probably also more taxing on the CPU. Like everything, it's a tradeoff. You get images that are much smaller and look way better but you need some more CPU muscle to decode it.

What about a website like 4chan which now supports it? It would certainly help if GAF does this as well. Though it still buzzes you cpu if you open a lot at once.

 

[hodgy100]

Is the game suppose to be fast forwarded and so smooth?? cant be

first time seeing 60fps?

 

[OminoMichelin]

What?

Aren't processors made to... process information? How will this harm your computer?

Some kinds of information is different from other kinds of information, and if you keep you cpu usage above 90% all the time it will seriously shorten its lifespan.

 

[hodgy100]

Yeah, this won't replace gif anytime soon.
It's way too CPU intensive, and will seriously harm your computer if you start wholesale using webm instead of GIF.

are you joking?

your processor is just doing what it's intended to for once, seems its spent a long time being underutilised

This will not harm your pc, ever.

 

[NekoFever]

So why aren't we embedding h264 instead?

Politics. It's not an open format so some of the open-source browsers can't or won't add native support.

 

[arit]

One might argue that a

preload = "metadata"
preload = "auto"

toggle would be nice to save bandwidth, though I do not know how it affects autoplay on metadata.

 

[maniac-kun]

Yeah, this won't replace gif anytime soon.
It's way too CPU intensive, and will seriously harm your computer if you start wholesale using webm instead of GIF.

Stop spreading false information.

 

[M3d10n]

So then aside from limited compatibility since its a relatively new standard what are the drawbacks of webm?

Practically zero hardware acceleration. A single HD webm already pushes an i5 2500k to ~10% CPU usage. I fear what would happen on a page full of auto-playing webm videos.

Webm, like h264, is a video codec. The browsers aren't designed to have several dozens of them playing at the same time on a single page.

Is there any browser for iOS that supports webm?

All iOS browsers are actually Safari re-skins.

Plays on iPad via VLC app. Hope native Safari support comes.

Forget about it. Apple already chose h264 for HTML5 video. Plus, without hardware decoding it would completely murder the battery life and probably be unplayable on older/slower devices.

If I had to guess, it's both. WebM is a new format, so it's possible that decoders aren't yet as efficient as they could be. On the other hand, because WebM has much, much better compression, it's probably also more taxing on the CPU. Like everything, it's a tradeoff. You get images that are much smaller and look way better but you need some more CPU muscle to decode it.

WebM is just a container. The codec, VP8, is 6 years old and was the last version of the TrueMotion codec lineage by On2 Technologies before they were purchased by Google, who open-sourced the codec.

The problem is the lack of hardware decoding. Decoding modern video is very taxing, but we hardly notice it because nearly everything uses h264, which has ubiquitous hardware acceleration support. Disable hardware acceleration and h264 becomes as CPU-intensive as WebM, if not more.

VP8 completely failed on getting hardware support from hardware vendors. On PC, only some Intel GPUs actually offer hardware support while on mobile only a few Android devices do it.

It seems Google is working hard to fix this with VP9, which is the rival to h265 in becoming the "4k generation" codec. However, this means we'll probably need new hardware to play accelerated VP9 (NVidia and AMD GPUs might get shader/compute-based decoding via drivers, but mobile devices and intel IGPs need new revisions.)

So why aren't we embedding h264 instead?

No fucking idea! All fucking browsers support h264 now, including Firefox since Mozilla gave up and ended up licensing it anyway.

 

[bbyybb]

Thanks for the addon, turned off autoplay and enabled sound be default.

My CPU goes from 6% to 12/13% when playing the videos, so it isn't that big of a spike for me.

 

[Chainsawkitten]

So is it pronounced jebm?

 

[M3d10n]

Politics. It's not an open format so some of the open-source browsers can't or won't add native support.

The only open source browser that didn't support h264 was Firefox. They gave in in version 8 versions ago.

All browsers, except Opera, support h264.

 

[Orayn]

The only open source browser that didn't support h264 was Firefox. They gave in in version 8 versions ago.

All browsers, except Opera, support h264.

Well, Google said they plan to cut support for it on Chrome, didn't they? They haven't yet, but just making the threat was probably pretty influential.

Is the game suppose to be fast forwarded and so smooth?? cant be

Nope, that's just what 60 FPS looks like.

As others have said, this is going to make framerate comparison threads very fun in the future.

 

[ElbowRocket]

first time seeing 60fps?

Well, Google said they plan to cut support for it on Chrome, didn't they? They haven't yet, but just making the threat was probably pretty influential.

Nope, that's just what 60 FPS looks like.

As others have said, this is going to make framerate comparison threads very fun in the future.

Guess I just got to use to console vids

 

[Chuckpebble]

So is it pronounced jebm?

hWebm

 

[SimleuqiR]

WebM for NeoGAF (Chrome) 1.3

- Added "hover-to-play" option.
- Added max-height option.
- Added Credits page in Options.

Niiiiicee. Thank you.

 

[TheSeks]

all the webMs there seem to open up in their own tab though

...That's... by design...?

Like... most webpages...?

Loading them all at once is CPU intensive, as this thread shows depending on the computer. Same for thousands of .gifs across one page. Letting people pick and choose which images they want to view is the intention of 4chan along with the discussions there, for better or worse.

Andy: One issue with the extension update is that click to play breaks the WebM controls in Chrome. Play doesn't have a play hover button like Youtube does in pausing. And if you click that, it won't run. So you have to click the invisible play button. Vice-versa for pausing. If you want to pause, you have to click the pause button on the tool-bar.

And still no option to remove looping as a global option. >:|

 

[Lombaszko]

It seems Google is working hard to fix this with VP9, which is the rival to h265 in becoming the "4k generation" codec. However, this means we'll probably need new hardware to play accelerated VP9 (NVidia and AMD GPUs might get shader/compute-based decoding via drivers, but mobile devices and intel IGPs need new revisions.)

Interesting. ffmpeg supports VP9, but I can't seem to get it working correctly. Searching other forums, it's not optimized for hyper-threading yet and is probably encoding slow for people who can get it working.

I've been doing tests for my company's streaming video we put online and h264 stuff seems to encode a lot faster than VP8 WebM, but the smaller file size of WebM is tempting.

 

[AuthenticM]

So that thing is really a video file, huh ? When it stops playing, instead of looping it stops and I have to hit the "play" button again.

That's so dumb. I'm all for better quality "gifs" but I'm disappointed in .webm.

 

[b&jy77VjiKn$#F]

So that thing is really a video file, huh ? When it stops playing, instead of looping it stops and I have to hit the "play" button again.

That's so dumb. I'm all for better quality "gifs" but I'm disappointed in .webm.

Right click ---> loop. Can be set to default.
http://a.pomf.se/knivwk.webm

 

[AuthenticM]

Right click ---> loop. Can be set to default.
http://a.pomf.se/knivwk.webm

Ok, but can these things even be embedded in a web page ? So far I've only seen links to these files.

 

[b&jy77VjiKn$#F]

Ok, but can these things even be embedded in a web page ? So far I've only seen links to these files.

WebM for NeoGAF (Chrome) 1.3

- Added "hover-to-play" option.
- Added max-height option.
- Added Credits page in Options.

Some people made some extensions for Firefox as well.

 

[Chainsawkitten]

Ok, but can these things even be embedded in a web page ? So far I've only seen links to these files.

Yes, embedding them in HTML is quite simple. Whether you can embed them on a forum/social media depends on whether that particular site supports them (or alternatively if you use a greasemonkey script or similar).

 

[AuthenticM]

Some people made some extensions for Firefox as well.

Good, but for this file to overcome .gif as the standard, it shouldn't require procedure to make it work. Every browser should support the format and make it work exactly like .gifs, or else people are going to stick with the most painfree format.

 

[Jal]

So will youtube change to this format and have instant loading videos in the future?

 

[Dennis]

Good, but for this file to overcome .gif as the standard, it shouldn't require procedure to make it work. Every browser should support the format and make it work exactly like .gifs, or else people are going to stick with the most painfree format.

It took 3 seconds of my life to install the app that embeds the webms..........

 

[Orayn]

Good, but for this file to overcome .gif as the standard, it shouldn't require procedure to make it work. Every browser should support the format and make it work exactly like .gifs, or else people are going to stick with the most painfree format.

Embedding them is painless and doesn't actually require an extension, it's just necessary right now because GAF just doesn't have a [webm] [/webm] tag yet.

So will youtube change to this format and have instant loading videos in the future?

Most of these load quickly because they're relatively small files that aren't being hosted on places that aren't congested and/or throttled like YouTube is. WebM is great, but it's not that dramatically better than other types of web video.

 

[b&jy77VjiKn$#F]

Good, but for this file to overcome .gif as the standard, it shouldn't require procedure to make it work. Every browser should support the format and make it work exactly like .gifs, or else people are going to stick with the most painfree format.

Well, it's a start.

The forum can be made to automatically embed these videos as well, if the administration want to.

 

[TheSeks]

Good, but for this file to overcome .gif as the standard, it shouldn't require procedure to make it work. Every browser should support the format and make it work exactly like .gifs, or else people are going to stick with the most painfree format.

It's a VIDEO. Why the hell would browsers make it work as a .gif just because you/people want to use it as a .gif/IMAGE format?

Browsers already support it if you have the codec. They even embed if the site supports embeding. Not our fault GAF doesn't.

 

[b&jy77VjiKn$#F]

Browsers already support it if you have the codec. They even embed if the site supports embeding. Not our fault GAF doesn't.

Pretty sure that WebM is supported natively in almost every browser, except for like iOS browsers.

 

[Coreda]

Good, but for this file to overcome .gif as the standard, it shouldn't require procedure to make it work. Every browser should support the format and make it work exactly like .gifs, or else people are going to stick with the most painfree format.

Already been said, but every browser does support it as far as I'm aware. However NeoGAF is run on forum software that limits what web features can be used here, such as basic HTML like font size that is excluded in GAF's BBCode implementation. The userscripts and extensions created in these threads basically allow us to see what the browser can already render, but which otherwise GAF itself doesn't currently support.

 

[Kreed]

It's a VIDEO. Why the hell would browsers make it work as a .gif just because you/people want to use it as a .gif/IMAGE format?

Browsers already support it if you have the codec. They even embed if the site supports embeding. Not our fault GAF doesn't.

Exactly. Google already has an image format known as webp, which supports animation:

Why not WebP? Works better for images and goes in the <IMG> tag.

Like so:

http://littlesvr.ca/apng/images/GenevaDrive.webp

http://littlesvr.ca/apng/images/Contact.webp

Google never intended for webm to be an answer to gifs, 4chan/people have just gotten creative.

 

[AuthenticM]

It took 3 seconds of my life to install the app that embeds the webms..........

You are not the average facebook, twitter and tumblr user.

 

[Dennis]

Here, this is what high-quality webm looks like

http://a.pomf.se/tgjdve.webm