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.

four tiny drum machines from ALH84001 on Vimeo.

Cybernetics is poised to make a comeback. The theory is, everything from electronic circuits to plants and animals can be understood in terms of feedback loops, as organisms – mechanical or organic – respond to input from their surroundings. The father of modern cybernetics, MIT mathematician Norbert Weiner, was inspired by working on the guidance systems of missiles. His writing was picked up Louis and Bebe Barron, informing their organism-like sonic circuits, as used in the film Forbidden Planet. The word cybernetic itself comes from Plato. Plato was talking about human self-governance. But designed with cybernetic ideas in mind, technology, too, becomes self-governing and autonomous – and the sonic circuits, too.

Young designers like Eric Archer are to me the newest continuation of work like the Barrons’. Inside his lab, Eric and others are creating hardware that behaves like intelligent life. In the video at top, four tiny drum machines, equipped with insect-like brains and reflexes, network together wirelessly over infrared, responding to light by way of photocells. These tiny devices form a colonial consciousness.

Eric may be a mad scientist, but he isn’t keeping his work secret or proprietary. He’s sharing the tools, sharing his methods, and with a whole growing crew of sonic DIYers in Austin, Texas, inviting anyone to join the revolution under the banner of the Handmade Music series. (More on the upcoming event shortly.) If you’re not from Texas, a lot of this documentation is also appearing online.

Here are more of the creations, plus the simple but powerful circuit that makes it all happen.

And yes, there’s a lot of potential to wireless IR sync.

The drums have names:

Drum Machines (Eric Archer)
ASR mk I “pops”: two analog damped sine oscillators with photocell pitch control, 16 presets
ASR mk II “snappy”: analog white noise, photocell controlled filter, envelope + VCA, 16 presets
ASR mk III “twiki”: photocell tuned analog osc, photocell tuned LPF, envelope + VCA, programmable
ASR mk IV “boomer”: analog damped sine oscillator, long decay, photocell pitch envelope, programmable

But drum machines are just the beginning of what could eventually be wirelessly synced. First up, this autonomous bassline generator, created by 4ms Pedals

The Autonomous Bassline Generator creates deterministic bassline patterns in a sci-fi retro sound by generating melodies on the fly, based on a knob. It’s just an AVR (attiny44) chip doing all the work, plus an opamp to act as the filter (photocell). The blue button is Tap Tempo, or if you hold it down for 1 second, it syncs up to the pulses on the IR receiver (this lets you beat-sync multiple Andromeda Space Rocker modules). The red button lets you edit a single note in the melody. Pulse-width modulation is currently pre-set to a certain envelope, but that will become user-controllable soon!

Part of the “Andromeda Space Rockers” series of modules, see www.ericarcher.net for drum modules.

The 6-pin header board dangling to the right is an ISP header. Totally hackable!

“Ah,” you say. “But I have computers and things. I don’t just want a bunch of little drum machines running around my studio like so many electronic beetles while I furiously tap my tap tempo in Ableton. Can’t I sync thing up?”

Yes. Yes, you can. There’s already a MIDI-to-IR prototype in the works.

Four analog drum machines are synchronized with a desktop computer running Logic. Logic is playing a loop with TR808 samples. MIDI timecode from Logic is converted to IR Sync with a PIC microcontroller. The PIC flashes an infrared LED, providing wireless clock to a chain of analog drum modules. Each drum module has an onboard sequencer, analog sound generator, and IR Sync repeater. At the end of the video, the tempo is increased to almost 3000 BPM. In a separate test, the system played OK at 1000 BPM. Of course this tempo is ridiculous but it is a nice “torture test” of Nathan’s PIC code.

PIC stuff: Nathan Wooster
drum machines: Eric Archer

Our friends at Bleep Labs also have projects in the works.

Eric and 4ms have contributed the circuits at the heart of this.

This simple circuit handles infrared clock networking. (Click for the full circuit.) I’m assuming you know how to read this; we may have to put together an actual how-to tutorial for those new to electronics, too.

And 4ms has a version for interfacing with microcontrollers.

The Barrons would be proud.

For more on the Handmade Music series as it spreads around the planet, visit http://handmademusic.noisepages.com.

I got to spend yesterday working with the Launchpad; see the video above which I think should help you get a sense of scale and what it looks like. (Also on YouTube) We have additional videos from other sources below.

It’s only been public for less than 24 hours, but as we did with the APC40, I think it’s time for a superguide answering questions about the Novation Launchpad controller.

