OpenSoundControl: Now Compatible with Magical Unicorns

oscicorn

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.

read more

Novation Launchpad OSC Wrapper Makes MIDI More Readable

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.

launchpad_max

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.

read more

Max for Live Beta is Here; Final Version November 23

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

read more

Novation Releases All MIDI Details for Launchpad

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.

launchpadillus

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.)

read more

Listen: Monome-Made Music, from tehn to Daedelus

makingthenoise (mtn); photo by Joshua Schnable.

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:

read more