Doesn't work with Ghostery enabled. Don't see why it shouldn't work with twitter/google analytics blocked...
Is there a console error?
Seriously.js
131–140 of 196 posts
Re: Seriously.js
#132Earlier quoted context omitted.
"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.
I coded WebGL a little over a year ago on a Precision "laptop" under Suse Linux. What I needed: (A) up-to-date Nvidia proprietary drivers (B) "de-blacklist myself" somewhere deep in the browser's hidden WebGL config page (I think it was about:gpu or some such back then in Chromium, but I'm not really up to date).
chrome://flags
override software rendering list
Re: Seriously.js
#133Finally 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
#134Earlier quoted context omitted.
Does it now or might it soon work with live video from the local camera?
Yup. You can see a live video demo with a sample of some of the effects: http://brianchirls.github.io/Seriously.js/ Although, both Firefox and Chrome have been a bit buggy for me with getUserMedia. Try the Ascii Text effect.
Cool, thanks!
Couldn't get it to work in FF (Mac/22.0) - it asked for camera permission, camera activity light went on, but no images and constant re-prompts for permission. But, worked quite well in Chrome (Mac/27.0.1453.93).
Re: Seriously.js
#135Doesn't work at all for me in Firefox 21.0 on amd64 Linux. Works in Chromium 25 on the same box. This is particularly disappointing because there's a Mozilla logo on the page.
It works fine in FF 24 on a mac.
That makes me happy; it means it'll probably work on my box too if I upgrade Firefox. (I'm using Ubuntu 12.04's default apt repository.)
Re: Seriously.js
#136Finally 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.
"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."
And unfortunately the dynamically-compressed-to-shit song wasn't enough to provide entertainment on its own.
Re: Seriously.js
#137Didn't really know what was I was looking at. Clicked a button. wtf-in-js-mind-blown
Great job!
Re: Seriously.js
#138Crashes my browser in seconds. Nice exploit.
Re: Seriously.js
#139Earlier 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.
[deleted]
Re: Seriously.js
#140Earlier quoted context omitted.
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.
[deleted]
Well no, because each frame builds on all the frames before it. Either way, seeking is still broken unless you run through all the frames up to that point.