Want to make a splash among the aficionados of digital sound? Releasing a software instrument emulating a broad collection of vintage digital synthesis chips from game and computer systems seems to do the trick. See my look at that software, and just as importantly, the chips that inspired it.

Within days of the release of Plogue’s Chipsounds, we have a couple of fair reviews of the new tool. Already got Chipsounds? Plogue’s David Viens has released screencasts showing you how to use it. Curious about other ways to explore vintage 8-bit sound? We’ve got that, too, in samples, hardware, and even SuperCollider code.

Reviews are in

Torley has an extensive video review – amazing stuff for something just days old – shown above. Gisle Martens Meyers has a review, too, on the blog Ugress. One complaint is that the plug-in is multi-timbral, rather than requiring different instances. In turn, automation is in the form of MIDI Control Changes, not parameters, since parameter automation really doesn’t deal with multi-timbral plug-ins. But all in all, you can get a lot from both reviews, plus a look at how the software works. There’s also a sense of where the software could go in future updates.

Plogue Chipsounds makes chiptune & video game sounds easy [Torley Lives]
Chipsounds Plugin Chip Sounds [Ugress]

The discussion of Chipsounds has also brought other efforts to resurrect vintage, 8-bit sounds.

Get Your Chip Fix

This is by no means comprehensive, but here are a few of the best goodies readers have pointed out in the last few days:

Free Samples: Little Scale, aka Sebastian Tomczak, has been busy. He’s added sample packs of his own, including a Friday release of the Commodore 64 SID. Add that to Sega Master System, Mega Drive, speech chip, and Atari POKEY and TIA. These are just samples, so rather than being a turn-key solution as Chipsounds is, they’re more of a construction set – though that could make them useful in other scenarios.

C64 SID Sample Pack [little-scale]

Go Hardware! And, in turn, if hardware fires you up more than software or samples, Sebastian has done some lovely work connecting the actual chips to MIDI interfaces.

And here’s the documentation on how to do it with the free and open hardware Arduino platform

Other hardware solutions:
A DIY TI SN76477N-based Voice Module, comprehensively documented (a heck of a lot fancier than the Arduino stuff I wanted to play around with)

SuperCollider Code: For SuperCollider fans, Fredrik Olofsson (aka RedFrik) has built emulations of vintage chips in the object-oriented sound coding language. That’s a doubly delicious thing: aside from allowing you to make 8-bit sounds in the free tool, looking at his emulations is a great way to discover more of what you can do with SuperCollider. You can continue in code the kind of elegant, minimal synthesis design work the early creators of the original chips did in hardware. (Thanks, Howard S and Morgan Packard for the tip!)

SC Code [and a lot of other great SC code there, too... bookmarked, downloaded.]

Video walkthroughs

I know quite a few readers did pick up Chipsounds, so you’ll be pleased to know – in case you missed this – that there are some video demos that walk you through how the tool works. This also gives a better idea of how the software itself functions, since I got distracted waxing rhapsodic about the chips!

As my piano teacher used to say to me, “that should keep you off the streets.”

Enjoy.

The tracker is back. Piano rolls and fake multitrack tape turn out not to be the only way to conceptualize how music is put together in digital form. And Renoise is a terrific way to learn a ground-up approach to production, because you get the quick workflow of the tracker without having to sacrifice so many of the “comforts of home” we’re used to in modern DAWs. So we’re pleased to have our Renoise + Indamixx contest going, not only for existing users, but newcomers, too.

Renoise users have one way of evangelizing why they love their tool, which is to show off, as seen in the excellent video above. But what if you’re new to Renoise, or new to trackers in general, and want to experiment? You don’t even need to make a cash investment: you can start to experiment with a relatively full-featured demo version on Mac, Windows, and Linux. The time investment is the likely barrier. So I asked Montreal-based Dac Chartrand of Renoise, who is also the man who keeps tabs on the community, to share his tips. Here’s what he suggests:

1) XRNS files are source code. Find one you like, load it up, press the spacebar and start clicking around. Renoise will happily chug along as you explore each and every facet of the sequencer. When you get bored of clicking, try remixing. Move some notes around, press the escape key and jam on the QWERTY keyboard. Anyone familiar with trackers will tell you that this is how it’s always been done, this is how it always should be, file sharing since the days of Amiga. PRO TIP: Tutorials and Demo Songs are in the Help menu.