The Launchpad and the way it works reveals a lot about how controllers work with Ableton Live. You may be surprised to learn a lot of this doesn’t require a special controller and doesn’t require Max for Live – it’s standard Ableton stuff that works with MIDI. (Remember MIDI?) And I think some of these answers could be worth a read if you have interest in hardware control hacking in general.

There have been a lot of questions from myself and readers, so I’ve done my best to get answers. Realize, a lot of this information is developing and is based on my limited understanding, so it’s all subject to change. I’ll update this guide over the next couple of days if I get any corrections.

Side note: What about interoperability? I intend to talk more about OSC and the Live API (and each separately) in coming weeks. I think it’s impossible to judge the full picture of how Live can interoperate with other tools, though, until there’s some more information, so stay tuned on that.

Basic Questions

Q. What do you get with Live 8 Launchpad Edition, the bundled software?

New to Ableton Live, and wondering if you can get anything done with the “lite” Launchpad Edition bundled with the hardware. The short answer is, yes you can. The included edition has restrictions, but it’s still a reasonably capable version if you’re new to Live and want to experiment.

Ableton Live 8 Launchpad Edition vs. Live 8

The Launchpad Edition even comes with 1 GB of Loopmasters loops to get you started.

Most importantly, ReWire support for Master and Slave (Host and Client) is included. That means if you have an existing host and just want to play with Live’s non-linear clip launching features, you can stick with that host, using Live alongside software like Reaper and Reason. You may want to consider upgrading, though, as some cool features like the use of Racks and the ability to slice instruments, plus the “Complex” warp mode, are missing.

Q. What the heck is going on in the crazy Novation video demo? How do I do that myself?

There isn’t any Max patch or other voodoo in the video demo from Novation. It’s all just a standard Ableton Live set, and the fact that the Launchpad responds to MIDI messages as well as sending them (something useful if you’re scripting the Launchpad in software other than Ableton, too).

Matt Derbyshire of Novation put together the video. Matt’s an interesting guy musically when not working for Novation, too – he’s part of a DJ Shadow cover band, for one. He shares with CDM how he went about this:

It’s actually a very simple session.

1) There are four clips only for drums in the drumrack channel

2) Each clip is pre-recorded but EMPTY at 1 bar length

3) These four clips are the first four clips in session mode but for convenience I also learned these to to User 1 mode bottom four left buttons.  Basically setting this up removes the need to rush back to session mode to drop out of record

4) Obviously quantize is on ‘cos my playing ain’t that great.

LED feedback

In User 1 mode the bottom left button turns on/off LED feedback.

The important thing I want from the video is to show that I personally do not think the lack of velocity sensitivity stops drums being played. In fact, to the contrary, I think in creative electronic music it helps to even out the playing.

The still-simpler explanation:

So long as you use the User Mode to play, enable LED feedback, and route MIDI from Live back to the Launchpad, you can get interactive light modes, as seen on the monome and Tenori-On.

Q. Okay, the Launchpad can assign control to continuous values. But it’s got buttons. How do you get eight buttons to replace a fader?

Actually, thanks to an Ableton feature that works with any MIDI controller (not just Novation or Akai), this is quite easy to do. You can assign any range on your controller by holding it down.

From Novation’s Matt Derbyshire:

Step 1: Choose the slider/knob you want (i.e. cross fader)

Step 2: Select USER 1 or 2 mode on launchpad

Step 3: Select MIDI learn mode in Ableton

Step 4: Select the thing you want to control (ie crossfader)

Step 5: Select the range of buttons on launchpad

Note that this also works for playing clips.

Now, obviously, if you control something like a volume fader with a set of buttons, you won’t get continuous values. And unfortunately neither Ableton nor Novation has designed any sort of interpolation between button values (though DIYers could find a way to do that). But I’m kind of finding the angular changes in buttons to be fun to play with. If I want a knob or fader, I’ll use a knob or fader.

Q. What can you do with these User Modes?

There are two User pages. User 1 sends basic note values – minus any velocity sensitivity, just on/off. User 2 sends control changes. User 1 by default will play any active MIDI inputs listening to channel 1. In Ableton Live, User 2 only sends control changes once you’ve mapped it using the MIDI Map, to avoid accidentally triggering notes when trying to control something else. (See also the special behavior with Max for Live below.) Of course, in software other than Live, you’ll set up whatever layout you want.

You can’t rearrange the organization of pitches on User 1 because there’s no real editor for the device; everything is hard-wired. On the other hand, you can always make this adjustment in software, as in a Rack in Live.

Advanced Live Use

Q. How will Max for Live integration work?

