Earlier quoted context omitted.
Yes, you do need to process from beginning to end. If you look at the original video, you see that each frame builds on the one before it, which builds on the one before that. Remember, the buffer is never cleared -- it's just overwritten with a few new pixels (the dude moving) each room.
[deleted]
Seriously.js
151–160 of 196 posts
Re: Seriously.js
#152Re: Seriously.js
#153Re: Seriously.js
#154Re: Seriously.js
#155Re: Seriously.js
#156Earlier quoted context omitted.
Apparently with my Retina MacBook Pro with 10.8.4 and Safari 6.0.5, I "need to upgrade my video drivers", according to the site...
Sadly, Safari still doesn't support WebGL by default, although you can enable the Develop menu in the prefs, and then enable it in the Develop menu.
Re: Seriously.js
#157Earlier quoted context omitted.
Isn't the algorithm just, filter out the greenscreen, for each remaining pixel draw it to the buffer, draw the buffer to the screen? That doesn't seem more complicated than the examples they showed.
It is actually slightly more complicated. The existing effects work in GLSL and are just transforming single frames of video. For that effect to work, you need the previous buffer states; this means that seeking will cause the image to be different, and you need to feed the previous render state back as a texture.
Re: Seriously.js
#158Finally 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.
Re: Seriously.js
#159Finally 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.
Re: Seriously.js
#160cool that somebody now packs a similar idea into a lib, will definitely check it out.