Great video and documentation from comes our way from Eric Medine:

Documentation of generative visuals applications I built using the Processing platform, ported to the Android OS and run on an HTC Evo. Output is 1080×720 over HDMI to a Vizio LCD display.

Although the EVO has an HDMI output for video, the drivers are crippleware– designed to only display media “approved” by Sprint and its affiliates. Luckily, Sam Bero has been developing a custom HDMI kernel to allow mirroring of any kind of output, and I was lucky enough to be on the beta tester team. Thanks Sam!

Here’s a tutorial on how to port Processing sketches to Android and rooting/installing Full HDMI to your EVO:‚Äčtute_mobileProcessing

Fortunately, this won’t be the case with Honeycomb Android tablets running Processing – we’ve heard people with great luck on XOOM and the like. I also hear lots of good luck with iOS, a topic I hope we’ll cover soon. But it’s nice to see a hack make something work on a phone – impressive. Now we need more tiny projectors with HDMI in.

“Fine,” I hear you say. “But what would really make my day is an unrelated Wiimote-controlled video mixer.”

Your wish – granted!

  • Ben

    Leave it to Eric force a 300 lb gorilla through an HDMI port on a smart phone.Very cool man. Looking forward to what's to come with the new Android I/O options.

    Just a note, that the tutorial link is broken.

  • Peter Kirn

    It's the oddest thing; when we copy and paste links from Vimeo descriptions, they break. If anyone can figure out why, I'm all ears. Anyway — fixed! Thanks!

  • massta

    This is probably one of those moments that, if you have nothing nice to say, then say nothing.

    I'm not looking forward to "what's to come with the new Android I/O options". I feel like we are taking a step back every time we try to push visuals through every new processor. How about a focus on powerful machines and software? Not the latest touch or eye device. Maybe VJ-ing is redefining itself at the moment.

  • Kevin Hackett

    @massta, I totally agree.

  • Peter Kirn

    @massta/Kevin: I think it depends on your aims. These mobile machines are capable of plenty of low-fidelity effects — and, if your work *isn't* pushing the envelope of your desktop GPU, may surprise you with how much of the desktop work they can do in a mobile platform.

    The advantage: you can cheaply, easily add *more* machines, without lots of heat, noise, space, cost, and power. And you get built-in touchscreens, making this far more compact and mobile than, say, having to take a tablet along to control your desktop.

    Provided mixing solutions, I could see these being very productive.

    But I'm certainly not walking away from the price proposition of more powerful desktop machines, either. I think a lot of folks will use both.

    The phone is a poor example as performance is a bit lacking; tablets (hello, NVIDIA Tegra) are more compelling. (Though even the phone – like those little game consoles and such – can become an expressive visual source in the right hands.)

    I would flip around the question and say, why are so many people doing visual performance wasting the processing power of tablets by using them *only* as dumb touch controllers? (Now, okay, there are a few answers to that — but that's why some people are interested in working through some of those obstacles.)