Max for Live will use the User 2 page. The good news here is, Max by default will listen only to User 2 while the other modes get routed to Live.

Q. Can you control Devices dynamically using the Launchpad?

No. Unfortunately, while there are pages for mixer settings and a generic way to transmit MIDI control changes, you can’t click a device and have a page on the Launchpad automatically make its eight columns control eight parameters / macros. That’s actually a feature enabled by the simple scripts available for the Korg nano series here on CDM (see my post explaining how this works, follow-up script from reader Raymond).

Of course, because this feature is supported by the Korg with our scripts and it’s very, very compact, the nanoKONTROL and Launchpad could make a great, cheap combo. And if you have Novation’s ReMOTE, Nocturn, and the like, you can alternatively use them – so, for instance, a keyboardist could stick the Launchpad atop a keyboard.

Q. Can you edit MIDI assignments? Is there a MIDI template editor, in other words?

No. All the MIDI assignments are hard-wired. The good news is, everything appears to send MIDI, though I still need to investigate how that works outside Live. The bad news is, as with the APC40, a lot of functionality is organized around Live.

That would be my one potential criticism, which is that we’re moving away from hardware that’s useful everywhere to hardware that’s useful only in one program. But I want more time to see how the Launchpad performs outside Live before I pass judgment on the Launchpad in particular, especially as I don’t even have the final software yet.

I still like editors, though, Novation, if you’re listening.

Q. What if you still have Live 7?

Update – official word: Ableton’s Baptiste Grange tells CDM:

On Nov 1 we’ll release two updates: Live 8.0.7 and Live 7.0.17. These will both support Launchpad.

So, Live 6 and earlier would need to upgrade, but not Live 7.

Hacking

Q. Will we get the full MIDI implementation and protocol for creating custom patches or custom setups with our own software? Will that be true outside of Live, too?

Novation confirms that they plan to release the full MIDI implementation and communication protocol for the Launchpad at launch. That’s something that was missing on the APC40, leaving us all to figure it out ourselves, so I’m looking forward to seeing that documentation. Part of the reason to use MIDI is to have a spec that everyone can read so power users can do what they want.

Q. Can you control the lights using MIDI?

Yep. This should be in the full documentation, too, but here’s a sneak peak. Bjorn from the awesome Covert Operators sent me the velocity assignments, which I’ll be using to hack my Launchpad setup:

Velocity 0 = Off
Velocity 1 = light red
Velocity 2 = medium red
Velocity 3 = full red
Velocity 16 = light green
Velocity 32 = medium green
Velocity 48 = full green
Velocity 17 = light amber
Velocity 34 = medium amber
Velocity 55 = full amber
Velocity 18 = light orange (Lighter > red / darker > amber)
Velocity 35 = medium orange (Lighter > red / darker > amber)
Velocity 31 = full orange (Lighter > red / darker > amber)

The Competition, and the monome

Q. How does this compare to the Akai APC40 / controller XX / the monome as far as Live integration?

The most important point here is that you can easily mix and match. You can even have multiple control surfaces active, operating dynamically, at the same time, as well as multiple MIDI inputs for instruments. Also, most of the features of the Launchpad are available to all controllers. Novation is emphasizing the mix-and-match functionality of the Launchpad. Basically, the feeling is, there is no one control scheme that works for everyone.

The Launchpad is quite similar to the APC40. The clip functions are nearly identical, if in a slightly different (8×8) layout – you get the red onscreen rectangle, the red/green/amber LED indicators, scene launching, the ability to page through clips, and so on.

Basically, the major difference with the APC40 is trading functionality for size and price. The APC40 has the ability to map to Devices automatically, as does Novation’s own ReMOTE series; the Launchpad does not. The APC40 also has encoders, faders, a crossfader, and a number of shortcuts. On the other hand, you can get a lot of the APC40’s functionality in other hardware, meaning the Launchpad can combine nicely with other gear you already have.

One significant edge the Launchpad has over the APC40, though, is that the Launchpad is set up to play drum racks.

The monome is also capable of nearly everything you see the Launchpad doing, with the exception of the clip selection rectangle (though I find that a bit hard to see, personally). In fact, the pages on the Launchpad are clearly inspired (directly or indirectly) by Pages, a GPL-licensed, fully-free, Java-based tool for monome which even appeared in action on David Letterman with Imogen Heap.

You certainly have other options that provide dynamic, automatic control mappings, including the M-Audio Axiom Pro series, the Korg kontrol and nano series, Novation’s ReMOTE line, the Faderfox series, and various others. You can see the built-in scripts available on the Control Surface menu, and anything that supports MIDI can be adapted for additional functionality.

