Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Seriously.js

seriouslyjs.org

Post reply on HN
Print view View original

161–170 of 196 posts

Re: Seriously.js

#161

Post by ilamparithi »

mindcrime wrote: post #70
danielweber wrote: post #41

"Sadly, we are unable to get Seriously.js to work on your computer. Sometimes WebGL gets a bit weird with certain graphics hardware and drivers. Please have a look here for more information."

"Sadly, we are unable to get Seriously.js to work on your computer. Sometimes WebGL gets a bit weird with certain graphics hardware and drivers. Please have a look here for more information." Yeah, same here, running Ubuntu on a Dell Precision laptop. Guess WebGL doesn't like my setup.

Same message here (Ubuntu, Dell, Chrome). But it worked on Firefox.

Re: Seriously.js

#162

Post by olalonde »

brianchirls wrote: post #129
olalonde wrote: post #113

I know next to nothing about graphics programming but how does this work? I don't suppose there is a Javascript loop that goes through all the pixels on each frame...

Nope. That would be too slow. I tried that a couple years ago before writing Seriously.js, and the big problem was copying around the memory. You have to first draw the video to a canvas, then you have to extract the pixel array from the canvas, loop through all the pixels and then draw the pixels back to the canvas. Now, for a high-definition video at 4 bytes per pixel (RGBA), you're looking at about 3.5MB of memory…

Sorry for the dumb question but how does the GPU execute Javascript? Or is it done in a declarative language specific to the GPU?

Re: Seriously.js

#164

Post by lucb1e »

mshron wrote: post #6

Finally a demo that doesn't make me think "Wow, the web has really caught up to the 1995 desktop!" Maybe if you're already an after-effects wiz this doesn't seem as magical, but it certainly felt like magic to me.

You sir are thinking exactly the same thing as I am.

Re: Seriously.js

#165

Post by slackito »

olalonde wrote: post #162
brianchirls wrote: post #129

Earlier quoted context omitted.

Nope. That would be too slow. I tried that a couple years ago before writing Seriously.js, and the big problem was copying around the memory. You have to first draw the video to a canvas, then you have to extract the pixel array from the canvas, loop through all the pixels and then draw the pixels back to the canvas. Now, for a high-definition video at 4 bytes per pixel (RGBA), you're looking at about 3.5MB of memory…

Sorry for the dumb question but how does the GPU execute Javascript? Or is it done in a declarative language specific to the GPU?

The GPU doesn't execute Javascript. It runs small programs called "shaders", written in GLSL (the OpenGL shading language), which are compiled on the fly by the graphics driver to something that can be actually executed on the GPU.

Re: Seriously.js

#166

Post by Intermernet »

wahsd wrote: post #159
garysweaver wrote: post #133

Earlier quoted context omitted.

The best part to me was that it was actually a pretty good music video, and the interactivity adds to it.

I thought it was just random goofing off for demo silliness. Was that a serious effort?

That was OK, Go (http://en.wikipedia.org/wiki/OK_Go) . The song is "WTF?"

They're famous for quirky video clips (original for this song is at http://youtu.be/12zJw9varYE). You should watch http://youtu.be/qybUFnY7Y8w . You'll like it. Trust me.

Re: Seriously.js

#167

Post by [deleted] »

wahsd wrote: post #159
garysweaver wrote: post #133

Earlier quoted context omitted.

The best part to me was that it was actually a pretty good music video, and the interactivity adds to it.

I thought it was just random goofing off for demo silliness. Was that a serious effort?

[deleted]

Re: Seriously.js

#168

Post by spyder »

tqs wrote: post #107

The technology used here to do the image processing is GLSL, in particular fragment shaders (aka pixel shaders). GLSL is a very small C-like language that's become a standard for GPUs. GLSL code gets sent (as a string) to the GPU by javascript via the WebGL API. Seriously is a JS library for handling the boilerplate of WebGL, composing and compositing multiple shaders in a pipeline/graph, and adjusting their paramete…

https://www.shadertoy.com/browse (WARNING: it can freeze your browser)

Re: Seriously.js

#169

Post by hexasquid »

brianchirls wrote: post #126
kmm wrote: post #87

Impressive! It's really amazing to see how OpenGL can enrich the web if it's used right. A few years ago I'd never have guessed shaders could be used in a browser. I have little experience with Javascript projects, so can I ask why the name Seriously? Wouldn't a more descriptive name cover the contents? Also, why is the main source file 4K lines long? That's a little off-putting.

Good questions. It's called Seriously for two reasons: 1) At some point, I had this idea that I would make all my Javascript libraries references to Homestar Runner. http://www.hrwiki.org/wiki/Seriously 2) "You can do that in a browser? Seriously?!" As for the file size, yeah you're right it's too big. I'm working on a grunt.js build script, and when that's done, I'll break the main file into smaller pieces so you ca…

I'm going to think of it whenever I see something like "You can't do anything serious with JavaScript"

Re: Seriously.js

#170

Post by brianchirls »

blindhippo wrote: post #154
brianchirls wrote: post #131

Earlier quoted context omitted.

Is there a console error?

"Uncaught Unknown source type seriously.js:2727" Soon as I turn Ghostery off it works fine. This is in Chrome 27.0.1453.110

Works fine for me with Ghostery. For some reason, it looks like videojs is falling back to EMBED tag for some people. Will investigate.
Post reply on HN