Via Aaron Meyers, who’s getting ready for some fun projects at Eyebeam here in New York this week, anyone using a camera for capture, live video, or tracking needs to check out this copious thread on the OpenFrameworks forum:
We already knew Sony’s US$40 PS3 Eye camera was a wonder; that’s why we strongly recommended its use in the tangible interface hackday hosted earlier this month. But while we’ve heard some good luck squeezing performance out of the thing on Windows and Linux, the Mac - while reliable - could use more options and performance. Theo Watson, one of the OpenFrameworks team, comes to the rescue with a patched version of the macam open source video driver - halfway down the page. (I hope his changes get rolled into macam?)
You’ll find lots of other tips, not only for the Mac but other stuff, as well.
We’ll keep collecting tips on this camera. Macam experiences, anyone? I’m still trying to successfully build the Linux driver; once I sort that out, I’ll share.
Version 2.5 is coming of the open source 3D suite that’s also a nodal compositing engine and a video editor and a real-time game engine — basically, a visual operating system in which you can make just about anything. 3D software in general hasn’t been gifted with especially slick interfaces. But 2.5 changes that: check out the elegant pop-up menus and Spotlight-style menu searching. Every little detail can be Python scripted, which sounds geeky but could be an easy way to just tell the software what it is you want to do - and Python is a lovely language to dip your toes into as a beginning coder, too.
All that’s well and good. But the real highlight of the video above is the fact that working in Blender now happens much more in real-time. For those of us used to working with visuals in performance, this means our “studio” workflow can be dynamic and live, too. Whether you render and remix video later, export 3D objects, or move to the Blender Game Engine to take your Blender work onstage, that is likely to appeal to visualists.
At the moment (<2.5), Blender follows the “do everything in one window” paradigm.
As jeff clermont stated above: Blender 2.5 will be the first blender release which will allow multiple windows. Hopefully, one can show the output of the game engine on one monitor in full screen while manipulating it on the other screen. The new event system in 2.5 might allow some nice possibilities for visualists. Pablo Vazquez has done a nice of manipulating a running animation (in the 3d view), which isn’t possible in Blender <2.5.
Stay tuned. We’ll see if multi-screen output becomes practical.
Blender, the free and open source 3D modeling tool that’s also a real-time game engine, promises real-time visual performance possibilities, and is even a video editing tool, continues its march toward the long-promised, insanely powerful 2.5 milestone. (”Point five” doesn’t really begin to cover it.)
2.49 is now stable. And boy does it have a heck of a lot going on. There’s nodal texture editing, multiple streams of video playback in the Game Engine (making this especially appealing to visualists), 3D painting, real-time dome rendering in case you’ve got a planetarium gig, faster Game Engine performance, Bullet physics improvements for lots of physics-y goodness, real-time shape modification, and better game logic and Python control and included Python script extensions. And that’s just the start.
Basically, Blender has become a full-blown, real-time OpenGL video and graphics powerhouse inside an existing modeling tool. I’m still intrigued by dedicated game engines, but this means your modeling workflow and real-time workflow are one and the same.
And it’s capable, as a result, of some stunning visuals. The video above is from Martin Supitis, who describes it thusly on YouTube:
Few weeks of exploring the magic world of GLSL coding and few days of getting it all in this demo. Here is the result.
The thread in BlenderArtists forums that also contains download links and updates - here: blenderartists.org/forum/showthread.php? t=152343
Made for company Twilight 22 where i take part of creating adventure action game Fire Wire District 22 as concept artist, modeler, now also learning graphic coding.
here is seen final composite of GLSL scene + SSAO, Depth of Field, Light Scattering and Chromatic Aberration filters, captured 30fps in 1680X1050 resolution; 8xAnisotropic filtering and 16xQ Antialiasing.
For live visuals, of course, modeling tools do way more than we might actually want or need. But if you can dive into Blender and find a way to simplify the work to the point you might like for a visual performance, I think it could be an immensely powerful tool.
And then there’s hardware control. Marco Rapino aka Akta has been controlling Blender with the accelerometer in his Nokia N95 phone, as in the video seen here. (Oh yes, I do need to port this to Android, especially as I already have the sensors working.)
Of course, I’d like to see standardized OpenSoundControl for this sort of application. (Accordingly, OSC may soon lose the “Sound” officially in its title, given its more generalized purpose. Open Systems Control, perhaps? Open Stuff Control? Open Smurf Control?)
There’s been at least one paper on the topic of combining Blender with Pd for sound (”Blendnik”): http://porcaro.org/blendnik.html
I’m not sure of the preferred way to implement OSC inside Python inside Blender, but I’ll have to give this a try myself.
A huge thanks to Giorgio Martini aka Tweaking Knobs for these links. Giorgio is working on his own live project. Here’s a glimpse of what that looks like, in progress:
Deride the mouse as you will. When it comes to two-dimensional control, the device is pretty amazing. It’s a reasonable way of amplifying small hand gestures into bigger gestures on a 2D plane. But what about 3D interfaces? Suddenly, the mouse becomes like playing charades, telling someone else what to do in a universe with an extra dimension.
What you need is interfaces that make sense in 3D. Some of these interfaces are out there; the missing link has been intelligent connections to software. To see how powerful this can be, look no further than Camera GripTools, a motion capture system for Maxon’s Cinema 4D modeling tool.
It works with a variety of devices:
Behringer BCF2000 MIDI fader panel (already a popular controller among VJs/visualists)
Nintendo’s Wiimote
Joysticks
Track IR 4 Pro is a head-mounted tracker for head movements. Pricing starts at just US$120, so this is absolutely a solution for mortals, and it appears to work really well – with 120 FPS tracking.
Polhemus Patriot VR Tracker – I’d never seen this before, and it looks utterly brilliant. It’s a six degrees of freedom tracker / 3D digitizer, made up of a small sensor. And it’s only £ 1,985 … oh. Okay, never mind.
For Cinema 4D users, this looks absolutely invaluable. It supports XPresso, CInema 4D’s fantastic modular, visual programming environment, with drag-and-drop support for objects. The free demo version is already pretty usable, with more powerful versions running EUR99-499 (though sadly you need the EUR499 version for full hardware support).
But I think the bigger message is how controllable this makes the 3D environment. This could be fantastic in an open source environment like Blender, or for live control in Blender, visual tools like VDMX, and custom creations in vvvv, Jitter, Processing, and the like. And while it may not be possible to make a system as accurate as the Patriot, looking at what they’re doing I suspect it should be possible to do a “ghetto” version on the cheap. (You know I’m all about that.)
It’s been a long time since I touched Livid’s VJ software. But when it comes to hardware, they’ve been doing unbelievable work that could have Resolume and VDMX and Processing and vvvv and Max users turning their heads.
The Ohm64 looks simply fantastic. It’s got an ideal configuration for a lot of live visual applications, with 8×8 triggers and plenty of faders and knobs to go along with them. It’s also finally a controller that’s well-made but doesn’t cost a fortune – you get a well-crafted device made by the people who designed it in Texas, but at $599, it’s still affordable.
Visualists are doing all kinds of new things to expand their performance, so I believe having a truly open controller is essential. The Ohm64 delivers, with a chip and editor software that have extensive open support. That means that, as with the brilliant monome controller, you should see a community that experiments with creative ideas for how to use it. (Nor do I think this is necessarily monome competition – the monome is still beautiful for its minimalism, whereas this should appeal to people who ignored the monome because they needed knobs and faders for additional parameter control.)
For visual software increasingly using OSC, a future firmware update should provide native OSC support (and possibly even DMX in the near future). For everything else, there’s MIDI support now. And unlike the Akai APC40, that means real MIDI support, with actual MIDI in and out ports and endlessly customizable controller assignments and LED feedback, instead of the Akai’s single USB port and permanently-fixed layout. And this is fully bus-powered, so you’re not screwed if you forget your power brick.
I did a full preview for CDMusic. But next week I should get to try one in person, which is the real test.
1