I expect that with the release of Max for Live, scripting custom control for other controllers should be more powerful, even if you don’t have Max for Live installed. Stay tuned in the coming weeks as I’ll be trying to get more complete information on this.

The Live API improvements should be especially benefit the monome project. And remember, the monome isn’t standing still. Because it’s open, it’s conceivable clever users could hack new features.

Q. Can I run monome software on it? OSC?

Yes and – no.

The Launchpad uses MIDI, not OpenSoundControl (OSC). That means you have to translate incoming, sometimes arbitrary MIDI numbers to useful information, and that the Launchpad can’t natively interpret messages in the way the OSC-native monome can. However, as noted in our APC40 hacking superguide, it is possible to use an emulator to translate between MIDI and OSC. That should also be possible with the Launchpad. One challenge is the extra buttons around the grid. I’m going to have to write some Java MIDI code that can map to an arbitrary array of buttons, huh?

Q. Does the Launchpad violate monome’s license and design? How is the monome licensed? How “open” is the Launchpad?

I don’t want to – and cannot – speak for the monome project. However, while the Launchpad is unmistakably similar to the 8×8 grid of pads on the monome, it is not a “clone.” It’s only superficially similar to the monome. Cloning isn’t necessarily healthy for design, but a certain amount of copying can be. Without the spread of keyboard layouts, for instance, we wouldn’t have any of the keyboard instruments we have today – and, indeed, before the standardization on the fortepiano, a lot of keyboard instruments were strange copies of one another. In modern design, the monome is itself indebted to the pad layouts on early drum samplers.

I mention the word “clone” because the Arduinome is an clone of the monome which is distributed non-commercially as a result. It actually duplicates major portions of the design, PCB, and protocol, which is not remotely true of the Launchpad. Because their intention was cloning (for the purpose of ready availability of parts), the creators of the Arduinome consulted with the monome project.

For the record, the monome’s software is released under an open source license, and it uses fully-documented, open protocols, including OSC. The hardware is not technically open source, but it is open to the extent that specifications for the hardware, PCB, and firmware are provided for customization and modification, and the construction of custom housing. You are restricted from using the hardware design to make your own commercial hardware, which means the monome doesn’t fit some more restrictive definitions of what qualifies as open hardware. But it does offer some components that are truly open source, and it affords a great degree of real-world openness for its users.

None of the “openess” of the monome is true of the Launchpad, which operates under more traditional and proprietary models. You can’t easily physically open the Launchpad case (and I expect you’d void your warranty if you did). It uses MIDI, an open protocol, but has a proprietary mechanism for interacting with Ableton Live (at least so far as I can tell). It uses USB, but does not support class-compliant operation – you must install your own drivers, which means you can’t use it with some devices (like Linux netbooks). And the process and operation of the Launchpad are not available or documented. That’s not to discourage the Launchpad, and you still have plenty of power via its MIDI implementation to keep you busy. But that does differentiate it from open hardware like the monome and the newer Livid Ohm64, and it’s worth considering how this difference impacts the ways you want to use the hardware. That issue is much bigger than any one piece of gear, and it’s one I hope we can cover in more depth.

More Videos

MusicRadar did their own hands-on:

Actually, judging by the LEDs, I think they were also working from a prototype and not the final production run. But you will also notice they have an L-shaped USB cord, which I believe is what the final unit will have. (And, heck, that’d be a useful thing to have around here, I may have to pick up some.)

Novation TV also has their own set of videos:

http://www.youtube.com/user/NovationTV

And DJ Tech Tools got a hands-on, too.

Take a weekend, and make something: that’s the challenge behind the Music Hack Day, which joins a growing phenomenon of events built around collective creation. (CDM held its own tangible interface hackday online, which I definitely hope to follow up soon!) Initiated by Dave Haynes of music sharing service Soundcloud, the Hack Day has already hit London. Many of the events were Web app-based and focused on consumption rather than creation of music, but we also saw a chordal synth plug-in and beer bottle percussion instrument.

The Berlin Hack Day, which wound up earlier today, offers still more projects focused on the creation side of music hacking. Having Ableton and Native Instruments as sponsors likely helped the mood. And as you’d expect from one of the world capitals of creative hacking, Berliners don’t disappoint.

Among the projects: a beautiful, elegant 3D sequencer, a fun bird-and-sky multitouch soundmaker with multitouch trackpad input, and a robotic xylophone controlled by monome. Someone even worked out a way to turn NI’s Maschine into a rhythm game, complete with Street Fighter sounds.