2) YouTube is your friend. Go there, type Renoise, watch and learn. Enthusiastic users show off their tunes, some even make "Do It Yourself" tutorials for good measure.

3) Download the "Pattern Command Quick Reference Card" PDF file. This DIY reference was created by a user in the Renoise forums. It’s a cool print out that folds up and sits pretty  on your desk. Pattern Commands are special columns to the right of notes; lets you take sample manipulation to the next level.

PDF: http://paulmerchant.com/downloads/RenoiseReferenceCard2.pdf

4) If you don’t know trackers, then forget everything you learned about other DAW workflows. You must unlearn what you know in order to be a jedi master. For example, other sequencers  have a very strong relation between track and instrument. In Renoise, instruments go anywhere,  tracks are what you make of them. Other sequencers have a timeline, Renoise has patterns that you chain together to make a song. A newbie mistake is to try to make one gigantic pattern.  Instead, make several smaller patterns and sequence them.

5) Documentation. Yup, it’s thee copout tip. But seriously, there are tons of documentation on the Renoise website. Not reading them is kind of stupid.  When all else fails, browse the forums or see if anyone in IRC chat can help.

DOCS: http://tutorials.renoise.com/
FORUMS: http://www.renoise.com/board/
IRC: http://www.renoise.com/community/chat/

Thanks, Dac! Now, I’ll also be working on some stuff for CDM soon, as well, but this should get you going in the meantime.

Must-Have Renoise Utility

Bantai at Renoise also shares (via comments) an excellent tool for sharing your work in Renoise, compressing files, and – aprospos of Dac’s suggestion – inspecting existing XRNS files.

Another tip: you can get the filesize of your song down by up to a factor 10 if you use lossy compressed samples instead of the default 32-bit stereo FLAC file format. I reckon a small filesize wins you bonus points in a tweaker’s compo.

Since Renoise songs are basically ZIP files containing song data and samples, it’s almost trivial to run the extracted contents of the song through OggDrop or a similar application and zip it up again.

It can be easier: I have written a Java tool that takes the work out of your hands and compresses your Renoise XRNS song automatically:

XRNIRipper

(Java geeks, he also writes me: “I’m using vorbis-java lib from xiph.org and a modified version of jFLAC to support Renoise’s custom 32-bit FLACs. There are also several libs included to convert sample and bit rates. Curiously enough, I couldn’t find any other Java apps that encode files to Ogg Vorbis.”)

More Videos, Tips?

It’s a couple of years old and based on an earlier version, but I especially liked this tutorial for demonstrating what the workflow is about:

And if you Renoise-using readers have tips, or if you find a YouTube video you think is especially awesome, please do share. I’ll get back to working on my basic guide.

Should you quit your day job and go on tour with a rock band?

That’s the question answered by cellist Zoe Keating at Ignite, the 5-minute hyperpresentation series put on by O’Reilly. (At an NYC event, I gave a talk explaining why understanding basic programming concepts was as important as calculating your tip on a bill.)

