You know it's Serious when "TV Glitch" is available as a feature.
Seriously.js
171–180 of 196 posts
Re: Seriously.js
#172Finally 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.
I've clocked many hours into After Effects, but seeing this in a browser and _interactive_ is amazing. Never would I have thought that JS and browsers would progress so much in such a short period of time.
Re: Seriously.js
#173CentOS 5.9 / Firefox 17.0.6
Re: Seriously.js
#174Earlier quoted context omitted.
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.
Incidentally, you really aught to see how they make music with a car... http://www.youtube.com/watch?v=MejbOFk7H6c
Re: Seriously.js
#175I 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…
Re: Seriously.js
#176I 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…
Re: Seriously.js
#177Seriously did nothing for me. Uncaught Not a valid HTML element: EMBED (must be img, video or canvas)
It sounds like you may have a browser addon that's creating an EMBED element as a fallback because the browser can't play the video itself. If that's not the case, do you mind writing a bug issue on github with your browser details? https://github.com/brianchirls/Seriously.js/issues Thanks
Re: Seriously.js
#178Finally 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.
The best part to me was that it was actually a pretty good music video, and the interactivity adds to it.
It was filmed on a green screen for a different effect: Frame layering.
Re: Seriously.js
#179Re: Seriously.js
#180Earlier quoted context omitted.
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"