flight404

All but one comment has disappeared. Vimeo must be sorting some issues. I will try to answer the questions I have in my inbox.

UPDATE ---- As soon as I hit Post Comment, all the comments reappeared. Odd!

Firstly, thanks for the feedback and kind words!

Bryce: Its made with Processing (processing.org) and uses Amit Pitaru's audio analysis library Sonia, and Andrew Bell's convenience classes.

Syed: I use FFT on the incoming audio to get distinct frequencies. Each sphere 'listens' to a specific frequency and adjusts its mass and charge accordingly. There are also several thousand invisible particles who aid in coloring the sphere surface. I will likely write a blog post describing the process more thoroughly but it isn't that different from how I made the original piece. Read about it here: flight404.com/blog/?p=111

planete: It always seems to happen this way. I will start working on a piece, I will get it working at realtime fps, I decide to post a video and the best way for me to do that is to save out the frames one by one as it runs, which slows it down. So of course I think, "well, since it isn't rendering out in realtime, I might as well crank up the particle count and get more bang". I will probably shoot a video off the monitor to better show how it looks running realtime. Its not too different from this video, but much less haze effect.

James: Ended up staying with Processing. The next order of business, once this and Fuji are shipped, is to port both to Cinder/C++.

InsightVR: For the live version, using a USB microphone. For this rendering, I pulled the audio bit I wanted into the project and analyzed it 1/30th of a second at a time. For each of those blips, I save out the resulting image, then piece the images back together and paste in the original audio.

Thanks defetto. Actually, it runs faster than this video in real-time. The video was prepped at 30fps. The actual piece is near 45. And yeah, this is Processing. Looking forward to finishing the port to Cinder/C++ but I just didn't have time.

Thanks Ryan and Jer.

Looped? Well, that is both correct and misleading all at once! The camera movement is not quite an oval which for this project means that no two camera positions are the same (well, almost. floating-point accuracy). Infinite partially-occluded views of Mount Fuji.

The opening is December 18th.

Thanks!

The background is all happening on the shader. I have a few moving points and using the distances from each frag to the points to determine the texture coordinates. The texture is a dynamic texture based on the audio.

I don't understand your second question: how did I map the audio input into the system?

This project runs real-time, but since I had to render out a video (which cant happen in real-time), I cranked up the particle count for the smoke and haze. Its very close to what I can get in real-time on the PC with Nvidia GTX 260. The only thing happening on the shader right now is the background.