brianchirls
Joined 13 years ago
Karma
145
Submissions
15
Member since
Jun 5
http://github.com/brianchirls
http://seriouslyjs.org
View on Hacker NewsRecent submissions
Comment · 13 years ago
That's pretty weird. Is it possible you have a browser extension that's replacing the video tag with an EMBED?
Comment · 13 years ago
That's the nice thing about requestAnimationFrame. It's smart enough to not waste time updating if you're not looking at it.
As for 80%, umm... video driver issues? :-(
Comment · 13 years ago
"TV Glitch" is the Page Curl of the 2010's
Comment · 13 years ago
Works fine for me with Ghostery. For some reason, it looks like videojs is falling back to EMBED tag for some people. Will investigate.
Comment · 13 years ago
Is there a console error?
Comment · 13 years ago
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 for each copy. And on top of that, it has to allocate and garbage collect that 3.5M pixel array for every frame, because it doesn't let you copy into an existing array. If you look at the first video-processing canvas demos, they tend to be pretty small, and this is why.
Instead, this uses WebGL/OpenGL. So the pixels are copied once from the video directly into the GPU memory, and they are processed in parallel there before going straight to your screen. Much, MUCH faster.
Comment · 13 years ago
Yeah, I run Chrome on Ubuntu on a pretty powerful Lenovo T-something with an NVIDIA whatever optimus pain in the neck. The only way I can get it to work is to add --ignore-gpu-blacklist to the Chrome command line.
Check: /usr/share/applications/google-chrome.desktop (or something like that) You should see some lines that start with "Exec" where you can add that parameter to the end.
Comment · 13 years ago
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 can pick and choose which utilities and things you need to load. Right now, it has the color lookup table and noise shaders, among other things, which are not necessary for everybody.
Comment · 13 years ago
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.
Comment · 13 years ago
This is where I got the original, raw green screen video:
http://okgo.net/2010/01/20/wtf-video-remix-project/
I kinda wish it was at a higher bit-rate. There are some jaggies at the edges of the hair and stuff that I had to cover up by tinting the color of the video.
Comment · 13 years ago
Something similar to that is possible for video. For example:
http://www.youtube.com/watch?v=rGMqXBvYxog
I'm working on porting this over to Seriously.js so it should run in the GPU, hopefully pretty fast. The first crack at it was not so good, and now I'm experimenting with some new features that are only in Chrome nightly builds at the moment (and buggy at that). So look for this in the next 3-6 months.
Comment · 13 years ago
Hi, I'm the person responsible for/guilty of this. Thanks for the comments, everyone. My sympathies for the BSOD.
Please keep the bug reports and questions coming. I'll try to fix/answer what I can.
Comment · 13 years ago
This is "WTF" by OK Go. Back in 2010 they posted the raw greenscreen footage for people to remix.
Comment · 13 years ago
No, it is definitely not supposed to look like that. Here's what it looks like for me:
https://s3.amazonaws.com/uploads.hipchat.com/23744/150541/nk...
Do you mind sharing your video card info and operating system? It will be hard to debug remotely, but I'll see what I can dig up. Please post it here or on github: https://github.com/brianchirls/Seriously.js/issues
Thanks
Comment · 13 years ago
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