I’ve got some of my favorite projects here, but see also an eyewitness report (in English and Italian) at Audio News Room:
Just back from Music Hack Day Berlin
… and keep your eye on the wiki:
Berlin Hack Submissions

xylobot run by monome from robb on Vimeo.

Monomist Rob Böhnke and Ramsey Arnaoot created one of my favorite hackday projects so far: a monome-controlled robotic xylophone. The ingredients: one monome grid controller, one Java application for step sequencing to the output, one Arduino open source controller board, and one terrific xylophone “robot” made of an array of servos that strike the bars of the instrument. Oh, and some hot glue and wood, of course.

Project details

Debugging

Audio loop

Of course, what’s especially impressive is nailing this in just a weekend – imagine what they could do with more time and iterations.

Proof that musical visualizers don’t always have to be trippy, futuristic, Tron-like 3D landscapes (and that’s me speaking as a fan of such things), Gernot Poetsch instead chose a whimsical environment with clouds and cartoon birds, inspired by the graphic identity of Twitter. (No actual Twitter is involved, meaning you lose the, ahem, unreliable, buggy, unfiltered chat network but keep the cutesy happy sky! Works for me!)

The visuals are built in Quartz Composer, which via OSC transmits messages to synthesis language ChucK for noisemaking. The surprise is, the multitouch input is not a Lemur or an iPhone – it’s the new MacBook touchpad under Snow Leopard!

iLoveAcid is a beautiful-looking nodal sequencer by Jakob Penca which uses wireframe “tracks” to guide music playback through a sequencer, transmitting events to your soundmaker of choice via MIDI or OSC. By using curved timelines and connections, it’s a veritable model railroad of music, in which formations combine to form more complex structures instead of simply stepping across a grid. Despite appearances, it is so far only two-dimensional – but then, the z displacement could easily be assigned to some form of modulation. I’m really eager to see the video of this.

One ingredient: Processing, which makes it easier to write visual code and to connect to Java libraries.

Project Page

The hardware controller for Native Instruments’ Maschine software drum machine has been adapted to other software, like Ableton Live. But this is surely the first time it’s been made into a game. Using Maschine’s MIDI output as a game control and sounds from Street Fighter, MaschineFighter is a simple, Simon-style rhythm game. Unlike Simon, though, there’s a twist – instead of rote patterns generated in advance, you face off against a friend and try to out-rhythm each other, battle style. I think it’s actually a pretty brilliant idea, and could become a new sensation for us electronic music nerds – not to mention, it’ll finally test our rhythm in a way electronic performance often does not. (Correction: It is Mac-only, making use of the PYMIDI Objective-C based library, which, since everything else that starts with “Py” usually means Python – a la jThings that mean Java – I assumed, incorrectly, was built on Python. But anyway, if you like the idea, carry on! And, actually, having a pure Objective-C CoreMIDI interface is also pretty awesome.)

Hoping for a video of this, too.

If you have a project that didn’t make this list, or if you add documentation after the fact, let us know.

Code, hardware, and software: Hack Days are all about getting actual stuff made. Berliners, the Music Hack Day that took place in London at The Guardian now gets underway in Berlin this weekend. For anyone who thought the first event was overly Web-centric, there are some new players in Berlin. Ableton is a sponsor, and Ableton, Native Instruments, and RjDj are all presenting hack sessions (in addition to the more Web-focused / consumer-focused 7digital, Songkick, Cloudspeakers, Mufin, SoundCloud, and Echonest). The awesome German musician magazine DE:BUG is also in on the action. I also see our friends at Future Audio Workshop (developers of Circle) in the lineup.

Check out the details:
http://berlin.musichackday.org/
Weekend schedule

So, German readers, who’s going? I’d love to have some spies tell us what the discussions are with NI and Ableton.

I’m, as always, interested in how we can get past geography and share work internationally. So if you’re doing a project, be sure to take lots of pictures, screen caps, code pastes, and the like, and we’ll feature your work here on CDM.

Future events are planned for other cities, and I hope CDM will be involved in some of them. Boston will be the first US event, but it’s on a date I can’t make it. Anyone have a space here in New York you’d like to suggest?

Ed.: It’s more than nostalgia that drives the dedicated chip musician with their modified Nintendo instruments. As guest writer Vijith Assar learned while interviewing Anamanaguchi, some more elemental love of digital synthesis leads these artists to deal with esoteric hardware and crashing homebrewed software. Vijith covered Anamanaguchi for New York’s Village Voice, but this trio had far more geeking than could fit in the free weekly’s pages. The band’s front man and songwriter, flanked by talented NES hacker bandmates, muses on the technology and artistic process – and on why, yes, the act did have to start with blowing on the cartridges. (Surprised?) -PK

