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.
From the suggestion box at CDM, we’re taking a look at DIY party-rocking sound system technology from the birth of Hip-Hop. Ed.: Resident DIY expert and editor-at-large Michael Una returns – and the man has been known to do strange things with speakers himself.
Say you’re an up-and-coming crew with a turntable and some mics. You’ve got a gig this Friday at the middle school gym (the janitor has been bribed appropriately) and the boys on the corner have been passing out your flyers to all the lovely ladies. Everything’s set, except you heard that Kool Herc is coming to battle. Herc and his mighty sound system schooled you last go-round, so you know you need something fresh to rock the bodies proper. Your DIY solution? The 55-gallon drum sound system.
Step 1: Get yourself two steel 55-gallon barrels and two 15-inch subwoofer cones.
(Kool Herc shown for scale)
Step 2: Have one of your buddies who works at the auto shop around the corner cut a hole in the bottom of each barrel. Drill some holes to mount the speaker facing out from the bottom of the barrel.
Step 3: Face the can towards the floor and have your buddy weld some 6-inch pieces of pipe on to boost it up a bit. Hook up your dad’s hi-fi stereo amp, plug in your mixer, and turn it up as loud as it will go (10 block radius). Get those bodies movin’.
Ed.: Now I can add this to my regrets about school, along with not taking shop to hone my welding skills — seriously, that should be mandatory. (Yeah, like I needed that extra AP. Dumb.) But I’m curious: have any of our readers tried this? Any tips to share? Perhaps we need a DIY speaker summit to try as many amplification and transduction options as possible — complete with welding lessons, natch. -PK
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.
Designing Sound, as the name implies, focuses entirely on the craft of audio from film to games. While there are industry-driven sites devoted to the topic, this blog is entirely the labor of love of composer and sound designer Miguel Isaza, whose writing has also appeared on Spain’s Hispasonic and Monofónicos. (Miguel also tweets to Reaktor aficionados as reaktorlovers.) That personal perspective has imbued the site with the feeling of artists talking to artists.
All week, Designing Sound has focused on Rob Bridgett, who has worked on numerous sound designs for games. Despite the massive growth of the game industry, most top artists have worked largely in obscurity – even less so in sound. There isn’t an equivalent of Ben Burtt, Randy Thom, Walter Murch, or others. (Those greats have been featured in Designing Sound specials, too.) Gaming is a young industry, to be sure, but that’s no excuse for simple ignorance.
In this week’s interviews with Isaza, Bridgett talks frankly about every last detail of what goes into sound production. He’s frank not only about what can go right in a game production – Scarface, pictured above, gets special treatment – but also what can go wrong. The brutal deadlines, fluid production parameters, and tangled production process of games can exact a toll on sound in gaming. The high point of this: Bridgett has gotten to employ the full resources of Skywalker Sound and has been at the forefront of bringing Hollywood-style sonic treatment to gaming.
I’m sure many readers here are curious about the games industry. There’s still time to forward your own questions to Miguel to pass along to Rob Bridgett.
Incidentally, this is beyond what we even imagined for our fledgling noisepages.com, which we’re readying for a full launch as a community and blogging platform. Miguel created Designing Sound without prompting or assistance – it’s entirely his vision. It’s great to have people sharing information in this way. I can’t wait to see what’s ahead.
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
36
![4073407571_9ffe4267f2[1]](http://createdigitalmusic.com/images/2009/11/4073407571_9ffe4267f21.jpg "4073407571_9ffe4267f2[1]")
