For anyone whose complaint about OSC aka OpenSoundControl is that it lacks broad hardware support, I have one word for you:

Unicorns.

OSC now runs on magical unicorns. (Would a unicorn not want high-resolution, human-readable messages encoded with time-stamps? I think they would. And because OSC is transport-independent, it can absolutely run on magical Unicorn Beams.)

No idea what this post is about? Don’t worry — I’ll have a talking unicorn narrate a proper, sophisticated, complete introduction to OSC for beginners soon. They’re magical, so they can make complex topics lucid to any audience.

Yesterday, I wrote, entirely tongue in cheek and not expecting anything to actually come of it:

I think maybe I’ll start running screaming headlines with things I want in them, if only for good luck. Tomorrow on CDM: “You Know What Annoys Me? The Fact That We Don’t Have Unicorns. Magic Unicorns. Who Speak OSC.”

Today, via Twitter, Max patcher and audiovisual Merlock Andrew Lovett-Barron of Toronto wrote to me:

@peterkirn I made you a unicorn that speaks OSC.

And here it is, for your enjoyment, in Max 5 patch format:

http://andrewlb.com/max/Oscicorn_for_CDM.maxpat

This is, of course, very silly. But it’s an excuse to pitch Andrew’s site, which has lots of patching and coding goodies and visual creations:

http://andrewlb.com/

And perhaps more importantly, OSC now has a mascot. That means t-shirts, plushies, costumes, the lot. Your job: what should the name of this unicorn be?

All MIDI has is an antiquated DIN cable. Oh, yeah, that and millions of compatible devices. We hope OSC support won’t be as rare as unicorns.

Side note: please don’t troll this post, tempting as that may be. It’ll make the unicorn cry.

A new, free software release for Novation’s Launchpad could make your device a lot more usable – and it shows how useful OSC can be for hardware, even if that isn’t OSC hardware. (Now, imagine what OSC-native hardware can do.)

There are plenty of misunderstandings about OSC and the monome out there. Among them, there’s the notion that OSC won’t work without “extra software,” or that the only reason to use OSC messages with something like Novation’s Launchpad grid controller would be to emulate a monome.

Here’s the secret: even if you still don’t know what OpenSoundControl is, the idea is to make messages readable.

Novation released the MIDI message mappings for its Launchpad — that’s a good thing! (See previous post.) But because of the utilitarian and somewhat arbitrary way in which MIDI describes devices, MIDI messages just aren’t terribly readable. For instance, one button is called 50h (in hex), or 80 (in decimal). Where’s 80? Uh…. yeah, no one knows. And simple grid devices like the Launchpad and monome illustrate just how abstract MIDI is. The Launchpad has an 8×8 grid of buttons. You might expect them to be numbered from 0,0 to 7,7, or 1,1 to 8,8. But that’s not actually possible in MIDI.

Will Crossland to the rescue. He’s been working on an OSC wrapper for the Launchpad in Max/MSP (easily ported to other environments if you like). This makes the Launchpad more usable and more logical. It’s just one of what I think could be plenty of efforts to use arrays of buttons on music controllers more fluidly and flexibly. That, in turn, could take the DIY musical ingenuity shown by the monome community to the next level.

Oh, and Will even has an open MIDI networking tool, also built in Max – relevant to the earlier discussion of the day.

http://www.chippanfire.com/SoccoChico/Software

Will’s full description follows.

I thought you might be interested in an OSC wrapper I have been making for the new Launchpad.

From the off, this IS NOT simply a way to make the Launchpad act like a Monome. Oh no. This is a wrapper for converting the MIDI communication provided by Novation into a more human readable (and memorable!) OSC formatted protocol. Additionally the wrapper incorporates a banking system that provides one layer of unaltered MIDI communication (for connection and use with Ableton Live, with all the expected features in-tact) and eight layers (switchable from the Launchpads surface) of OSC transmitting (and controlled) decoupled grid action.

