What if your musical instrument were gelatinous? Edible?

“Noisy Jelly” is the latest project to imagine that scenario. Thanks to the capacitive quality of gelatin (known to us Americans by the brand name JELL-O and to some simply as “jelly”), you can mix up a set of colored instruments that jiggle when you touch them. Powered by the open hardware platform Arduino to read sensors and Max/MSP to produce sound, it’s the work of a couple of Paris-based students, Raphaël and Marianne Cauvard.

Check out the terrific video featuring wide-eyed children, and specs below.

What makes this more delightful is the possibility that we’ll see orchestras of squishy, organic, edible instruments. NYC Resistor and our friend Ranjit Bhatnagar built their own instrument out of JELL-O (or fruit salad, depending on the iteration). The Gel-tone made a splash (erm, squish) as a more whimsical entry at the Guthman Musical Instrument competition, and was played and eaten at our own Handmade Lounge at Solid Sound Festival in Massachusetts last summer. Hilariously, it debuted at (and was invented for) a JELL-O mold competition. See these couple of videos (Guthman top; Solid Sound bottom) below, and find more information on that instrument:

the resistor jeltone :: an edible toy piano [openMaterials]

How to make your own: The Resistor JelTone (I dearly hope this inspires more copy-cats. Let the gelatinous musical instrument revolution continue!)

More on the Noisy Jelly project:

Note : This project is a fully working prototype made with Arduino and Max/MSP, there are absolut no sound editing in the video…
More picture at this Flickr set
And download the project PDF
Noisy jelly is a game where the player has to cook and shape his own musical material, based on coloured jelly.
With this noisy chemistry lab, the gamer will create his own jelly with water and a few grams of agar agar powder. After added different color, the mix is then pour in the molds. 10 min later, the jelly shape can then be placed on the game board,and by touching the shape, the gamer will activate different sounds.
Technically, the game board is a capacitive sensor, and the variations of the shape and their salt concentration, the distance and the strength of the finger contact are detected and transform into an audio signal.
This object aims to demonstrate that electronic can have a new aesthetic, and be envisaged as a malleable material, which has to be manipulated and experimented.
Author: Raphaël pluvinage (pluvinage.eu and twitter (twitter.com/#!/rpluvina)
& Marianne Cauvard (mariannecauvard.fr)
at L’Ensci Les ateliers (ensci.com)

If you do make your own project, we’d love to see it. Perhaps a gel-orchestra is next.

Several people showed this to me; notably at DE:BUG (Deutsch)
http://de-bug.de/musiktechnik/archives/5820.html

It started as some compelling demos or proof of concept, but it’s plenty real now: the tools for translating movement, gesture, and dance from the body to interactive music march forward. Empowered by Microsoft’s Kinect and an artist-friendly toolchain, even a single, clever developer can do a lot. Sound designer, music producer, and Max/MSP developer Chris Vik of Melbourne has been one of those busy early pioneers, with an incredible tool called Kinectar.

So, the tech is cool and shiny and impressive: what about the actual music? And, even more importantly, what if all the hand waving and moving about could be meaningful? That’s the next step. For his part, Chris is teaming up with a dancer and choreographer to combine his compositional ideas with someone who knows how to move. The Dubstep-y demos (all below) are impressive, true, but the early tests of the work with the choreographer are simply beautiful, and demonstrate that wobble bass isn’t the limit of what this can do. They also turn the arbitrary arm-waggling into a part of the art.

And as for you: the software’s alpha, but you can fire up your copy of software like Ableton Live and grab this software for Mac or Windows and try it yourself. So if you don’t like the results – be the gesture-controlled basslines too wobbly, be they not wobbly enough – you can put your music, and your movement, where your mouth is.

At top, Chris shows off an early test of the dance collab. (There’s more to come.) Below, a tutorial that shows how this works with Ableton. And read on for more from Chris on what the work with the dancer is about, and what the tool can do.

Chris writes:

Since April 2011 I’ve been working solidly with the Microsoft Kinect, developing my software, Kinectar, to enable its use as a MIDI controller for performing music live. I’ve done a number of performances around Australia since I started the project, however, it’s safe to say that, although I would consider myself an electronic musician, I’m certainly no dancer. Enter, Paul…

Dancer, Paul Walker and I have joined forces to bring the Kinect controlled music concept into the world of contemporary dance. Recently we obtained a residency at PACT theatre (centre for emerging artists), where we spent the week developing different ways of implementing my Kinect music control system in a dance context.

My system is developed in Max and uses OpenNI drivers, OSCeleton and Ableton Live.

via Chris’ blog

CDM will check back in with Chris soon, because:

I’ve got some more videos to release over the coming weeks from a range of my different Kinect music performance applications, including controlling/conducting the Melbourne Town Hall Organ and a 100+ speaker Kinect-controlled diffusion performance. I’ll keep you posted when they’re released!

More on the software:

Kinectar Performance Platform is a toolkit developed by music producer Chris Vik to allow the use of Microsoft’s Kinect motion tracking sensor in computer-based music. The software is designed for electronic musicians to expand the way they control their music in a futuristic and extremely expressive way, using only the waving of hands and a small amount of creativity. It can be used to control the simplest of parameters like a filter or LFO, play notes and chords on a sampler or synthesizer, or be programmed to control an entire live-set through nothing more than gesture.

Key Features:

Movement Tracking UI allows manipulation of the Kinect’s human tracking capabilities, displaying all relevant data extracted from the hands location in 3d-space

Instrument Builder lets the user build virtual ‘instruments’ by outputting MIDI notes in three modes:

• Static – Produces a single note value. Useful for drum triggers, turning on/off effects within a DAW or feed that trigger into Kinectar to switch between presets using your gesture
• Solo – Do sweeping solos by selecting from over 40 musical scale presets or click the notes on the UI to make your own
• Chord – Create a progression of up to 8 chords per preset to play live

Global Flags lets you turn on/off Kinectar’s instruments using a MIDI note sent from your DAW, external MIDI controller or Kinectar itself

MIDI Preset Control lets you switch between Kinectar’s presets and instruments using a single MIDI note

Value Editor enables many more MIDI/OSC outputs, for controlling device values

Visual Metronome popout window sits on top of all programs to make it easy to see if you’re in-time when the music gets messy

It’s labeled “rough alpha,” so don’t expect a finished tool here, but you can go download it and give it a try (or learn more about what’s possible):

http://kinectar.org/download

And now, the obligatory (but quite awesome, Chris) Dubstep demo videos:

For the last few decades, generally speaking, we’ve had computers, and we’ve had physical, modular, analog gear. Computers are endlessly patchable, but not using physical cords. Modulars use physical cords, but they lack the flexibility (and affordability) of a computer.

Now, US$25 and an Arduino can change that.

rePatcher is a simple, tangible modular interface for computers. It could work with any software, but right out of the gate it already works with two popular (virtual) patching environments, Max/MSP and the free and open source Pure Data (Pd). You use physical patch cords to make connections, and those connections are reflected in the patch you see on the screen. The patch cords are coupled with requisite encoders for dialing in additional parameter changes. (Reason comes up as a possible candidate for additional compatibility, which would, of course, be really sweet.)

rePatcher is built as a shield for Arduino, so you’ll need one of those, but that still keeps the price low enough to say I absolutely have to have one of these right now.

It’s not the first attempt to do something like this, but it might be the most accessible and affordable – and interesting. And while those cute little patch cords are fun, there’s nothing stopping someone from building on this idea and going to bigger cords and something more extensive than this 6×6 matrix.

Best of all: the magic happens entirely over USB, so if you want to make this work with something else – say, your favorite VJ software – you can do so with anything that can communicate over serial.

More information:
http://www.openmusiclabs.com/projects/repatcher/

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:

Look around the room you’re in. Drum your fingers against some of the objects around you. Now imagine that you could turn those touches into any imaginable sound – and all you’d need to play them is a single contact mic. And we’re not talking just simplistic sounds – think expressive, responsive transformation of the world around you, all with just that one mic, thanks to clever gestural recognition.

Bruno Zamborlin has made that idea a reality, with hold-onto-your-chair results. It’s not available yet for public consumption, but it’s coming.

Bruno explains to CDM:

Mogees is a novel way for transforming any surface into a musical instrument.

By putting a (very cheap) contact microphone over a surface, the software can recognise different types of touch and associate them with different synthesisers.

Users can train the software with their own ‘gestures’, using both bare hands and objects. In the video demo we put the microphone over different surfaces such as kitchen tables and balloons.

The sound synthesis is based on two different techniques:

1 – physical modeling, which consists in generating the sound by simulating physical laws. Different materials can be simulated, such as membranes, strings, tubes and plates

2 – mosaicing, that works as follow: first, users load a sound folder; then, the noise coming from the microphone is analysed and the software continuously finds and plays its closest segment within the sound folder.

Mogees has not been realised yet. It could be published as Max4Live patch in some month.

Yes, we’ll be watching for future versions and publication, with bated breath and eager hands.

http://www.brunozamborlin.com/mogees

Update: Readers point to similar earlier work; obviously, contact mics have long been readily available. I’m not always concerned with whether something is new or not – old and cool can be cool. But what does appear to be new here is the additional gestural analysis to work more accurately with location. That takes an existing technique and refines its musicality. -PK

If you liked the generative, probability-based sequencing seen earlier this week, here’s another example – and it’s free and open source, so if you do want to pick it apart and you own a copy of Max/MSP or Max for Live, you can. Co-creator Giuseppe Sorce points us to the work:

This is a simple generative music synthesizer built in Max/MSP created by Diego Caponera, Nicolò Paternoster and Giuseppe Sorce. It involves 5 FM generators which play notes randomly based on a root key and intervals defined by the user. It’s an university project made for an exam for Sound’s Science degree ( Math Department of Roma Tor Vergata ).

The software is distributed “as is”, without any warranty, under a GPL license.

Not bad for an exam project. A heck of a lot more fun than a paper (and, believe me, I say that wholeheartedly having done a bit of university teaching).

Grab it:
http://code.google.com/p/smilesynth/

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/

Cycling ’74′s Max 6 is now available. See our previous previews:
For Home-brewing Music Tools Graphically, Perhaps the Biggest Single Update Yet [Create Digital Music]
In Max 6, Big Banner 3D + Animation Features for Jitter, Alongside Usability Improvements [Create Digital Motion]

Along with the release comes an updated site, which does a really nice job of presenting different applications, from sound to physical computing to visuals and show control:
http://cycling74.com/products/max/

Pricing details:
US$399 retail (Max 6, now includes Jitter at last)
US$199 Max 6 upgrade
US$249 discounted bundle of Max 6 upgrade + Gen
Academic discounts, including a new annual subscription plan for institutions

Those academic plans finally cover a year instead of 9 months, just in case you want to patch through your summer break.

Gen is the set of low-level objects that allow you to create more sophisticated tools from scratch without coding externals. I’m a little sad to see it priced separately, even if it makes sense from a business perspective, in that users of Gen won’t be able to easily distribute their work to the rest of the user base. Scratch that – yes, they will; they just won’t be able to edit them. So that’s a good compromise! See the upgrade FAQ.

That said, for anyone thinking gen~ is comparable to Reaktor’s Core, here’s a good explanation:
Comparing gen and Reaktor core level [Cycling '74 forums]

(It certainly is in terms of goals, but the way it behaves is very different.)

Max for Live users…

So, what if you’re using Max for Live? Now that Max 6 is available, Max for Live incorporates the new release – if you have a separate license for Max 6. That should be especially useful to Jitter users, who will get all the new Max 6 stuff and a full-featured copy of Jitter that’s otherwise lacking in Max for Live alone.

If you have only Max for Live and not a separate copy of Max, for now, you’ll continue to use Max 5, until an updated Max for Live is available. (When that happens, we’ll be sure to carry the news.)

Of course, dropping in Max 6 may cause compatibility problems, so France-based Julien Bayle has a tip at top on how to switch between your licensed copies of Max 5 and Max 6:

Switching Max5/Max6 inside Ableton Live (max002) [Design the Media; see video, top]

Of course, the good news here is, if you want to use the new Max with Max for Live, you can.

Max 6 in Public Beta; For Home-brewing Music Tools Graphically, Perhaps the Biggest Single Update Yet

Just because a music tool fills your screen with tools and options doesn’t necessarily make it easier to realize your ideas. From the beginning, the appeal of Max – as with other tools that let you roll your own musical tools from a set of pre-built building blocks – has been the blank canvas.

Max 6 would appear to aim to make the gap between your ideas and those tools still narrower, and to make the results more sonically-pleasing. The reveal: it could also change how you work with patches in performance and production. I was surprised when early teasers failed to impress some users, perhaps owing to scant information. Now, Max 6 is available in public beta, and the details are far clearer. Even if Max 5 was the biggest user interface overhaul in many years, Max 6 appears to be the biggest leap in actual functionality.

It’s what I’d describe as a kitchen-sink approach, adding to every aspect of the tool, so there’s almost certain to be some things here you won’t use. What could appeal to new users, though, are I think two major changes.

More visual patching feedback and discoverability. First, building upon what we saw in Max 5, Max’s approach is to provide as much visual information as possible about what you’re doing. It’s probably the polar opposite of what we saw earlier this week in something like the live-coding environment Overtone: Max’s UI is actively involved with you as you patch. There are visual tools for finding the objects you want, then visual feedback to tell you what those objects do, plus an always-visible reference bar and rewritten help. This more-active UI should make Max more accessible to people who like this sort of visual reference as they work. No approach will appeal to everyone – some people will find all that UI a bit more than they like – but Max’s developers appear to be exploiting as much as they can with interactive visual patching.

Multiple patches at once. New objects for filters and data, a 64-bit audio engine, and low-level programming are all well and good. But the change that may more profoundly impact users and workflow is be the way Max 6 handles multiple patches. Max – and by extension Pd – have in the past made each patch operate independently. Sound may stop when you open a patch, and there’s no easy or fully reliable way to use multiple patches at once. (Compare, for example, SuperCollider, which uses a server/client model that lacks this limitation.) That changes with Max 6: you can now operate multiple patches at the same time, mix them together with independent volume, mute, and solo controls, and open and close them without interrupting your audio flow. (At least one reader notes via Twitter that you can open more than one patch at once – I’d just say this makes it better, with more reliable sound and essential mixing capabilities.) Update: since I mentioned Pd, Seppo notes that the pd~ object provides similar functionality in regards to multiple patches and multi-core operation. This has been an ongoing discussion in the libpd group, so I think we’ll revisit that separately!

One upshot of this change: some users have turned to Ableton Live just to host multiple patches. For users whose live performance set involves Ableton, that’s a good thing. But it could be overkill if all you want to do is bring up a few nifty patches and play with them. Now, I think we’ll start to see more people onstage with only Max again. (Check back in a few months to see if I’m right.)

Here’s an overview of what’s new:

• Discoverability: A “wheel” makes the mysterious functions of different objects immediately visible; Object Explorer makes them easier to find, and new help and reference sidebar keep documentation close at hand.

• 64-bit audio engine

• Open multiple patches, solo and mute them, open and close them without stopping audio, mix audio between them with independent volume, and take advantage of multiple processors with multiple patches.

• Low level building blocks: You don’t get new synth objects, but you could build them yourself. New low-level data-crunching goodness work with MSP audio, Jitter Matrix, and OpenGL textures

• More JavaScript: An overhauled JavaScript engine makes JS scripting faster and more flexible, and there’s a proper text editor with syntax highlighting (though, of course, you may still prefer your own).

• New visuals: Vector graphics and “HTML5 Canvas-like” UI scripting (though to me it’s a shame this isn’t just the HTML5 Canvas). There are also massively-expanded Jitter powers, but those are best left to our sister site Create Digital Motion.

• Filters: New filter-visualizing tools for audio filter construction and manipulation.

• Dictionary data type and associated objects let you describe information in a more structured way (all kinds of potential here from control to composition)

• Projects now let you organize data, media, and scripts in the manner more associated with conventional development environments

• What about Ableton? No news on that front, but I expect more soon. Max for Live users will at the very least get the advantages above, since Max for Live is really Max inside Live.

Looking over all that Max does, I have to say, I’m really amazed. I wonder if computer musicians ever pause to consider how fortunate we are. Even if this isn’t the tool for you, its availability – compounded by the availability of a range of other tools – is itself worth reflection.

Max is a program that shouldn’t exist, doing a number of things it shouldn’t do, for a user base that shouldn’t exist, doing things they shouldn’t be doing.

It doesn’t make sense that you could maintain a commercial project for this kind of audience, that you’d wind up with something this mature and powerful that had a continuous lineage stretching back to the 1980s. It doesn’t make sense that musicians would embrace such a tool and produce invention. The only explanation is sheer love.

Then, even as Max reaches new heights, some of the alternatives you have for making your own music tools are simultaneously growing by leaps and bounds. They provide very different approaches to music making (compare Overtone and SuperCollider, or Pd and libpd, or AudioMulch, or new Web audio tools). There really aren’t many fields that have this kind of choice, free and commercial, in their medium. In science and engineering, there’s private and public funding, producing some amazing tools but nothing with this kind of meeting of power and accesibility. There’s just something about music.

The fact that Cycling ‘74 can maintain a business model – just as open source projects maintain volunteer contributions – is a testament to sheer passion and love for music, and a commitment to perpetually re-imagining how that music is made from an atomic level up. There was a wonderful piece on C creator and UNIX co-creator Dennis Ritchie, whom I remembered yesterday, that observed that what he did was to do what others said couldn’t be done. From Max itself to what people make with it, I think that fits nicely.

So, have a look at the public beta, and let us know what you think. The release of Max 6 has caused more people to ask what this means for Pd and other tools, or even whether to patch things from scratch at all, but I’ll leave that question to a bit later. (I do have my own opinion about which tool fits which circumstance and user, but that’s best left to a separate discussion.) For now, you can try Max yourself and see what the fuss is about. If it doesn’t fit your means of music-making, know that you have a wide array of other options – pre-built to low-level code to old-fashioned tape-and-mic approaches, and everything in between. Go out and listen and see what you discover.

http://cycling74.com/downloads/max-6-public-beta/

Montreal-based Damian Taylor, music director and engineer for Björk, is the subject of an epic interview on cycling74.com, spanning music, life in Montreal, working with Björk and what makes her special, and what patching in Max/MSP can mean compositionally and creatively.

Damian has some especially nice reflections on what having an open-ended music environment can mean.

If you’re a musician or composer, Max is an amazing tool that will really open up a completely different way of thinking about music. If you’ve been working on sequencers, looking at time lines, working on tape, or reading off musical scores, then without really realizing it you start looking at music in this very linear way and your brain gets formed into a lot of similar patterns.

But the Max environment provides this whole alternate way of thinking, a whole different flow. Suddenly your own ways of thinking about time and harmony and melodies and everything, expands completely. Music kind of changes shape, you see it from this whole different side. So it’s really, really, really, worth putting in the effort!

It’s a great and well-deserved endorsement for Max, but I think it’s deeper than than any one tool — this way of thinking could also be applied to tools like Pd, AudioMulch (saw a great workshop on that last week), Reaktor, or code-based languages like Csound and SuperCollider. Or, for that matter, I think this notion of thinking in non-linear ways can even be applied to playing your acoustic instrument. It really gets at the heart of how to unlock creativity, I think.

In case you’re afraid of Max or other languages, Damian has some advice there, as well:

If you’ve never done any code or computer language programming before, there are a lot of times where you just have to try to absorb things without really knowing what the hell they are for. And I mean that in the nicest possible way!

I just slowly worked my way through all the tutorials, largely without understanding what the hell I was doing, but just absorbing what was going on, trying to follow every step that was presented. And yeah, it really was a case of locking myself in a room. If there was another noise anywhere, I just couldn’t do it. It took really intense concentration; just trying to absorb what was going on and follow a tutorial from start to finish.

But then at some point I figured I needed to speed things up, so I got in touch with Harvestworks, in New York, who I actually was aware of through an interview on the Cycling ’74 web site. I got tutoring from Matthew Ostrowski — and it was amazing, a complete revelation.

But best of all, for folks using Max/MSP, Damian gives you a leg up, with his nice Woodpecker tool available as a free download for MIDI sequencing.

Woodpecker creates fast 16th note midi sequences from your keyboard input. It’s designed to allow you to bring this very electronic feel into a live ensemble, free of set tempos and click tracks. There are options to allow you to vary the feel of the sequence, play triplets, and explore various arpeggiation styles.

(Nice use of Topspin for a Max patch download! Clever!)

Here’s some music for Damian, as well:
Damian Taylor by MissManagement

damiantaylor.com
bjork.com

And absolutely read the full interview – it even has a nice shot of the Max rig in there:
An Interview with Damian Taylor [cycling74.com]

Full disclosure: this terrific interview is by Marsha Vdovin, who’s also CDM’s business development manager. Thanks for the great work on this, Marsha; I enjoyed reading it, anyway!