Turning music and sound into three-dimensional worlds often yields something that fields like a trip through space. But this feels like a real trip. Through pulsing, glowing starfields, “Versum”‘s audiovisual movements are brain-bendingly transformative. Artist Tarik Barri has created an integrated world of sound and image that makes the interface and the compositional realms seamless. It seems as though this really is a musical universe, through whose harmonies of the spheres you can fly like. Boldly going, indeed.

Ingredients: Max/MSP/Jitter, Processing, Java, SuperCollider, GLSL [the 3D shading language], and … some serious skill and time, I imagine.

The work has been in development for some years (not surprisingly, given the results). But it surfaced again as we brought up the 3Dconnexion SpaceNavigator hardware as a practical controller for 3D. See Create Digital Motion:
Look at Me, I’m Flying: SpaceNavigator Hardware + Blender

Tarik’s work resurfaced after a presentation in the UK. Reader janklug writes:

I’m just back from the M4_u Max/MSP/Jitter conference in Leicester (was great, btw), where Tarik Barri presented his project ‘Versum’, both as an installation and as a performance.
The user (and in case of the performance, Tarik) navigates through this incredible 3D-space-sequencer-universum with the help of a SpaceNavigator; glowing objects floating in this space produce sound, and as you approach them, they even give this nice doppler effect…
It was totally amazing to be able to float between pulsing rhythm-planet-objects and shiny drone-beams; navigation was easy and natural. Tarik uses a combination of Processing and Max/MSP; don’t know which one the SpaceNavigator is connected to.
Having tried this, I immediately ordered one; I think it also could be a great interface for M4L…

More information:
http://tarikbarri.nl/projects/versum
PDF documentation [2009]

Significantly, it’s really the act of flying that controls the music. That remains interactive, but it’s the movement through the three-dimensional space that determines what you hear. As the artist explains:

This virtual world is seen and heard from the viewpoint of a moving virtual camera with virtual microphones attached. This camera, controlled in realtime by means of a joystick (or any other kind of controller) moves through space, similar to how first person shooter games work. Within this space, I place objects that can be both seen and heard, and like in reality, the closer the camera is to them, the louder you hear them. So when the camera moves past several visual objects, you simultaneously hear several sounds fading in and out. Consequently, the way the camera travels past them actually causes melodies and compositional structures to be seen and heard.

The visual position of each object coincides with the panning of its sound: objects to the right of the camera will also be heard on the right, and those behind the camera will be heard from behind in case a surround speaker setup is used. This principle also applies to the Z-axis, meaning that sounds can be heard coming from above and below if the speaker setup supports it.

That’s the essential question, to me, when looking at 3D environments for music. What about the dimensionality will interact with the music? Is it something spatial, or will there be other sorts of interactions? (New Zealander-turned-Berliner Julian Oliver worked extensively with game engines, for instance. One solution for him was modifying the “gun” in those games to be an implement for doing things in the space, turning swords into plowshares after a fact by making the gun produce music rather than kill virtual entities.)

So, now you’ve seen some of the technical demonstration. But Tarik uses his work as an environment in which to make audiovisual performances. Here’s what some actual live playing looks like, in a beautiful, meditative piece called “Eleven”:

In fact, the biggest challenge to me of a piece this awesome is that you want an immersive environment, not just the small, rectangular screens that are often all festivals and venues can afford.

Holodeck, anyone?

More:

Add this to the Internet of Things: imagine data recording scratching and scratch performances.

Technologists Jamie Wilkinson, Michael Auger, and Kyle McDonald propose a new way of storing scratch moves as data. They’re not just working in traditional ways, either: they’re hacking turntables and optical mice and cameras, and imagine not only recording performances, but having machines recreate scratching. (Robots!) And they want your help. Kyle writes:

i’m going to be leading a group at art hack day ( brooklyn, january 26th-28th www.arthackday.net/ ) about scratch markup
language, a tool for recording performances from turntablists.

this describes the general idea and who we’re
looking for. we need everyone from web designers/developers, to
hardware hackers, coders and musicians. if you’re interested, or know someone who is interested, contact me or join the google group groups.google.com/group/arthackday/

(We cover the awesomeness that is Graffiti Markup Language on Motion, which goes further to explaining why this sort of data storage can be powerful and enabling.)

All is described – rather bizarrely – in an image. (Can we have plain text, please? It is, at least, a pretty picture!)