The wrapper is based in MaxMSP, but uses it only for selecting MIDI IO ports, udp communication to the ‘localhost’ (via netsend/netreceive to make it Pd compatible) and a single [js] object with the actual handler/wrapper inside it. Oh, and there’s a local loopback function for testing you have the write MIDI IO selected for each Launchpad you hookup… The wrapper (theoretically, not that I own a fleet) supports up to six Launchpads, each uniquely addressable. If you get really greedy, the javascript could be altered to support more; it is just a 3d array of data elements at its core, currently limited to [6] in one dimension…. The limit of six is a reflection of the maximum number of control surfaces Ableton Live supports.

Specs at a glance:

– Supports up to 6 Launchpad devices, each individually addressable via OSC/MIDI
– Retention of the default MIDI mode for use with Ableton (via internal midi bus)
– 8 OSC mode ‘user banks’ (per device) where the Launchpad (well, technically the wrapper) sends/receives OSC using a markup similar to that used by another popular ‘grid’ device [though it does not directly support Monome markup, as row/col/frame etc messages are not used)
– user bank switching from the Launchpad via top row of buttons
– retains all data received on any bank (even if the Launchpad is not currently focused on it) and updates the surface accordingly when swiching banks

As the handler magic is ALL done via a single javascript file, ANYONE can edit the functionality in their favourite text editor. You then need only MaxRuntime to run the code inside. While this is not an ‘open-source’ solution by any stretch, it can at least be tailored to an individuals needs without spending any money. As the wrapper will communicate happily with Pure Data, an avenue exists for freeware development of OSC patches that use the Launchpad as an interface (via the wrapper).