Zoe Keating on Should you join a rock band? [Ignite's Brady Forrest]

Zoe debunks the myth of the glamorous tour with some sobering realities with which I’m sure at least some readers here are already far too familiar. The presentation is snappy, sharp, and more than occasionally hilarious, a perfect Igniter.

If that’s got you down, though, the same post points to this brilliant “Quantum Cello” piece in which Zoe explains how she works with loops, blending electronic techniques with a 17th-century instrument. That’s the kind of old meets new sensibility we love. And by the way, when Zoe tours with a rock band, she does have good taste — she hit the road with the Dresden Dolls’ fabulous Amanda Palmer.

Quantum Cello, WNYC Radio Lab [Audio podcast / interview]

Octopus transmute!

I can’t in good conscience fail to mention the JUNO-60 video uploaded to the Roland How Do You Juno contest. The work of UTM, you have love that (a) it’s a video of the legendary JUNO-60, the original, analog JUNO, and (b) all those gorgeous flying imaginary graphics. Clarification: I should say that the JUNO has an all-analog signal chain. That is, the oscillators are digitally-clocked DCOs and get digital patch storage, but everything else is analog. So it’s more analog than the JUNOs sold by Roland now. And by “original,” yes, the 60 was an update of the JUNO-6.

Yeah, that’s what we’d label the parameters, too, given complete freedom.

From YouTube:

This is my entry in the How Do You JUNO? YouTube™ Video Contest. All audio was created and performed on my quarter-century-old, pre-MIDI, analog Juno-60 synth. Computer Museum Photo: Scott Beale/Laughing Squid

UTM says he’s a CDM reader, as well, so additional bonus points for that.

Deep thought: who wants to build a CV to OSC converter, and we can really pretend like MIDI never happened? (Apologies, Dave Smith.)

See also Robbie Ryan’s JUNO song. Like, with lyrics.

Getting DIY ads out of YouTube is all the rage these days, but when it comes to certain time-tested synth names, let’s just say the audience is a little different. You love the gear, you make music with the gear, you praise everything that’s brilliant and you’re unafraid of criticizing what’s not. We covered the Roland “How Do You JUNO” contest launch back in April with a look back at the JUNO line through the years. Check out comments for some frank, nostalgia-immune commentary from synth geeks about the high points and low points of the various models. And so, we wind up, oddly enough, with high-production-value ads for even vintage Rolands like this Alpha Juno 2. (Hmmmm… maybe Roland should have set up an eBay affiliate account).

If anyone doubted it, there’s no question: even in the age of computer soft synths, keyboards are beloved items. The video at top is — well, pretty crazy, as you can see for yourself. Check out the crew they put together to make it after the jump.

You still have time to submit your own video to the contest, JUNO owners, if you haven’t already. The entries end tonight, Tuesday, at midnight.

Roland How Do You JUNO Contest Page
YouTube video group with the competition

Voting starts tomorrow (Wednesday) on that same contest page.

If any CDM readers have submitted videos you want to point our way, we can help you rig the contest because we love you um, get the word out.

Disclosure: Roland has generously sponsored CDM for this contest. That allows us to keep the servers humming and to have the unique pleasure of shamelessly pimping discontinued Roland keyboards from the 1980s. (I still want to see what some of you are doing with the V-Synth, which is my favorite current Roland model, but that’ll have to be a separate contest.)

This is my entry to the “This is How I Juno” contest where I explain the many unique features of my Roland Alpha Juno-2.

Producer, Editor, Sound Designer/Editor, Co-Writer, Lead Actor: Henry Borchers
Director, VFX Supervisor, Co-Writer, Actor, Associate Fight Coordinator, Stunt Double: Erik Kjonaas

Extra Special thanks to Alex Champion and the rest of the crew.

Alex Champion: Boom Operator, Voice Actor, Grip

Alex Rott: Fight Coordinator, Stunt Double, Voice Actor, Grip, Sound FX Assistant:

Ben Mayer: Key Grip

Brett Schilke: Sound FX Assistant

Thanks for the helpful participation of Jonathan Fung

For more music by Henry Borchers, please check out www.myspace.com/henryborchers

Previously:
Roland Wants Videos of Junos New and Old; A Look Back at the Juno Line
Keyboard Geeking Day: Roland Answers JUNO Questions, plus 2.0 Sampling on JUNO-G

Gestural Music Sequencer from Unearthed Music on Vimeo.

Something as simple as remapping a single knob can give you new musical ideas. So expand that to entire gestures and live video input, and you can help push your performance in new directions and out of old habits. That’s why it’s always great to see projects like the Gestural Music Sequencer.

Built entirely in free tools – tools fairly friendly even to non-coders – the GMS lets composer and musician John Keston explore new ideas through gestures captured in a video stream. It’s easier to see than to talk about, so check out the just-completed documentary short by Josh Klos, with the aid of Julie Kistler and Brian Smith. (And yes, documentation makes a huge difference; we’d love to see more of this stuff!)

The ingredients:

• Processing, the free, multiplatform coding environment [site | cdmu tag | cdmo tag]
• controlP5, a lovely, light, quick-and-dirty library for UI controls
• Ableton Live – though you could substitute other software via MIDI, Live makes a nice, familiar interactive music engine

Lots more information on John Keston’s wonderful Audio Cookbook blog, which is fast becoming one of my favorite reads:

http://audiocookbook.org/category/gms/

And here’s a really lovely video that demonstrates what you can do with video. It uses a string of lights in a jar as the source. Yes, in a way, it’s almost like having a very focused random generator, but I think there’s nothing wrong with that. There’s an almost analog approach to seeing the source, and using that to organically create music.

GMS: Chromatic Currents Part II from Unearthed Music on Vimeo.

I have to observe, while this works reasonably well with MIDI, it reveals why standardizing on networked communication, as OSC does, makes more sense. In a world of software, “controller” can really mean anything you like. Control is increasingly about software talking to software – including when devices are involved, since they generally have a software layer of their own. Also, because sometimes it’s easier to code this with Processing than with Max, I can see some powerful uses of the Python-based Live API, which we expect to mature later this year. (Yes, the project called Live API seems to be in a holding pattern, but we may be able to work up a more complete, Live 8-ready alternative.)

By the way, our goal is to make noisepages a platform and collection of tools for people doing this sort of work (or anything creative with music and motion), even if you host your blog elsewhere. Stay tuned for the details on that.

Segue – Reset (Live at Big Day Out 2008 Two-up Edit) from Jaymis on Vimeo.

How do you make live performance documentation that doesn’t suck? You’ve been there: you’re trying to shoot footage, you’re trying to edit footage someone else shot, or you’re trying to tell someone shooting footage how to take material you can actually use. Jaymis from Create Digital Motion talks a bit about a recent experience working on footage of Segue – or skip to the end for some tips, either for you or to give that young, eager videographer you hope can make you look cool. Got more thoughts? We’d love to hear them. -Ed.

I’ve posted about this on CDMo, but the topic is applicable to musicians as much as visualists, so I think it’s worth repeating here.

I’m currently editing some video of a gig and interview, taken at an album launch party here in Brisbane. The promoter supplied me with a DVD containing about 10 minutes of interview, and about 45 minutes of “party” footage. If you’re in to documenting your work you’ve probably shot some just like it yourself: Crowd dancing. Shot of the artist. Over the shoulder of the artist tweaking his Lemur. Cute girls dancing. Repeat.

Of that 45 minutes of party action, I was able to extract only about 40 seconds of usable footage. It wasn’t badly shot, just homogenous. There was no shot variation, so it wasn’t interesting to watch, and there was no way to edit for continuity, to give an overall, consistent feel for what was going on.

The missing ingredient, which would allow me as an editor to glue it all together, was closeups.

Last year my collaborators Segue had a high profile gig at the Big Day Out. At the last minute the festival organizers said we couldn’t provide our own visuals, so I took my camera along instead, with a view to shooting footage which could be used for a live video. As there was just a single camera, I tried to cover as much ground as possible, shooting from the front and back of the stage, out in the audience, getting wide shots of the crowd and zooming up close on details of the rig and artists. I’m not a very good cameraman, but I knew that with enough details, enough cutaways, enough different shots, I’d be able to tie everything together at the end.

Getting the footage back to my studio, I took over 9 hours to edit that 45 minutes of footage into a single 7 minute live video. At the time the band were wondering why it was such an intensive job, so I exported a two-up edit of the video to show them how I was able to use closeups, crowd shots, and details to take that single-camera shoot and make it look like there had been a team of ninja cameramen swarming the stage.

The two-up edit shows the final mix on top, and the original continuous camera feed underneath.

This edit took so long because I was very careful with the continuity of shots. If I was cutting from a wide shot of an artist drinking, the following closeup should show him putting the bottle back down. If he had headphones on, then subsequent shots should have them as well. It didn’t matter if those clips were dragged in from 20 minutes earlier in the set, because close shots don’t show enough of the stage detail for the viewer’s brain to realise that things are happening out of order.

I’m sure many CDMu readers have been lumped with the task of capturing video of your own performances, or those of your peers. You may have edited the video yourself, or given it to a handy visualist to have a crack. Even if you have someone else shooting video of your show, it’s worth giving them some direction on what you’d like to to see. Hence:

Jaymis’ Tips for Great, Editor-Friendly Gig Shooting

Leave the camera(s) running constantly: Even if there’s only one, you won’t miss anything. If there’s more than one camera, continuous tape makes multi-camera editing exponentially easier.
Closeups are your friends: Close, detail shots allow you to tie disparate pieces of footage together and to cover camera moves. They also add variety, and show some intimate details of what’s happening on stage. Closeups of the crowd and venue are also great for adding context, without having the distraction of a full human body unrelated to the action.
Keep the camera moving: If you just want to document your set for posterity, having it up the back on a tripod is fine. But if you want to produce some thing visually interesting, then get that camera moving around the space. Remember to hold it still in between moves so you don’t get stabbed by your editor. Take your cues for the music. Move a couple of beats, hold focus for a phrase. Make your moves in between sections of music. Wide shots for builds, close shots in the middle of a section.
Don’t be scared of manual focus: Out of focus shots can be a great transition device. For fast, exciting music, hunting focus reinforces the frenetic nature of the action.

All of the other standard photography rules apply of course, so find someone to tell you about white balance, aperture, shutter speed, exposure etc. If you stuff those up though, there’s a lot which can be done in the edit, but we can’t make up interesting footage in post-production. That has to happen on the night.

Barry Threw demos the K-Bow at Maker Faire from The Amazing Rolo on Vimeo.

Yann Seznec aka The Amazing Rolo brings CDM his coverage of
music tech at the Maker Faire in three episodes today.

As long as there have been computers, violinists have looked for ways of extending the nuances of their physical performance into the digital realm. (Us keyboardists have it easy – we’re used to pressing an array of levers, and a lot of the gestures we make are, arguably, superfluous.) Many of these concepts return to the idea of the bow.

The K-Bow by Keith McMillen Instruments is a Bluetooth-enabled bow with sensors that read bow angle, length, acceleration, grip pressure, and even hair tension. It’s accompanied by software developed in Max/MSP. The bow itself is one of those “if you have to ask, you can’t afford it situations,” at US$4000-5000 retail, though they claim the bow itself – specially-designed kevlar and carbon graphite, anyone? – can compete with more expensive bows even before you add in the sensors.

http://www.keithmcmillen.com/kbow/index.html

In the video at top, developer Barry Threw of Keith McMillen Instruments demonstrates the K-Bow.

Here’s what you get out of the software screen:

Barry has also written up a visit to the STEIM research center and work with sensor bow pioneer Jon Rose.

Jon Rose with the K-Bow

And yes, you can rock out hard with this thing:

I know what you’re thinking – you could also just hook your violin into a pickup and some distortion pedals. I think it’s really the experience of playing it that changes, though I’m just guessing, since I’m not a string player.

Previous research projects:

Jon Rose’s own Hyperstring project (warning: loud hyperviolin audio auto-plays, and I don’t see any mute button!)

The Augmented Violin project at IRCAM: see Emmanuel Flety’s development blog, IRCAM project page and references

And that’s by no means a complete list, of course.

Food for thought: if we didn’t still make “albums,” we’d never know when the album was done. Sure, the delivery mechanism that spawned the album may be disappearing – “LP’s” in particular are long gone. But perhaps, like so many ubiquitous technologies, the album was a fortuitous coincidence of physical practicality and human scale, happenstance generating some unit of creativity that just makes sense to artist and listener alike.

For Imogen Heap, the beloved artist who’s just finished her latest, it’s cause to literally dance and sing, accompanied by a generative Buddha Box. (We can dance around when we get the album in August.)

http://www.imogenheap.com/

It’s not the only approach. Geek troubador Jonathan Coulton rose to Interweb fame partly through the creation of his Creative Commons-licensed Thing-a-Week podcast, which fired up his productivity as he released 52 (get it?) tracks in the space of a year. The episodic form helped him build a following and created a new unit of musical output.

From other parts of the online world, we get a little insight from each of these favorite artists. Imogen Heap videoblogs her latest album and talks promise at top, as found via the lads of SonicState.

Jonathan Coulton talks to one of my favorite non-music blogs, Lifehacker, about staying musically productive – and keeping other productivity away from his musical process. He talks about using Google apps and MobileMe as an intelligent cloud he can share with his assistant and PR person.

He also speaks to musical process:

It’s a combination of things. I generally write when I have guitar in my hand, but, capturing ideas is like … I do use the voice recorder app on my iPhone like crazy. I’ve learned that whenever you get one of those little song fragments, out of the ether, it’s like a dream—no matter how much you’re going to remember it, you’re going to forget it, in like five minutes. And I’ve lost too many of those, so wherever I am, I take my phone out, I pretend that I’m making a phone call, so that people don’t think I’m crazy, and I sing into the voice recorder, and then I have it available later on.

If I want to do a more involved quick capture of something, my MacBook has a piece of software on it called Ableton Live. It’s meant for loop-based composition, but it does recording as well. It’s very easy to capture an idea and sort of rough something out, even if you don’t have a bunch of gear handy. You can use the built-in microphone, use your keyboard as a MIDI keyboard. It’s a nice way to put together a quick demo, and capture some ideas about arrangements.

And, comfortingly, he doesn’t have enough time for music, either, and winding up wasting time on latency problems. (Jonathan, we feel your pain. And if you came to this site and didn’t find your answer, well… sorry. I need to put together a better reference for that stuff; open to suggestions!) He dives into finance, career goals, the game Rock Band and “accidental” discovery of music – all fantastic stuff. Thanks to Kevin Purdy for a great interview – who says you need music publications for great music magazines?

Jonathan Coulton on Making Songs and Geeking Out [Lifehacker]

Out of the box, Akai’s APC40 has some lovely features for plug-and-play control of Ableton Live, with clip triggering, track control, device control, and dedicated buttons for command shortcuts. It also sends and receives standard MIDI messages for every last button and encoder. But what if you still want more? What if you need more controls to do multiple duties, or get bored with simple clip triggering and decide you want additional interaction? Enter the hackers. Already, using MIDI, clever APC40 users are squeezing more function out of this box. And while it isn’t solved yet, there are some clues to the infamous hardware handshake – a System Exclusive string exchanged between the APC and Live that locks certain Live software features to the APC and not to other hardware you might like to use.

Manual MIDI

Before we get too fancy, for power tricks, your first stop should be Akai’s own site:
Tips and Tricks June – APC40

Live allows you to manually override the APC’s dynamic control assignments using the standard MIDI Map. Let’s say you don’t use headphones for cueing. You can select the MIDI Map, pick a control to which you want the Cue Level encoder to be assigned, and you’ll manually assign just that control – the rest of the dynamic template remains in place. Akai has some tips for scrolling through scenes, selecting scenes with one of the two footswitch jacks on the back of the unit, scrubbing and nudging clips, fine-tuning tempo control, and more.

monome Emulation for APC40 and Korg padKONTROL

Our friend Michael Hatsis of trackteamaudio has been hard at work in Max/MSP patching an emulator for the creative patches for the open-source monome hardware. (Thanks on Twitter to ruaridhTVO, too.) By translating from the (and, cough, superior) OpenSoundControl messages the monome supports natively to MIDI, the emulator supports not only the APC but Korg’s padKONTROL, as well. This opens up the use of the APC for creative microsampling and other tasks.

Video demo at top (updated late Sunday night, so if you saw this over the weekend, here’s a tighter version).

Direct download:
http://www.warperparty.com/datter/Monomulator0.9.zip

Forum discussion:
http://forum.ableton.com/viewtopic.php?f=1&t=117307&start=0

And be sure to check out the Java- and Python-powered open-source library for the monome on which Michael’s work is based:
net.loadbang.shado

You’ll find plenty of documentation in Michael’s download, and the hope is that this is just the beginning — you Max patchers out there (and Pd, if we can port this) can keep hacking on it and try out some new ideas. One reason you might want to keep hacking on the padKONTROL is that you could find uses for velocity – unlike the monome and APC, Korg’s 4×4 drum pads are velocity sensitive.

APC40 Customization, Performance Tweaks

This is the best video I’ve seen yet with the APC40. The APC itself is strikingly limited for a MIDI device, without even basic abilities like preset switching or the ability to change default MIDI assignments. But because it’s connected to a computer, if you’ve got some MIDI programming skills and time on your hands, you don’t have to stop there. Stray411, the creator of the brilliant nativeKONTROL software for the padKONTROL, Korg nano series, and Akai MPD32 has turned his MIDI hacking superpowers to the APC.

First, he demos the manual remapping technique. But from 1:38 onward, he remaps and reroutes messages via Bome’s MIDI Translator, commercial Windows (and now Mac) software for more sophisticated mapping of MIDI messages. This allows him to create his own dynamic template for control that applies more functionality to the onboard hardware controls on the APC.

I’m not even sure you’ll want to do this – it can make for a more complex control scheme – but it’s impressive just seeing the ideas out there.

Note that this sort of thing should also be possible via any software that does MIDI input and output, including the free Pure Data (Pd) patching environment and Max for Live when it ships in the fall. (I’m not entirely sure how intercepting MIDI with Max for Live will work, though, especially with the hardware handshake to contend with… more on that in a moment.)

Korg fans (and Akai MPD owners), be sure to check out:
http://www.nativekontrol.com/
And see the nativeKONTROL videos:
nativeKONTROL YouTube Playlist

…and really, that deserves a separate post.

MIDI for Lights

Akai left out the MIDI Implementation that’s traditionally included with MIDI hardware (cough), but it does use standard MIDI messages both for outgoing control data (when you move an encoder or press a button) and incoming messages (like Live switching a light from off to amber to green).

I’m going to publish the Missing MIDI Implementation later this week here on CDM, but to get you started, Danny P on the Cycling ‘74 forum has deciphered the toughest part – the messages that light up the clips:

Midi confusion with APC40

And even better, CerebralNektar (of the nativeKONTROL) project has already built a full-blown Max/MSP template for the clip grid:

OK, let’s hack the APC

The Hardware Handshake: First Clues

Ableton has worked with Akai to add a specialized MIDI implementation to Ableton Live, using a set of System Exclusive messages to prevent the hacker community from emulating certain APC features in other hardware. Specifically, this includes several abilities:

• Using bank buttons to trigger different sets of clips in a larger set, without running out of MIDI messages to do so
• Providing a red rectangle overlay to show which 8×5 (40 clip) array is selected in Live
• Sending MIDI messages for clip status back to the hardware (thus lighting up the lights)

Now, granted, as implemented this functionality may be of limited to use to hardware that isn’t the APC40 – particularly because it’s hard coded for an 8×5 grid of buttons, which is a non-standard size. But having talked even to some passionate fans of the APC, I know it’s bothering a lot of people. I think there are several reasons why.

In short, it’s the first time I know of that standard MIDI messages were used not for the purpose of interoperability, but to actually prevent you from using your own hardware. The APC itself won’t work properly with Live if this string is interrupted (and you’ll see complaints on the user forum in which people are having related problems). Also, while the functionality here is hard-coded to the 8×5 array on the APC, that raises another question – why not make a generic implementation for other hardware? Why not a rectangle that shows a 4 x 4 grid for hardware like the Akai MPD series, Native Instruments’ Maschine controller, and the popular Korg padKONTROL and M-Audio Trigger Finger?

In the meantime, cracking the handshake could be useful for owners of the monome or upcoming Ohm64, even with their 8×8 grid – you can use the last three rows for shortcuts.

Michael Hatsis writes (consistent with what I saw running MIDI through MIDI-OX):

from what I can see both the APC’s 2nd string and Live’s 3rd string have 24 bytes, both with bytes 8-23 different each time
- There’s your handshake…

I have set up two max patches that parse and output the SYSEX sent by both the APC and Live. the one called handshake only outputs the unique bytes for both the APC and Live to the Max window. There are more details inside.

Have a download, folks – this gives you some of the MIDI to look at even if you don’t have an APC40:
http://warperparty.com/data/handshooken.zip

I couldn’t figure out what the algorithm was, but then, I’m not terribly good at that sort of thing. So we’ll be interested to see if anyone else can sort it out.

By the way, this is sent in the clear as MIDI messages. There’s no real reverse engineering here. It’d be like printing the secret password for your speakeasy on a billboard at a rush-hour bottleneck on the 101 highway. Nor is there any kind of theft involved. These are capabilities built into Ableton Live, which Ableton has effectively blocked from use with this System Exclusive communication.

In a matter of days since the hardware shipped, the APC40 user community has already done some incredible work. This to me makes a powerful argument for openness – and it says that the same community could do even more if hardware and software used more intelligent communication schemes like OpenSoundControl instead of being locked to the limitations of MIDI.

A Video to Close us Out

To close, here’s a reminder that part of why we expend this much energy on controllers is to make them personal instruments for ourselves. Here’s a YouTube demo that shows people can make the APC, well … shake.