I recently had a chance to chat with Anamanaguchi, who would probably be the boy-band teen idols of the chiptune world if the scene were to tolerate such things. Lead songwriter Pete Berkman opened up about his creative process and the digital speed bumps he hits along the way, and guitarist Ary Warnaar is on another planet when it comes to working with Game Boy synths like LSDJ and Nanoloop, but the most freakish technical bits came from bassist James DeVito. He wrote later to describe in detail the customized hardware he’s cobbling together for use on tour, which so far has involved modding the Nintendo for multiple outputs, each with a bolted-on 1/4″ jack and volume knob, and integrating a tiny high-res screen lifted from a PlayStation. He’s even considering a built-in controller for the next version.

The stock NES has five channels of sound — two square waves (lead), triangle (usually for bass), noise, and DPCM sample channel. Normally, these are all mixed down to one mono output, but by tapping directly into pins 1 and 2 of the CPU, we are able to separate them into two outputs. Pin 1 on the NES CPU (2A03) contains the two square channels, and pin 2 contains the triangle, sample and noise channel. A third output is gained from a proprietary audio expansion, containing two extra square channels and a sawtooth channel. This particular one, VRC6, was designed by Konami and featured only on Japanese Famicom games. However, with development carts we are able to get the expansion audio on our NES. The extra audio chip is in the cartridge itself, and outputted directly through a pin on the cartridge. This pin is tied directly to pin 9 on the expansion port, which is where we tap in to get our third output. Directly off those pins I connected 1µf capacitors @ 50V (negative leg goes to CPU pin, positive goes to output) to protect the chips from any short circuits or power surges when plugging a cable in. From there it’s relatively simple, putting them in line with 50K pots and outputting directly to the 1/4 inch jacks out the back. The screen is all wired internally. 5V power is taken from the regulator within the screen and fed into the NES. In order to avoid problems, I cut out the 7805 regulator in the NES and applied the 5V where it needed to be. Audio and video were soldered directly to where the RCA jacks are attached to provide signal to the screen.

And what then? Well, let’s ask Pete.

Vijith: How do you do write these sequences?

Pete: It’s a [DOS] program called Nerdtracker 2 that apparently writes music in the language that the NES can understand. It’s a really home-brewed program. It was made in 1998 by a bunch of Swedish dudes, and it never got out of beta, and it’s prone to crashing, and it has all these terrible bugs in it, half the features don’t work.

And the decision to mix it with guitars?

Pete: I started messing around with it and sending songs back and forth with a friend of mine, and in the beginning, the music I wrote kind of sounded “videogamey,” but as I continued writing, my actual musical influence kind of started to get in there. And at that point, it made a lot of sense to put it as an instrument in a full live band setting, with guitars and drums and that sort of thing. Right before going to NYU, literally NYU move-in day, I released the Power Supply EP through 8bitpeoples, which I had recorded totally by myself at my house except for one track which we recorded with James. All I had was a shitty mic and a shitty guitar and a shitty amp and just recorded what I knew, without any kind of formal training.

It was made in 1998 by a bunch of Swedish dudes, and it never got out of beta, and it’s prone to crashing, and it has all these terrible bugs in it, half the features don’t work.

Do you write using a guitar or a Nintendo?

Pete: It’s a mixture of both. Certain songs, I’ll get the idea as a melody in my head. The music is pretty melodic, so it’s pretty transferable from instrument to instrument. Anything I write on guitar I can put on the Nintendo, and anything I write on the Nintendo I can usually play on guitar – unless it’s way too fast, which it usually is.

Recently, I’ve been getting more into making sounds on the Nintendo that can’t be reproduced by instruments, doing stuff that only the sound chip can do. But more or less I like to create a skeleton of the song on the NES. Ary, on the Game Boy, makes some absolutely ridiculous stuff that’s really fucking weird, like, really just straight-up the weirdest music I’ve ever heard. And the way he does it is not so much thinking musically, but technically. When I came into the 8-bit world, I was definitely the opposite. Any time there’s electronic music, you have people who are thinking technically, and usually that’s music that I’m not very interested in, because it’s kind of cold, usually. I came into the 8 bit world with a very musical background, being in bands growing up and stuff, as opposed to a programming background. But recently I’ve been getting really into making strange sounds on the Nintendo that, like, “Whoa, I didn’t know you could do that with that sound chip.” At the same time, I’m mixing that with that simple pop sensibility.