The appropriate files (along with suitably concise/detailed) documentation can be downloaded from my website (http://www.chippanfire.com/SoccoChico/Software)

Finally, the OSC protocol I have used is fully detailed in the download. It is essentially an extended version of the basic subset (i.e. /press and /led) employed by the Monome. My intention is not provide a ‘Monome Emulator’; the similarity in protocol is both a courteous nod to the Monome creators, and logical progression. The Monome OSC protocol is clearly well thought and well suited to addressing a 2D grid so why reinvent the wheel? I’d expect any sensible grid based OSC controller to use a similar markup as the original is so well thought out…

I have added extensions that allow for the multiple device/multiple bank addressing, as well as some extra ‘data’ for the extended colour set available to the LEDs. If you want to use the wrapper with Monome apps you’ll have to get your hands dirty converting between the two OSC protocols (not that that would be too difficult). The lack of support for /row, /column etc messages is just one example of why this is technically an inferior device to the Monome; that said, i’d still be making a wrapper like this for the banking/multiple device features it enables if I had the budget to buy such a beautiful device…

p.s. Where I am saying OSC, at this stage I really mean ‘OSC formatted’. The implementation is limited to using the netsend/netreceive objects in Max (which perhaps limits their reception to Max/Pd?). I’m a bit too new to using OSC to say I am ‘definitely’ sending Full Packet Messages that could be picked up by any OSC client…. I’d be happy for someone with more know-how to take the final steps in making it truly OSC compliant…

I imagine this could generate plenty of feedback, so fire away.

Max For Live Sneak Peak from max4live on Vimeo.

Suddenly, I have an image of American Ableton hackers patching on their MacBook over Thanksgiving turkey.

After a long, long wait, a public beta of Max for Live is available. The software incorporates the full version of Max/MSP/Jitter – complete with visual output, video processing, and 3D capabilities – with the Live host. Max patches operate with all their usual capabilities as devices inside Live. User interface elements are available to give Max patches conventional Ableton device interfaces, and there are even pre-built elements for useful functions like frequency displays and MIDI patterns. Via the Live API, Max for Live patches are also able to control most elements of the Live interface.

Because of Max’s networking capabilities, Max for Live devices can also be used to route OpenSoundControl data into Live. That isn’t necessarily with the same ease as you might route MIDI, and there’s still no native support in the Live interface, but it is a step forward.

Our friend Michael at max4live.info has been busy documenting the new software. His overview video is at top, and for OSC coverage, see his tutorial [part 1 | part 2].

Updated: Pricing has now been announced.
Max for Live is not included with Live 8 or even (perhaps surprisingly) Live Suite. It will be a US$299 / EUR249 download, available separately, on top of the cost of Live 8 or Live Suite 8. If you already own Max, you’ll have a set of crossgrades available:
1. You own Live. You can add Max for Live for US$99.
2. You don’t own Live, and want just Live. You can get that and Max for Live for US$449.
3. You don’t own Live, and want the whole Suite. Suite plus Max for Live crossgrade, US$699.

Total cost:
Max owners without Live: US$449-699
Live owners without Max: US$299 + cost of the upgrade to Live 8
Max + Live owners: US$99 + cost of the upgrade to Live 8

I think this could arguably be worth the investment, but given the discontinuation of support for developing VST, RTAS, and AU plug-ins in Max – a feature that was formerly free – I expect some resistance. Also, as previously announced, there is no known Max for Live “runtime,” meaning Max patch developers don’t really have a distribution outlet for work made in Max for Live, other than other Max for Live users.

Sign up for the public beta on Ableton’s site, and you’ll be able to grab the downloads (details below). You must be an Ableton Live 8 owner, though you don’t need to own Max 5:
http://www.ableton.com/maxforlive/beta

At the bottom of the page, you’ll have a direct link to download Live 8.1 (the official current build of Live is 8.0.9 otherwise), and a link to Cycling’s site to download Max. (Note: the Max link worked this morning, then promptly disappeared, so it’s possible they’re uploading an updated build is now back up.)

There are full instructions there. I was able to simply click a button and become a beta tester; hopefully you have the same experience. You’ll need to install two pieces of software, both Ableton Live 8.1 on the Live side and Max 5.1.

For the Python-based Live API, and the MIDI and OSC interfaces based on it, this should also come as good news. Live 8.1 should theoretically represent a more stable, feature-complete, fully documented version of the Live API under the hood in Live. That means even without Max for Live, it may be possible to, say, route an OSC input into Live as easily as a MIDI control surface.

If you’d like to join in with other people working on hacking Ableton Live and ask questions, try out our Noisepages group, which should now be functioning properly with a forum, wire, and networking features. More to come with this, with Max for Live, with OSC, with other tools, with… yeah, I’m glad I own a coffee maker.

http://noisepages.com/groups/ableton-hackers

Novation’s Launchpad, its affordable (<$200) "grid" controller, may have a big Ableton logo on it. But underneath, it's just a MIDI controller. Bi-colored LEDs, containing a red and green element for red, green, and amber output (amber = red+green), can be triggered using simple MIDI note and control messages. That means, whether you're looking forward to Max for Live or you're sequencing in a tracker or writing Processing sketches, you can use the Launchpad just like any other MIDI controller.

One of the things I thought was a major demerit for Akai was the fact that they failed to ship a MIDI implementation for the Akai APC40. MIDI implementations are the charts of MIDI messages we've had since the very first MIDI devices came out in the 80s. They're usually printed in the back pages of the manual, and even the cheapest gear has often had one.

Score: Novation 1, Akai 0. Novation has done the MIDI documentation, and then some. Its MIDI “Programmers Reference” is out even before the official Launchpad ship date. And rather than just doing a MIDI chart and assuming people know how to read it, they’ve taken the care to fully explain the way MIDI messages work, how to calculate the right messages, and how to really use this. Experts will have all the information they need, but newcomers will also find they can spend a little time and learn how to do what they want.

Launchpad Support with Downloads (see Programmer’s Reference at the bottom)
Via: Novation released Launchpad Programming Guide, and Protocol [Nezoomie's Zen Wave Blog - great read]

It’s listed as “for Max/MSP programmers,” but anyone using MIDI will want to have a look; that’s obviously relevant to far more than just Max. (In fact, there’s not a single mention of anything specific to Max in the document.)

What might people do with stuff like this? Well, as of just four hours ago, Matt DiFonzo lets us know he’s written a simple monome emulator. It’s even got a clever name:

nonome – monome emulator for Novation Launchpad

There’s some bad news mixed with the good. Even with something as simple as a grid of buttons, MIDI isn’t as friendly as it could be. I still would like to have a MIDI editor for the Launchpad so you can reassign buttons if you like — that’s a feature, incidentally, available on rival Ohm and Block hardware from Livid Instruments. Also, the documentation reveals that Launchpad uses “a low-speed version of USB,” which runs at a maximum of 400 messages per second, thus taking 200 milliseconds to update a Launchpad’s LEDs. (There are some workarounds, but they’re … more work. Clarification: Once you double up messages, though, you can get this to a more acceptable gap, and that’s for updating all the LEDs, not the latency of input messages.)

Also, here’s a hint to Novation: use a Creative Commons license for that document. That way, your users will be free to document even more ingenious solutions and friendly guides. You win, and your users win. For instance, I have the illustration here, which I should be able to do for purposes of reporting on this story. But can I write my own how-to guide using your guide? Why not make it explicit to encourage me to do so? (They list the PDF as “proprietary,” though there’s no explicit license, and I think they just mean “proprietary” as in “what we’ve done on our hardware.”)

That’s a difference between open hardware and closed hardware, but I don’t even want to belabor the point — CC licenses are something a commercial company like Novation could easily use. In fact, if anyone at Novation or Ableton would like to talk to me about why I think it’s a good idea, I’d like to extend an open invitation. I’m no legal expert, but I can explain what it means to me as a user and developer, and connect you with some of the right people at Creative Commons and the CC-using community.

But those gripes aside, kudos to Novation for getting this documentation out here. I think it’s really good news for people experimenting with grid controllers. And we’ll be looking at how all of these tools, hardware and software, fit together, and how open source development can make them more powerful.

Patchers and coders and hackers: if you’re interested in working on interoperability between all this stuff, let us know.

It’s round, it’s mechanically-resistant, it’s tangible, it supports multi-touch and gestures. Yep – it’s the turntable, and outdoing it would mean reinventing the wheel, literally. And so it is that more than a few Ableton fans have wondered how they might work vinyl into their software axe of choice.

Ableton and digital vinyl vendor Serato have announced they’re doing “something,” and then announced at the beginning of October that an announcement would be announced on January 14, 2010 at NAMM. Oh, and they said it will “unleash your creativity,” which sounds good. (It’s better than, say, “Ableton and Serato’s creative partnership will unleash two dozen angry badgers,” or “if you own Ableton Live, what we will say in 2010 is that we will unleash an unspeakable, nameless evil, known only to the ancients, which shall bring about the endtimes.”)

Here’s the surprise – you likely won’t have to wait for Serato to get integrated digital vinyl control. It’s already working with Ms. Pinky, and that means more choice, more DIY possibilities, and a broader variety of ways to integrate turntables and Live.

You see, there’s this little thing called Max for Live, which allows the use of Max patches inside Live as seamless instruments and effects. And one of the best – if least-known – vinyl control systems out there has long featured Max integration: Ms. Pinky. People have already made use of VST plug-in integration, but because Max for Live also connects to the Live API for control of Live itself, the functionality of the two can be expanded.

Via our friend Luthier.Lab, we get a first look at the Ms. Pinky plug-in. And this should be just the beginning, as Ms. Pinky and its Max/MSP support could be a great construction kit for building your own solution – something that may not be possible with Serato.

Ms.PinkyforLive [Luthier.Lab - en Español]
Google Translate (which has some very funny ideas about how to translate Spanish)
Discussion on the Ms. Pinky forum

While you ponder the possibilities, it’s time for a video from Daito Manabe demonstrating that not all turntablists sound quite the same.

multi-touch the storm – interactive sound visuals – subcycle labs from christian bannister on Vimeo.

What if you could mash, mangle, mush, and morph sounds with your fingers on a screen, watching the waveforms dance in response in three dimensions? That “what if” is expressed beautifully in a project by musician-developer Christian Bannister of Portland, Oregon, who works as Subcycle Labs.

The result is like being able to touch sound directly.

Three-dimensional forms morph and vibrate using visuals programmed in Processing, making architectural-organic shapes and spaces that really begin to “look” like sound. These forms can represent synthesis and effects parameters (Christian has done some work with the Massive synth from Native Instruments), or can allow navigation through loops using touch. Gestures remap offsets and duration for audio, scrub and slice, and apply granular resynthesis.

Controls use multiple touch points on a screen (apparently via Community Core Vision and reacTIVision), with sound from Logic, Reaktor, and Max/MSP, and auxiliary control with a joystick array and KORG KAOSS Pad.

Here’s what happens with a Massive bass line:

low frequency entity – subcycle labs from christian bannister on Vimeo.

It’s spectacular, gorgeous work, and I can’t wait to see more. It’s well worth reading through the whole description on the blog for more details, technical, musical, and artistic:

http://www.subcycle.org/

It’s actually paradoxical to talk about music “made” on the monome. The monome, the open controller, is after all, a grid of buttons. It has no sound of its own. But as such, perhaps its design as a blank canvas – without any indication of how a single button may function, without a screenprinted logo or name – that allows computer musicians to project upon it whatever they wish. The monome, more than any other object designed since the emergence of computer performance, is emblematic of what digital music can be. It’s an empty digital grid, like viewing the world of music software under a microscope.

It’s also, therefore, possible for the monome to disappear, leaving behind a spectrum of what people are doing with music on computers. That was what was most striking to me about the music of the monomeet on Saturday in Princeton, NJ: it covered a range of techniques, from glitchy granulation to breakbeat rhythms derived from turntables. Listen to what

In the lineup: tehn (aka Brian Crabtree), the instrument’s creator, playing on the Max/MSP patch mlr that is partly responsible for the monome’s set, through Daedelus, Brian’s friend who helped raise awareness of the strange box of buttons around the world. There are also fantastic sounds from mtn (makingthenoise), picture in the photos here, Edison, ro, %, and altitude sickness.

Here’s what the live sets sounded like. Bet you you can’t hear the monome.

Latest tracks by monomeet

More photos from the event:

Bliss – SevenUpLive 1.4 Preview from bar|none on Vimeo.

monome lovers have come from all over the planet to exchange tips and creative ideas and check out music here in Princeton, New Jersey at the Monomeet. I’m here shooting some video, so expect a feature and links to some of the projects in a few days. In the meantime, JP has set up a live stream, so you can listen in while you clean your studio or whatever you happen to be doing on this Saturday afternoon / evening. Enjoy, and stay tuned for more! (Incidentally, there’s quite a lot of discussion here that’s relevant whether or not you own the monome hardware, really getting to the heart of open source and DIY musical tools. I’ll certainly be sharing some of that soon.)

Updated: what a Saturday! The monomeet was incredibly packed with goodness, from crazy DIY projects to terrific music. And it’s also worth saying, the event wound up being about far more than just the monome; the object becomes a catalyst for all sorts of other discussions of open source and audiovisual technique. I have some video that looks good, lots of cameras were rolling, photographers snapping – expect good documentation over the coming days.

You can also follow the post-event discussion on the monome board.

If you have videos to post, there’s a special monomeet Vimeo group. To get things kicked off, check out the SevenUpLive preview, contributed virtually by bar|none who couldn’t make the event. (See the monome boards for a discussion and download of the software in the video.)
http://www.vimeo.com/groups/monomeetfall2009

If you have photos, of course I always watch the CDM Flickr group:
http://www.flickr.com/groups/cdmu/pool/

For blog posts and so on – or if you couldn’t make it and have specific questions for the monome folks – you can holler on Twitter or via our contact form:
http://createdigitalmusic.com/contact/

GPS Beatmap from Jesse Stiles on Vimeo.

“Locative art,” the idea that somehow location will feed into music and visuals, has eluded culture. We have the technology, in the form of sophisticated databases of location information and highly accurate, publicly-available GPS satellites. But it’s one of those solutions in search of a problem, and begs the question, why?

That is, until you unleash a nearly 6-liter V8 Ford LTD Crown Victoria on the legendary Bonneville Salt Flats, and your driving gets translated to music. Now it makes sense. And sweeping through the salty dust in one of America’s greatest action-car-chase cars of all time, manipulating music on a Max/MSP software patch, all becomes right with the world. (That’s how it is in my head, anyway.)

The planet is your control surface.

Such is the project sent by co-creator Jesse Stiles, who worked with Rich Pell (and editor/documentarian Olivia Robinson) under the name Face Removal Services to perform this vehicular musical production. (Thank, as well, The Center for Land Use Interpretation / GPS Expo 2006. PS – I think we now know what to do with all those clunkers Americans are turning in for Cash for Clunkers.)

Now, this covers only X and Y axis. I think we need to add the Z-axis, for base jumpers. (I had a dream last night in which I was hang gliding from the rim of the Grand Canyon to the Colorado River below, a reminder that the Earth – and computer interfaces – do not have to be flat.)

Through the power of skin-safe conductive ink, Scottish electronic artist Calvin Harris has collaborated with a team to make a synthesizer out of himself and a group of models in bikinis. That’s just fine, Calvin – now what are you going to use for your remaining two wishes?

The project is the creation of Calvin, Steve Milbourne and Phil Clandillon at Sony Music Entertainment, and four masters students at the Royal College of Art Industrial Design program who created the conductive ink: Bibi Nelson, Becky Pilditch, Isabel Lizardi and Matt Johnson. Johnson programmed the interface and music: two Arduinos provide the analog-to-digital connection between the ink-human circuitry and a computer. Patching environment Max/MSP then deals with the data and translates to MIDI, and musical materials are sequenced live and “performed” into Ableton Live. As seen on Engadget and sent in by a number of readers (thanks!) as well as the creative team that did it.

Team member Steve Milbourne writes us with full details and extra behind-the-scenes shots. I wanted to know how they put this together and if there were any false starts or experiments necessary to get it right. He responds:

We read about the conductive ink ‘Bare’ that the students at the RCA (Royal College of Art) had invented and we thought it was pretty cool. We wondered if we could make some kind of musical instrument from it, so we spoke to Calvin and asked him if he’d be up for collaborating.

After quite a bit of mulling over various methods of doing it, we decided to try and create a choreographed routine where people touching hands would close the circuits and trigger sounds somehow.

With the help of the guys from the RCA we began to draw a schematic for the synth, and conceptualize how it would operate, we eventually decided on a layout and that we’d control it using MIDI, by connecting the paint ‘electrodes’ to an Arduino which connects to Max/MSP. This then controls individual tracks in Ableton, and in the live mode automatically quantized them on the fly as the performance took place.

Behind the scenes it was two days of setting up, testing, and working out the routines before the day we filmed it. On the day we spent the morning letting the dancers rehearse and get the timing more or less right (so the notes were quantized into the right places at the BPM running in Ableton, a bit slower than the original track, but dancing at 140bpm was a little difficult for them!) and then we filmed several takes before we got one we were happy with.

False starts, well it took a while to get it all together. At times it seemed like it might not be completely possible. The conductive ink worked better on some people than others (due to a lot of scientific variables such as… how much salt they have in their body, how sweaty they were etc), but the RCA students went through a number of different variants of the paint to get it exactly right.

We messed around with painted pitch bends as well as ribbon controllers on peoples arms – which actually worked too, but we couldn’t fit them into the performance as they weren’t ‘quite’ reliable enough. Cool though.

As to Calvin’s other wishes.. I’m not sure what more you can ask for than a human synthesizer made up of 16 attractive girls in bikinis! ;-)

Fair enough!

In the interest of gender balance, I can think of a few female electronic artists who certainly deserve to turn the tables on the roles here, however.

The ink itself is fascinating, and winks and nods about models aside, it’s terrific to see electronics getting closer to the human body and physical movement. For more on the ink and how it’s used:

http://www.bareconductive.com/index.html

More on Calvin Harris:
http://www.calvinharris.co.uk

Photos courtesy Sony; used by permission.