I’m not sure how everyone who owns an iPad uses it for music, but I find myself strangely drawn, more than anything else, to analog step sequencers. With MIDI connections – via a special interface or a standard USB MIDI interface connected via adapter to the tablet – you can even drive hardware. For me, the app of choice has been Little MIDI Machine. Developer Chris Randall has a new application in the analog-style sequencing category, though, called Phaedra.

If you haven’t grabbed it already, you have until the New Year to get it for US$4.99 before the price jumps to ten bucks. And you get an impressive array of features:

• Multiple buses, with 32 steps max each
• Programmable note, velocity, gate time, and two MIDI CC outs for each step
• Send or receive MIDI Clock for sync
• Use MIDI hardware (via Core MIDI), other apps (using “background MIDI” or OMAC), or your computer (networking via a MIDI Network Session

Phaedra for iPad [iTunes Store Link; you'll need iOS 5.0]

I wanted to know more about the creation of Phaedra. Developer and musician Chris Randall, known for his work with boutique plug-in maker Audio Damage, released this under a new moniker, Naughty Panther, which does iOS and MIDI development. Chris has been known to mix old and new, as with his musical use of the Apple II. Here, he gives us some insight into how he went through the design process on this new tool.

CDM: How do you sketch out the UI on a project like this? Paper and pencil?

Chris: Normally I just make notes in a little Field Notes notebook as I think about them — I carry one everywhere — then once I have a clear mental image of what I want to make, I just bust it straight out in Photoshop (or, for skeuomorphic interfaces like this one, a combination of Photoshop for the panel and 3D Studio Max for the knobs and buttons).

What inspiration did you consider as far as hardware?

Adam sent me the page for the Moon Modular 568 “Sequential Trigger Source” and quipped that it would make a fun iPad app, and I kind of ran with it. (Their site is a frame-a-thon, but ’tis here: http://www.lunar-experience.com/home.html) As you can see, the UI for Phaedra closely follows the Moon Modular design. The functionality diverges quite a bit, though. Once I had the initial look, I just started adding features I personally thought would be nice in a step sequencer. Then the beta testers had some more input. And now that it is out, I’m getting a ton of great feature requests from the users. The next update will have some cool tricks in it, provided I can figure out how to code them.

What hardware would you recommend for connecting MIDI?

The best MIDI I/O situation for Phaedra is an Alesis iO Dock. Hands down. I have tested it with a half dozen MIDI interfaces via the [Apple] Camera Connection Kit [for connecting driverless USB MIDI interfaces], and they all work fine except that $5 cheap one that people buy from Amazon, which unsurprisingly, has problems. Phaedra also automatically creates a virtual port and connects to all virtual endpoints running on the iPad, so it can drive NLog Pro, Animoog, whatever. And it also is [Apple MIDI] Network Session aware, so it can just work over wi-fi.

I’m going to add OSC output as an option in the next update, I think. I’m still thinking about how to implement that, but it seems like it would be handy, and then Phaedra’s abilities would be greatly increased.

I’m also adding trigger outputs via the audio ports, so you can use Phaedra to clock an external modular sequencer like Makenoise René, or a pre-MIDI drum machine. I’m giving it 48-ppq clock for Korg drum machines, 24-ppq clock for most every other drum machine, and arbitrary rates from 16-ppq on up to 1-ppq for driving modular sequencers and your Monotribe. This should be handy, and will be sample-accurate in line with the MIDI clock output.

See also Chris’ blog entry on the app at Analog Industries:
Some Cool Shit

First revealed last month, PreenFM is an open source hardware synth. As the name implies, it’s an FM synth, with some very serious specs: up to six-operator FM synthesis with some nine algorithms, up to 4-voice polyphony (depending on algorithm), glide, selectable LFOs, modulation matrix, and preset banks with SysEx support. It’s all usable via a display and MIDI support.

It’s also fully open source hardware; whereas early efforts often had commercial restrictions attached, PreenFM is free for use under the GPLv3 and Creative Commons. And it’s got a unique platform under the hood: the open source LeafLabs 32-bit development platform gives this some serious horsepower. It’s very much in contrast to the ultra-inexpensive 8-bit brain of our own MeeBlip synth; think of the MeeBlip as an exercise in what you can do with a little two-stroke engine versus the V8 muscle in this. (The creator says the MeeBlip helped inspire his creation – yes, synths are multiplying!)

You may have glimpsed the PreenFM making the rounds online, but I got creator Xavier Hosxe to tell us more of the gory details and share some sounds.

CDM: So this is all based on the Leaf platform?

Xavier: Yes it’s built around a LeafLab board.
I coded a first version on the Maple [development board]; then when they announced their “Maple Mini,” I realized it was going to be very easy to plug it into a PCB.
I’m not directly connected to [LeafLabs]; I participated in the forum and learnt many things from the team.

They are very friendly and helpful.

What was it like working with the Leaf?

The LeafLabs boards uses an ARM Cortex-M3 microcontroller.

It’s a 32-bit chip runing at 72Mhz that can do 32-bit multiplication in 1 clock cycle, has 128Kb of flash [memory] and 20Kb of RAM. That seems very few but it’s not, PreenFM software uses 92Kb for the moment.

LeafLabs provide a Linux/gcc toolchain that allows to develop in your IDE of choice… Eclipse in my case, which is very confortable.

They also provide a strong bootloader and some libraries that worked perferfeclty for my needs : Usart (Midi), I2C (EEPROM), LiquidCrystal (LCD).

What will you get in the PreenFM kit?

All you need to build yourself a complete synth: PCB, screws, resistors, ICs, audio/midi jack, box, 20×4 LCD, encoders, knobs, buttons… even an USB cable [for power].

You’ll also get a Maple Mini board with PreenFM soft preloaded. The Maple Mini is easily updatable, and you can experiment lots of different things with it.

PreenFM C++ source code is available on GitHub. It’s easy to read and modifiable. If you want to see your name to welcome you on the boot screen, go ahead

To build the kit, you only need a soldering iron and some solder.

There will be 2 differences with the photos you can see on the site: the final PCB will be blue (I should receive them next week). [Ed.: See the photo in blue at top; the orange one is included here for variety! -PK]

Xavier also sends along some welcome news:

Here is a sound I can get with my soon-to-be-released StepSequencer feature in PreenFM.

This is a single voice of a simple 3-oscillator voice. 1 very slow LFO + 2 * step sequencer routed to the modulation indices.

PreenFMStepSeq by cdm

Here’s a sound sample:
PreenFM 1 by cdm

http://www.preenfm.net

In a marvel of DIY engineering, one intrepid user of the tracker-made-modern music making environment Renoise has reconstructed the basic elements of the Ableton Live interface. With quantized clip launching on channels and even a crossfader, it’s unmistakably a copy of what Ableton does. I don’t think you’d dump your install of Ableton for this; the whole reason you’d want a feature like this is really if you prefer other elements of Renoise that are different from Live. But as a proof-of-concept, it’s pretty extraordinary. (Ableton users, the ball’s in your court: someone want to make a tracker in Max for Live?)

mxb has more information on the Renoise forum:
Cells! Preview

We love the bleeding edge, but as mxb notes, “this is still at a very early beta stage; if anyone has any suggestions or feature requests, [they should] make them in the thread on Renoise forums.”

All of this is possible because of Renoise’s powerful scripting environment.

The Cells! video above is a bit primitive – mxb says it’s a result of poor screen capture software, which is also responsible for sync disappearing – but you get the idea. mxb has also built a four-oscillator synth called ReSynth, and previously-mentioned sample import.

http://tools.renoise.com/users/mxb [all of mxb's creations]
http://tools.renoise.com/tools/resynth

Compare the complex model of what a computer can use to control sound and musical pattern in real-time to the visualization. You see knobs, you see faders that resemble mixers, you see grids, you see – bizarrely – representations of old piano rolls. The accumulated ephemera of old hardware, while useful, can be quickly overwhelmed by a complex musical creation, or visually can fail to show the musical ideas that form a larger piece. You can employ notation, derived originally from instructions for plainsong chant and scrawled for individual musicians – and quickly discover how inadequate it is for the language of sound shaping in the computer.

Or, you can enter a wild, three-dimensional world of exploded geometries, navigated with hand gestures.

Welcome to the sci fi-made-real universe of Portland-based Christian Bannister’s subcycle. Combining sophisticated, beautiful visualizations, elegant mode shifts that move from timbre to musical pattern, and two-dimensional and three-dimensional interactions, it’s a complete visualization and interface for live re-composition. A hand gesture can step from one musical section to another, or copy a pattern. Some familiar idioms are here: the grid of notes, a la piano roll, and the light-up array of buttons of the monome. But other ideas are exploded into spatial geometry, so that you can fly through a sound or make a sweeping rectangle or circle represent a filter.

Ingredients, coupling free and open source software with familiar, musician-friendly tools:

• Two projectors
• A monome
• Processing, the elegant and artist-savvy free software for visual code
• Ableton Live and Cycling ’74′s Max for Live, acting as the interactive glue with the sound world
• Drumaxx, Image-Line’s tasty physical-modeled drum synth
• Native Instruments Battery, the sampled drum engine
• Eclipse, the free IDE, for Java coding in this case
• Community Core Vision and reacTIVision (based on our previous info, at least), free and open source community-based projects for making the interfaces you see in movies happen in real life.

Another terrific video, which gets into generating a pattern:

Now, I could say more, but perhaps it’s best to watch the videos. Normally, when you see a demo video with 10 or 11 minutes on the timeline, you might tune out. Here, I predict you’ll be too busy trying to get your jaw off the floor to skip ahead in the timeline.

At the same time, to me this kind of visualization of music opens a very, very wide door to new audiovisual exploration. Christian’s eye-popping work is the result of countless decisions – which visualization to use, which sound to use, which interaction to devise, which combination of interfaces, of instruments – and, most importantly, what kind of music. Any one of those decisions represents a branch that could lead elsewhere. If I’m right – and I dearly hope I am – we’re seeing the first future echoes of a vast, expanding audiovisual universe yet unseen.

Previously:
Subcycle: Multitouch Sound Crunching with Gestures, 3D Waveforms

And lots more info on the blog for the project:
http://www.subcycle.org/

What happens when you meld the most futuristic Microsoft technology with the most futuristic Apple technology with the most ColecoVision-esque graphics as built in Jitter? Or you create gameplay that couples physical human contortion with the step sequencing rhythms of music? A different take on music games, that’s what.

Developers Matt (“M@tt”) Boch and Ryan Challinor work, in their day jobs, on the music game as most people know it, at Harmonix. Harmonix’s roots remain in the rhythm game, so that music play, even at its most serious, is still about musical timing accuracy. Pxl Pusher is a very different mechanic: imagine a step sequencer grid on an iPad, presenting blocks that, true to the classic game Twister, require another player to balance and stretch their bodies to match.

I caught up with Matt and Ryan over the summer at New York’s Museum of Modern Art. Before throngs of crowds swarmed the game – easily one of the most popular of the night – I managed to get some quick footage of the creators doing last-minute patching and trying out gameplay. (The quiet there is atypical; we got to shoot before the doors opened.) An insane travel schedule kept me from publishing sooner, but here, Matt and Ryan share their process.

Another interesting twist: Max/MSP and Jitter allowed extremely rapid prototyping with Kinect, something of interest to anyone doing this sort of work. (And dig those “3D” images … if they don’t blind you.)

CDM: How did you work together on this project?

Matt: Jamin from Kill Screen had asked me to make a project for the Pop Rally, and I was looking for someone to team up with to make it happen. Around the same time, Ryan was developing Synapse, and I got super excited about that tech. Having worked with him closely on Dance Central 2, I was positive we’d make a killer team, so I proposed we team up and make it happen. He got the ball rolling immediately.

Max/MSP is a pretty ideal environment for the both of us to work in, as it lets us evaluate ideas really quickly, and completely obliterate the lines between disciplines that we’re used to in traditional game development. Each of us designed, coded, sound designed, and made art for the game. It was awesome to be able to share in the creation of all parts of the game.

Ryan: We riffed on ideas with each other until it snowballed into the final product. Max allowed us both to work in the same space, as opposed to the traditional programmer/designer arrangement, where I would work in code and Matt would tweak values that I expose. This allowed us to work much faster and blurred the line between programmer and designer.

Any roadblocks, discoveries along the way?

Ryan: The whole project was driven by discovery: discover a fun interaction, then figure out how to leverage it. There were no real roadblocks, other than Matt being on painkillers for the entirety of the project!

Matt: I fell, knocked out four teeth, and fractured my jaw, so I was on heavy doses of painkillers for much of the development. I’m doing much better now, almost fully recovered.

The greatest discovery for me was more of a rediscovery. I remembered how freeing it is to design a game for a very specific context. Before working at Harmonix, I made arcade games in a contemporary art context. Getting back into that mindset was a blast.

Tell us a bit how you work with Max for rapid prototyping. How did you set it up? Any specific tools you made use of? Any tips, either related to Max or Kinect specifically?

Ryan: No real tips for Max, other than do a lot of commenting when you’re working on a file with someone else. As far as Kinect tips, my main advice would be to explore and discover what fun you can have with he input, other than starting with a specific goal. The only tools we used outside of Max were Synapse for the Kinect data, Adobe Premiere for the background movie, and some web app Matt used to generate some of the sound effects.

Matt: We ended up using Beanstalkapp & Versions for version control, which was huge for us in the late stages of development when we both needed to be working simultaneously. It was great that we structured our patch in such a way that we could easily turn elements of the patch into standalone patches, so simultaneous work could happen. You lose some flexibility, but it’s worth it to be able to work in tandem.

How did you conceive the idea for this game?

Matt: Largely through iteration and idea exchange. I VJ around Boston a fair amount and often used TouchOSC to VJ with my iPhone, so I’m not stuck behind my laptop for hours at a time, so when Ryan brought up the idea of using TouchOSC with MAX and Synapse, I was totally sold. We quickly arrived at the mashup between Twister and Step Sequencer, and every after that was polishing mechanics, arriving at a unified aesthetic, and then finding the best way to ramp difficulty.

Ryan: Matt approached me to work on a game for the PopRally right around when I just finished up Synapse, so I wanted to leverage that in the project. I had also just learned about TouchOSC, so I thought it could be fun to incorporate that. So, the initial concept was born out of experimenting with interactions that combined the Kinect and iPad.

How did things go at MOMA? Any surprises in terms of reception? It was effectively rapid playtesting — anything that you would now incorporate into the game? Or things that worked well, for that matter?

Matt: It was a phenomenal success. I never imagined we’d have a line of people waiting to play the game all night, never mind a line full of people cheering, laughing, and clapping as they watched others play. We’ve talked a bit about ways to modify the existing game to make it a bit deeper and more broadly compatible, but I’m also wary of upsetting the balance we arrived at.

Ryan: I was pleased with the reception at MoMA, it was very satisfying to work on a project and then immediately have people playing it, literally 10 minutes after it was finished (thanks to a last-minute feature request from Matt’s friend Christina)

What does it mean to you to have this game in this landmark art museum?

Ryan: I’m really grateful that we were able to show it off in such an amazing space. It feels a little unreal to me, my brain hasn’t really processed it yet.

Matt: It was hugely validating, especially because my Dad was in town and was able to make it to the event. He’s never seen crowds of people play the games I’ve worked on so to have him there, seeing how much fun everyone was having, was awesome in and of itself. That it was at the MoMA? Still haven’t totally processed it. It was the stuff of dreams when I was getting my art degree; it’s going to take a bit for me to internalize that that dream was realized. Not only was I able to show work at the MoMA, but it was shown in the context of so many great games: Bit.Trip Beat, Limbo, B.U.T.T.O.N., QWOP, the list goes on…

How about the connection to Kill Screen Magazine?

Matt: I think Kill Screen is far and away the best game writing happening right now. Both their daily updates on the web and their themed print issues are staples in my life. To be fair, I might be biased as I’m good friends with [editor-in-chief] Jamin, but nevertheless, I think what they’ve accomplished is undeniably phenomenal. What other publication could convince the MoMA to have a video game night?

Can you tell us a bit about your roles at Harmonix, and how you came to be there?

Ryan: I’m a programmer at Harmonix, I’ve worked on The Beatles: Rock Band and the Dance Central series. I was a CS major at the University of Texas, I got an internship at a game studio in Austin that turned into a job, then a few years later a coworker talked me up to someone he met from Harmonix, and I got recruited to work there.

Matt: I am a Project Lead at Harmonix, though I’ve occupied many roles previously, most recently Senior Designer. I started at Harmonix as a Production Assistant while I was finishing my thesis at Harvard. My friend and VJ partner, Josh Randall, is the Creative Director of Harmonix. We’d been VJing together for a bit while I was in school. He gave me a call one day, suggesting I apply for a Production Assistant role. One of my jobs was to track all the prototype hardware, but I ended up spending most of my time repairing it, as my art practice of building arcades gave me a fair amount of experience about mechanical engineering, electronic engineering, and coding. That landed me a role as hardware designer, and, many Rock Band iterations and trips to China later, I was tasked with investigating tech for a potential dance game. That lead to me heading up the development of a game prototype that would become Dance Central, and I’ve been designing for the franchise ever since. A circuitous path for sure, but I’m really happy with where I ended up, and deeply grateful to Harmonix for allowing me to occupy such varied roles throughout my 4 years tenure.

Synapse is something other folks can use, too, correct? What does it do, and where might they begin?

Ryan: Yep, Synapse is a freely released toolset. The primary focus of the project was for controlling Ableton Live with Kinect, but it can be used with anything that receives OSC input. You can find more information at http://synapsekinect.tumblr.com/

Any future plans for this game, or other Synapse-powered stuff?

Ryan: In the immediate future, we’ll be showing off PXL PUSHR at Indiecade in LA on October 8th. Beyond that, I’m not sure what the future is. At the very least, we’re going to keep the ideas of the gameplay mechanic in mind to be incorporated into future projects. As far as Synapse, I’m currently exploring other ideas so I don’t have any Synapse stuff in the works at the moment, but I know of a few other people working on Synapse-powered projects currently.

Matt: As Ryan stated, we’re showing it at Indiecade, and are hoping we’ll get more opportunities to show the game publicly. I deeply enjoyed working on the game with Ryan and I hope that TeamPXL, the moniker we’ve adopted, will develop additional games with the same working methodology. For now, given that we both just wrapped development on Dance Central 2, we’re taking a much needed break to recharge. I know Ryan’s got some awesome audio manipulation patches in the works, and I’m excited to see what comes of those. In time, I’m sure an awesome idea for a game will cross one of our minds and we’ll have no choice but to dig in and make something new!

http://teampxl.tumblr.com/

With great power comes great learning curves – or maybe not. Csound for Live, just announced this weekend and shipping on Tuesday, brings one of the great sound design tools into the Ableton Live environment. You can use it without any actual knowledge of Csound, without a single line of code — or, for those with the skills, it could transform how you use Csound.

For anyone who thinks music creation software has to be disposable, you’ve never seen Csound. With a lineage going literally to the dawn of digital synthesis and Max Mathews, Csound has managed to stay compatible without being dated, host to a continuous stream of composition and sonic imagination that has kept it at the bleeding edge of what computers can do with audio.

Csound for Live does two things. First, it makes Csound run in real-time in ways that are more performative and, well, “live” than ever before, inside the Live environment. Second, its release marks a kind of “greatest hits” of Csound, pulling some of the platform’s best creators into building new and updated work that’s more usable.

If you’re not a Csound user, you just dial up their work and see what your music can do. If you are, of course, you can go deeper. And if you’re somewhere in between, you can dabble first before modifying, hacking, or making your own code. And that means for everybody, you get:

• Spectral processors
• Phase vocoders
• Granular processors
• Physical models
• Classic instruments

More description:

It looks great. It works great. It sounds… beyond great.

CsoundForLive is a collection of over 120 real time audio-plugins that brings the complexity and sound quality of Csound to the fingertips of ANY Ableton Live user – without ANY prior Csound knowledge.

Capitalizing on the design power of Max For Live, what once took pages of text in Csound can now be accomplished in a few clicks of your mouse.

Move a slider on your APC40 and deconstruct your audio through professional quality granular synthesis…

Touch a square of your Launchpad and warp pitch and time with real time FFT processing…

Press letters on your keyboard and create sonically intricate melodies through wave terrain synthesis…

And Dr. Richard Boulanger, unofficial Jedi Master of the Csound movement, instigator of this project, and Berklee School of Music sound and music wizard, posts a bit more:

With my former student, and now partner, Colman O’Reilly, I have been working around the clock for months to collect, adapt, create, wrap, and simplify a huge collection of Csound instruments and make them all work simultaneously and interchangeably in Ableton Live. In this guise, I am able to “hot-swap” the most complex Csound instruments in and out of an arrangement or composition – on the fly. This is something Csound could never do (and still can’t!), but CsoundForLive can, and it makes a huge difference in the playability and the usability of Csound.

Two weeks ago, I played a solo concert in Hanover Germany, at the first International Csound Conference. There, all of my compositions, from 20 years ago to 20 minutes ago, were performed in real-time using CsoundForLive. Tonight, at the Cycling ’74 Expo in Brooklyn, NY, I will be demonstrating the program; and next week, I will be releasing this huge collection (on Tuesday, October 17th, at 12:01am).

A huge part of the complete collection is FREE, and I hope it will make the creative difference in your (and your student’s) lives that it is making in mine. This is a serious game changer for Csound. Check it out. Dr. B.

If you’re at Expo ’74, do say hello to Dr. B for us (and I think you’ll get some nice surprises with this project).

I’ve got a copy in for testing, so stay tuned. And I’ll be doing some follow-ups with Dr. Boulanger and company.

The only bad news here, of course, is that both a supported version of Ableton Live and Max for Live are required to be able to run Csound in this way. In fact, sounds like we have a nice four-horse race going. Max 6 overhauls how multiple patches work (on top of Max for Live), SuperCollider has its own possibilities for multiple real-time patch loading, someone suggested in comments using pd~ inside Pd to manage multiple Pd creations (something fairly new even to most experienced Pd users), and now we have Csound in Live.

But overall, Csound for Live looks like a no-brainer for Max for Live owners, no question, and an exciting taste of the ongoing convergence of cutting-edge creative sound and code with live music making for everybody. As I hinted at in the Max 6 post, I think it’s suddenly a Renaissance for all these platforms.

http://www.csoundforlive.com/

Silly geeky footnote: With pd~ for Max, I know it’s possible to run Pd for Max. And via another external, Pd can also run Csound. So we could theoretically run Csound in Pd in Max in Live. But let’s not get carried away.

More Videos

The generation of people who defined modern computing seems to be passing this year. Following Max Mathews, another Bell Labs titan is lost to us: Dennis Ritchie is the man who created the original C programming language (again at Bell Labs) as well as co-developed the UNIX operating system. President Obama commented that many people learned of Steve Jobs’ death on a device “he invented.” For all Jobs’ contributions, it is as untrue to say that as it is true to say the same of Ritchie: you are quite literally reading this story as served by software derived from his creations on UNIX, using tools written primarily in the language he, with others, devised.

For music, C endures in some form as the basis of the vast majority of tools we use for musical computation – that is, his creation is at the heart of the software with which we all make music. And just as Mathews made the computer sing for the first time, C is a lingua franca on which musical expression is based, the kernel of the vast array of sounds computers today make.

But C is important not simply because, in some form, it remains at the heart of much of the computer code written today. It also introduced in a material sense the idea of portability and cross-platform code, allowing in turn music tools like Csound and others to appear on new computers rather than pass away. It formalized coding concepts that, even in radically-different, more “modern” languages survive. That means that for people expressing musical ideas in code – and anyone using the software that results – software is not tied to specific hardware, lost as new generations of gear cause the old to pass away. The ideas behind C allow computer music to pass from one generation to another – to outlive us.

Ritchie would probably at this point hasten to add that he didn’t work alone, that his work was based on others, that he had colleagues like Ken Thompson who worked with him on C and UNIX. Such is the nature of invention, and unlike the titanic egos of the past (yes, Henry Ford and Thomas Edison, we’re looking at you), some of today’s creations were built by people whose impact was no smaller, but who have been far humbler and lesser-known.

So, get to know Dennis and the many colleagues who survive him. Marvel that the “machine” is not some alien robot at all, but that in your hands, you hold the contributions of creative human beings, the thoughts of complete strangers encapsulated in front of you, and that at the end of the day, you can make it all sing a song.

Via TechCrunch

Light-up grids of buttons are nearly commonplace, but the BlipBox is something different: its array of lights is also a sensor, making it both X/Y controller and light-up grid. And it’s designed to be completely open — firmware, hardware, schematics and documentation are all fully GPL-licensed and open source.

For those of us who aren’t ninja coders, it’s also easy to customize, thanks to friendly software (pictured below) .k for making nifty interactive animations on its display and support for the artist-friendly Processing code environment. As the creators describe it, it’s three (three!) pieces of hardware in one:

• a creative tool and musical instrument
• a large, high definition x/y controller with visual feedback
• a uniquely versatile MIDI and OSC controller

Lest you assume such oddities as this come only from non-musician hackers, these are designed by musicians. The project, built right in London, is available in fits and starts and stock becomes available, but a recent run was “Prices are GBP 140 for a complete ‘box with USB and MIDI interface, and 9v external power connection, in a black aluminium case with perspex side panels.” (To the team: apologies for giving you splashy publicity right as you have precisely none in stock. Readers, follow @cdmblogs on Twitter for updates. Or just follow their site:

BlipBox News

Side note: yes, we need to stop putting “blip” in the name of things. Guilty as charged. (I’ll be writing soon about the Blippo Box, which is … completely different.)