What I usually like to do is to harmonize everything. Why not? You have two square channels. What else are they going to do but harmonize each other?

James: You don’t have the option of chords, so you might as well harmonize.

Pete: I tend to get bored very easily, which kind of finds its way into the music too. Like, “Oh, here’s an idea. Oh, wait, no, it’s gone now. Now it’s totally different.” In high school, I guess I was diagnosed with ADD — whether that’s bullshit or not, which I think it is, but I’m very capricious, and I tend to jump from thing to thing, in life and in music. But yeah, basically, hyperactivity is something I do.

Basically, hyperactivity is something I do.

How does it actually work? All this time I thought it was a MidiNES, but I recently read a YouTube comment where you said that wasn’t the case.

Pete: Two years ago, I was really upset by the claim that it was MIDI, because it was such a ridiculous process that we don’t do anymore. Back then, you would make the song in Nerdtracker 2, and if you typed in a wrong filename and hit Enter, the program would just crash, and you’d lose everything you had worked on. From there, you’d have to hit Enter to create, like, four different files — temp.ihd, temp.dat, temp.dmc, and temp-dot-some-other-shit. And you’d take all those files and compile them in an NES compiler. That would give you a Nintendo Sound File. And you’d have to do this specifically in Windows 98, because the assembler for XP was fucked up, and it would give you the wrong shit, the wrong hex to burn onto a chip. What you would do from that point is turn it into a binary file, .nsf. The only command is “Play this song at this location in the EPROM’s memory.” And so what you would do from there is you would take that binary file and burn it to a special 28-pin EPROM chip that you would have to order in bulk from some electronics company in New Jersey. And then if you’re lucky, the burning worked. And then if you’re even luckier, all 28 pins are in place in the socket that you soldered into an NES cartridge. And then if you’re even luckier, the NES is willing to play the song in the cartridge — instead of having to blow on it — and then it plays. And that’s the process that we did live, with one chip for each different song, having to flip it out with a guitar pick and replace it with my shaky hands.

James: And the chips aren’t even labeled. So it was this long, complicated process.

Wait, isn’t that last problem your fault?

Pete: Yeah.

James: We’ve come a long way since then.

Pete: Yeah, we have come a long way. That’s why I was… not upset, but adamant about saying what it was. But we’ve got this new system that’s the happiest…

James [unzips case]

Pete: Yeah, we have it here. Instead of burning stuff to a chip, you just take the NSF and put it on a CompactFlash card, and put that in a cartridge that will straight-up just play the song, and has a menu. It’s a 2-gig Flash card, so you can put every song on there, and there’s an on-cartridge browser. And we have a screen hooked up to it, too.

James: The card is usually meant for development, but it also plays the Nintendo sound files that Pete exports, so we can actually just go through it and the file browser has all of our songs listed. (And every game we downloaded from a torrent.)

Ary: He’s currently working on a new Nintendo. They’re going to replace literally every electrical component.

James: Well, not everything. But just make it sound better, like improve the output.

You mean just gutting it and rebuilding it with better parts?

James: It’s more like rebuilding the audio output aspect of it, and certain things like the power supply that adds noise to the signal. It’ll have newer parts, so it’s less likely to explode on stage. With our old setup, if major vibrations were happening to it, it would actually just restart the song.

Pete: Tons of aberrations live.

Ary: And major vibrations happen a lot on stage…

Check out the band for yourself; they’re on tour now.

Vijith Assar is a musician, writer, and computer geek based in New York City. His musical projects have tended toward scores for film, television, and
advertising, and his writing has appeared in the Village Voice, the New York Post, Tape Op, Electronic Musician, and PopMatters, among others. He plays the Chapman Stick and might be going bald because of Reaktor.

Ready for more dynamic control of Ableton Live, on the cheap? My how-to on MIDI Remote Scripting in Ableton Live was just last week, but it has already inspired new scripts for hardware, this time on the Novation Nocturn. (My examples for the tutorial were the Korg nanoPAD and nanoKONTROL.) The Nocturn is also very easy to slip into a backpack or carry-on, and very affordable at US$100-130 street. It just happens to become more valuable with a little user hacking.

Why the Novation Nocturn? After all, Novation touts their own Automap technology for just this purpose. But Novation assumed you only want to use the Nocturn Automap with your plug-ins and not to control Live. Here’s the non-dynamic hack from Novation:

How to control Ableton Live with the Nocturn?

Musician NCKN (”Nicken”) of Aachen, Germany has a better solution. He uses MIDI Remote Scripting to create a downloadable file that will map the Nocturn’s eight knobs to your device racks automatically. If you did pony up for Automap PRO, it’s useful, too, as it allows mapping buttons to Live keystrokes. (Bome MIDI Translator would be another option.)

Complete instructions and a free download at NCKN’s site. Be sure to check out his music, too; there’s some wonderful stuff.

DIY: Automap in Ableton Live with Novation Nocturn

Beautiful ambient-ish tracks with field recordings and acoustic noises blended elegantly into an electronic production:

Back to the controller that has an Ableton logo tattooed on it, we’ve got still more APC40 hacking going on, too. Darren Cowley sends along his Live rig and a video:

APC40 Customization from Darren E Cowley on Vimeo.

The “short” film clocks in at nearly eighteen minutes, but here’s the basic ingredients:

Korg padKONTROL + the free Farmpad customization tool for Mac + Akai APC40 + the mighty, powerful Bome MIDI Translator for more control over events + the now-discontinued Lucifer VST (which I believe has now been replaced with the audio-recording-manipulating Live Sync Recorder.)

There are some really tasty hacks here. Scene launch buttons glitch the sound or impact launch quantization. Controls provide quick access to recording and playing audio loops. Effects are on summed tracks for DJ-style effects manipulation. There are clever tricks for using lights for additional feedback. It’s all proof that no two people really approach Live or even this fairly clearly-mapped hardware in the same way.

Side note: I received a comment from a gentleman who is color blind and therefore can’t see the red/green light feedback on the APC40. Anyone with tips? I don’t think you want to rip out the APC’s lights, for sure. It does really prove that one size can’t possibly fit all in hardware.

CrudBox by Steven Litt at ITP from Core77 on Vimeo.

How much performance power can you pack in a briefcase? What if you could have a magic box that did whatever you wanted?

That’s the question asked, in various different ways, by the artists we’re showcasing at this month’s Handmade Music NYC, Thursday evening 7/16 in Brooklyn. It’s a free event if you’re in the New York area, and we’ll be bringing as much of the work to you online around the world. Full event details:

Brooklyn, July 16: Suitcase Sequencers, Handmade Loopers, APC Hacking, Shake That Egg

Facebook event/RSVP

Join the global Handmade Music group on noisepages

The projects:

Sequence everything: CRUDBOX / STEVEN LITT
The CrudBox is an original hardware step sequencer in a briefcase, which plugs into and sequences everything from cassette decks to power tools and turns them into musical patterns.

Looping hardware: LOOOP-R / RUI PEREIRA
Looop-R is a musical, visual, hardware, software instrument.

Shake the beats: EGGBEATER / TED HAYES
This wireless, egg-shaped controller lets you mash loops, control filters, and play music using live gestures.

Ableton hacking: AKAI APC40, HACKED / MICHAEL HATSIS
Live laptop fans, take note: the commercially-available Akai APC40 Ableton Live controller warped to make new musical performances possible.

Handmade Music is FREE and, as always, made possible by our hosts at Brooklyn’s 3rd Ward creative space, plus our friends at XLR8R Magazine, MAKE Magazine, and DIY marketplace Etsy.com.

Handmade Music’s Brooklyn home:
http://www.3rdward.com/handmade-music/

Handmade Music in NYC and (soon) around the world, @ CDM’s Noisepages:
http://handmademusic.noisepages.com

Reminder: we’re meeting Saturday in Manhattan’s Meatpacking District to chill out, hear some music, and share strange and wonderful and hacked hardware controllers for Ableton Live as part of DubSpot’s Live Sessions tour. If you’re in the NYC area, you won’t want to miss out on music-controlling ironing boards, handheld controllers, and folks like RJ Valeo (Isomer Transition) above.

Full details
Facebook event

But if you’re not in New York, DubSpot and CDM are working together to make sure the weekend gets videoed, and we’re doing some work online.

Friday afternoon I’m chatting and answering questions as I work with the Live API to hack in OSC support for Live, and build a simple app for Google’s Android phone (which can be ported to other platforms, as well).
irc://irc.freenode.net/cdmblogs

Join the Noisepages Ableton Live hacker group for bleeding-edge discussion of some of these topics, too:
http://noisepages.com/groups/ableton-hackers
(I’ll be doing some link dumps with resources later today)

And Sunday, I’ll be giving a workshop about some controller secrets, with more to come online. (Sign up with promo code CDM for a discount if you happen to be registering at DubSpot; otherwise, hang out here.)