The Traktor Kontrol X1 is an exercise in minimalism, reducing the various uses of Traktor to a few encoders and buttons and a compact form factor. But while it supports MIDI for use with any DJ software, its “high-resolution” mode – as with Maschine before it – uses a proprietary protocol. The unit will sell for US$229 when it ships in February of next year.

The control arrangement of the Kontrol X1 fits a selection of essential parameters into its narrow form factor. The controls are divided in right and left into the two decks, with four sets of effects controls each. There are dedicated controls for browsing through tracks, and cueing and tempo controls. The case can be used either horizontally or vertically.

The strategy appears to be to focus on controlling loops and effects, while those who want to work with digital vinyl can view this as a consolidated mixer / browser interface.

There are some nice extras, too. The box itself comes with Traktor LE, meaning someone can get started with digital DJing for about two hundred bucks. And for another $49, you can add a custom stand and case – details too often left out of controllers.

We saw this controller in September, in use in Richie Hawtin’s set. On NI’s promotional site, Richie has something interesting to say about Traktor, which is that it isn’t necessarily getting used by everyone in the same way:

You can put ten people on a stage with Traktor, and each one of them will have a different way to be creative and bring out their personality through it.

My sense is that this hardware will be well-received, because it is focused on some clear functions, it’s compact, it’s cheap, and it can be used in different ways by different people. Those trends have proved successful in controllers of late. On the other hand, it seems that a generation of hardware controllers that could have employed an open, standard, high-resolution control protocol are doing anything but. Ableton has locked certain software features to certain controllers, and in its controllers uses only MIDI. NI uses higher-resolution data, but has not continued to actively develop OSC. That could mean that, while open-source and visual software continues to progress, we may have to wait years before commercial music software comes to support any standard for this kind of communication using anything other than low-resolution MIDI. The big question may be, is there any incentive to commercial makers to do otherwise?

www.native-instruments.com/traktorkontrolx1.info

Call it the 8-bit preservation society. Chipsounds is now available. It’s a new programmable soft synth, filled with custom oscillators and samples of famous and obscure vintage chips, accompanied by an EP of free chip tracks. Far from a threat to fans of hardware, I think this release is a major achievement for fans of digital sounds.

Oh yeah, and if you’ve been feeling burnt out on chip music in general, firing up some of the sound of some of these more obscure chips could well change your mind. If you like sound, there’s something here for you.

Chip music, championed by a supportive network of artists and fans, has unquestionably made the big time. But for those who value the unique sounds of a variety of vintage 8-bit chips, there is still cause for concern. Even though they’re digital circuits, the unique design of various chips won’t last forever. Some chips are simply disappearing, while others cease to work. At the same time, while the sound of the Nintendo game system has become ubiquitous, lots of other unusual chips don’t get heard. Software emulation and sample packs so far have been pretty shallow. Emulators tend not to model all the nuances of different chips, and samples are really only expressive if they’re presented in the context of something that’s fully programmable and playable.

Enter Chipsounds. Creator David Viens told us about the Chipsounds project back in January:
Authentic Chipmusic Soft Synth Emulation: Plogue Chipsounds Scoop from NAMM

It’s available today, with an introductory price of US$75 ($95 thereafter).

chipsounds @ Plogue [Product Page]

Something like Chipsounds could have been just an attempt to cash in on “what the kids are playing.” But David’s work is more like an epic love poem to the sounds of chips themselves, not only as a reminder of game music but as a unique sound source. And the passionate chip music community got in on the act, as well, with notable artists contributing to the product’s development and in fine form on the EP.

But forget about that for a second. What matters is that chipsounds is an exhaustive, exhaustively programmable set of sounds that almost no eBay budget could ever amass. It takes some unique sounds and allows you to warp them into arrangements and performance configurations not possible with hardware. And it might well make you explore hardware in a new way all over again.

For your listening pleasure, here is the full, free EP with downloadable tracks to set the mood. It’s all been made with Chipsounds by some terrific artists, including David Viens himself, and covers a range of genres and techniques.

Why Chipsounds

David has a really lovely intro in the manual for the tool. He’s got a story like many of us I expect have.

My father bought a Commodore VIC-20 for me and my brother when I was around nine. After a few days with it, I guess he knew I had found my calling. There is not a year that passes without me reminding him how bringing that computer home some cold autumn night changed my life.

But this isn’t just nostalgia. David also notes that some of the limitations imposed by earlier 8-bit hardware caused artists and musicians to invent new techniques that were later lost. These methods can now be rediscovered and coexist with new processes only possible with newer tech. What Chipsounds represents is an expanded “sonic palette,” not just the literal representation of the hardware included. And for those willing to dig into programming the sampling instrument itself, that palette can be even wider and more personal.

David did a whole lot of work on research and experimentation to make this work, but also drew upon the massive community online. Here’s a look at the chips included.

The Instruments

David did extensive research, testing, sampling, and A/B sound programming for the project. Just going through the chips is a nice history lesson – and could be a good introduction for those interested in working with hardware, too. You can check out extensive technical details on the hardware at the chipsounds blog.

SID (6581) and (8580) It’s the mother of all sound chips, and deserves the top space in this list. The SID was the legendary Commodore 64 chip, sampled in this collection at 96KHz. The 8580 I think doesn’t get nearly enough credit, so it’s nice to see both so you can hear the oddities of each.

RP2A03 (NTSC) and RP2A07 (PAL) and RP2A0X (unlimited): This is the big one – the chip in Nintendo’s NES and Famicom. It’s not actually a dedicated audio IC, but a clone of the 6502 CPU, but it still has some unique features and sounds.

DMG-CPU, SGB and DMG(unlimited) The classic: Nintendo’s own sound generator for its Game Boy handheld. Confession time: I’ve heard this chip so much that I’m starting to long for other things. But again, because the Chipsounds collection lets you create hybrid instruments in different ranges, there’s nothing stopping you from inserting DMG sounds where you wouldn’t expect. (And while functioning Game Boys are everywhere and run a variety of amazing homebrewed sequencing software, some of these other chips aren’t as accessible or portable.)

AY-3-8910 (various clocks sources), YM2149 (2Mhz): General Instruments’ sound chip was one of the great sound chips of the 8-bit gaming and computing age, found in the Intellivision, Vectrex, Atari ST, and Sinclair ZX, among many others. That means it’s critical not only to gaming fans, but also fans of the sounds in early tracking musicians, particularly on the Atari ST. It’s even got its own Wikipedia article.

D1867G The classic Casio VL-1 makes a surprise cameo in this collection. Result: you have the opportunity to imagine your own music console that combines the sounds of the VL-Tone with the IBM PCjr, and that’s a beautiful thing. The VL-1 may be the odd man out in this collection, but then, it also exemplifies the lo-fi digital sound of the 80s – and with the ARIA sampling engine, you can warp it to do things it has never done before.

P8244 (NTSC), P8245 (PAL) This is one of the rarer (or at least more unexpected) entries in the collection, the sound chip that drove the Magnavox Odyssey2. Intel’s Video Display Controller used this chip to make both graphics and sound (hmmm… could Chipgraphics be next?) For extreme nerding out, check out David’s full post on working with this chip. Unlike the other entries here, the VDC doesn’t have much documentation online for these kinds of applications.

POKEY (various clock configuration) Atari’s Doug Neubauer created sound capabilities for this chip, used in Atari’s 8-bit computers as well as many arcade games. (The POKEY actually handled not only audio, but keyboard, pots, timing, serial… Arduino fans, take note.) Which arcade games? Try Tempest, Gravitar, Gauntlet and Crystal Castles, for starters.

TIA (NTSC), TIA (PAL) and TIA (unlimited) Another combined graphics and sound chip, the Television Interface Adapter was the sonic soul of the Atari 2600. The variations here in Chipsounds give you a lot of choices, including the awesome “polynomial counters” which create different kinds of distortion. Using keyswitching, you can choose among these sounds live, ideal for keyboardists. And David has even included the sounds the TIA makes when the cartridge was improperly inserted.

SN76489(AN) (various clocks) Here’s my personal favorite: the classic Texas Instruments sound chip was dead-simple (three square wave generators and one white noise generator), but elegant, efficient, and unique in sound. The BBC Micro, IBM PCjr, and ColecoVision game system all used its sounds. I can still hear the echoes of Subroc in my sleep. (Yeah, okay, I was a bit jealous of my friends who had Apple IIs and NES instead of the more oddball PCjr and Coleco I had, but now I’m older and appreciate them more.)

Side note: David was nice enough to share some of his SN chips, so I’m working on building them into standalone hardware and will share the results.

UVI 2637(NTSC) and 2637(PAL): Now we get into the chips you probably haven’t heard. Signetics made this chip for the Arcadia 2001 console developed by Emerson (yeah, the electronics company) in the heady year of 1982, before the meltdown that would purge the home gaming market. That console was widely cloned, under names like the Interton, Leisure Vision, and MPT-03.

VIC-I : 6560 (NTSC) 6561(PAL) in various configuration Here’s another oddball chip: the VIC-I, used in the VIC-20, had 7-bit pitch range, giving you oddly-tuned scales, plus a truly strange noise generator. That strange sound is rarely heard, but leave it to the demoscene to exploit it. From the Chipsounds manual:

In 2003, a brilliant demo writer by the name of Viznut reverse-engineered this side effect, mapping all possible “weird” waveforms that the chip was able to reproduce in a deterministic manner, and put the to good use in his now famous “Robotic Liberation” demo.

Here’s a look at that creation:

The Software

Let’s get something out of the way: I believe in synths. I’m naturally skeptical of samples. If I believed for a second Chipsounds was about plugging in some sampled sounds and hitting a key and waiting, I wouldn’t have posted this article. Fortunately, Plogue’s ARIA sampling-plus-synthesis engine is powerful enough to allow immense programmability and playability. It’s loaded up with programs that model every last detail of these instruments, while also providing the possibility to create your own, unique performance configurations. Samples make up just a portion of the sound, used where appropriate, with lots of custom oscillators and modulators, as well. This is really a full-blown instrument, not just a sample library. (ARIA has previously been sampling-only, but Chipsounds is the first of a line of instruments to use synthesis, as well.)

Standalone, plug-in modes:

As a plug-in, Chipsounds works with VST on Mac and Windows, RTAS (for Pro Tools) on Mac and Windows, and Audio Units on Mac. And of course, in plug-in mode you can automate all your parameters.

In standalone mode, you have additional features: audio file recording, MIDI file playback, and even the ability to render MIDI to audio directly.

Mixing, Multis:

• Load up to eight chips/instruments per instance. (Each of those, in turn, can be made up of combinations of samples.) Maximum polyphony is suggested at about 4-5 voices for artistic reasons, but… rules are made to be broken, right?
• Assignable tuning, polyphony, mix parameters
• Reverb busing
• Key switching, which allows you to change between waveforms immediately using a key on your keyboard
• Snapshots

Sound editing:

Here’s where things get fun – and where you can do things more easily than you could with the original hardware. Even with the ARIA engine alone, you have a virtual studio of tools in which to place your samples.

• Arpeggiator for pitch, velocity: with configurable range, loop modes, gate, sync, etc.
• Wave sequencer: This allows you to sequence lists of pitches on an instrument, allowing tracker-style events inside the software. (Add your own tracker to the mix and – well, things get pretty hectic.)
• Live, high-performance oscilloscope.
• Pitch LFO (currently fixed), pitch and amplitude envelope generators.
• Effects, which currently includes only an ARIA-native port of the lovely Ambience reverb by Magnus Jonsson. (But then, the advantage of having these sounds on your computer is easy access to all your other effects.)

Still Want Hardware?

In order to make the Chipsounds collection, David spent time rigging quick hardware devices allowing the actual chips to be connected to a computer. That could make Chipsounds an affordable gateway drug into building your own standalone hardware with these chips as sound sources, as I hope to do soon with my TI SN’s. To get you started, check out the superb resources on the Midibox wiki:

Midibox SID
Midibox POKEY
MIDIbox AY 3 8912

The SID is the most common of these, but ironically finding working SIDs is getting to be much harder than finding these other unique, lovely chips.

I’m actually really interested in the possibilities of combining hardware with the open-source Arduino platform and creating devices that behave in new ways; stay tuned, and hopefully we can get a group of folks working on that.

One example – our friend little-scale aka Sebastian Tomczak of South Australia – has used the Arduino to connect to the SN chip and create a MIDI-controlled Sega Master System equivalent:
MIDI + Arduino + chip on little-scale’s blog

Add in new MIDI capabilities on the Arduino, and this gets quite interesting.

The Artists

A lovely collection of artists contributed to the EP and to the development of the software, so this is very much a release connected to the community. (David’s own music is on the EP, too.)

The artists:
8Bit Weapon
Computeher
nitro2k01
Chupathingy and on MySpace
James Mireau
XC3N
shrimps

And for more on the making of one of the tracks, GameBoy Genius aka nitro2k01 has documented the work of translating a hardcore chip track from Game Boy to computer, using Renoise. This is a pretty traditional approach to what to do with chip music, but on the other hand, once you’re in the world of Renoise, you could go in other directions, as well.

If you’re interested in anything covered here – the artists, the chips and digital synthesis history, how to use the software, or how to make some of these hardware creations – all of these topics are fair game for CDM. I promise a non-nostalgic (okay, maybe slightly nostalgic), musical approach to these topics.

In the meantime, let us know what you think of the software.

I don’t know if it’s “the most revolutionary new musical instrument of the last 60 years,” but let’s be clear on one thing: the Eigenharp Alpha is utterly, beautifully insane. It combines breath and finger input in a bassoon form factor, but with quite a lot more physical control, a computer connection, and no internal sound source of its own. The breath input comes from a crooked tube as on a bassoon, with finger input in a touch strip, a fretted, light-up keyboard, and keys that have their own various forms of expression. Launched yesterday in London, the Eingenharp is getting a lot of attention. (And yes, some of you spotted signs of its launch all the way back in June, to which I say – I’m sorry I’m so late to the party.)

From BBC: Do you drum it, strum it or stroke it?

I hope to speak to the creators soon. Already, I see some indications that there are equal parts genius and madness here. The controller itself, even in the bizarre bassoon form factor, has an extraordinary amount of control, with high-resolution keys, percussion keys, elaborate control arrangements that can adjust tone or record samples, and extremely precise breath and touch. At £3,950, many computer musicians accused of “knob twiddling” by the creators probably won’t be able to afford the top-of-the-line model, but I do believe an instrument like this can easily, fairly cost this much, it’s a cost reasonable for musical instruments – and there is a £349 “Pico” edition for mortals.

There’s some madness, too, however. For the “instrument of the future,” the creators appear to have chosen MIDI, via USB, in place of a modern control protocol. Then, they plug the instrument into proprietary Mac software. (A Windows version is expected early next year.) There are software models of a Cello, a Clarinet, and a Synth, but there are also gigs of samples oddly loaded into SoundFont format. Given the futuristic ambitions and the sky-high price, closed software and antiquated I/O seem puzzling to me. I’m also skeptical of the approach here of piling on as many controllers as possible.

CORRECTION – CORRECTION! Yes, indeed – proprietary software and the limitations of MIDI wouldn’t make any sense – and apparently the creators agree. So the software will be open sourced, as will their custom-designed protocol. I’ve got all the details – required reading for anyone working on expressive instruments.

But don’t get me wrong. I think this fascinatingly bizarre instrument is worth exploring. The hardware design looks exceptionally luxurious, and there is some genuine design innovation in the controller the likes of which we’ve never seen in an instrument beyond a prototype or two.

Oh, and yes, I already want the Pico – and I think the Pico’s fewer controls may actually make more sense.

Basic specs:

Video of the key action, among others collected on YouTube:

The “Alpha,” the flagship:

• 120 keys, plus 12 percussion keys. (Wait — 120? Yes, you read that right.)
• Two strip controllers, one on each side.
• Breath pipe and mouthpiece.
• 11-bit resolution (2048 values) in the keys and strip controllers, 12-bit resolution (4098 values) for breath.
• Internal audio interface with mic pre, converters, and headphone out – so you need to carry this and a computer, but not this, a computer, and an audio interface.
• A “Base Station” with inputs for expression pedals and foot switches, which also contains the USB connection. This connects to a floor spike on which the instrument rests.

http://www.eigenlabs.com/alpha/

The Pico:

• 22 keys (18 for playing, four mode switches).
• Keys work via direct pressure and lateral pressure in both directions, as on the Alpha.
• Breath pipe.
• Strip controller.
• Same resolution: 11-bit keys, 12-bit breath.
• £349.

http://www.eigenlabs.com/pico/

To be honest, I’m quite a lot more interested in the Pico, not because I think cheaper is better, but because I’m curious whether you can’t be just as expressive with the more limited set of controls as with the kitchen sink approach of its big brother. After all, 22 keys is roughly the number you’d find on most reed instruments, including the Bassoon. True, the piano has 88 keys, but it also doesn’t really have anything else – and it’s able to have so many because of its form factor.

In fact, I’m sorry, but I love the Pico. It looks friendly, it looks portable, it isn’t terrifying-looking like the Alpha, and it seems it’d be more at home in a variety of musical venues than the Alpha. Sometimes less is more. Let’s see if I prove to be correct.

The software, though I hope you could also customize your own software rig using the MIDI input:

• Modular, allowing the routing of control inputs, sound sources and samples, loopers, and synthesis and effects.
• SoundFont oscillator.
• Physical models of the clarinet, cello.
• AU host for adding your own plug-ins. (And yes, this is where I think you’ll have the most fun.
• A system for triggering events, takes, key, and mapping scale.
• An interactive arrangement system for step sequencing.
• Oddly, an extensive Steinway D multi-sample. On the other hand, for years we’ve all have been playing bassoon and other reed samples on the keyboard, and in organ form for centuries, so now the reed instrument gets its revenge.

Source: Eigenlabs software specs.

The instrument’s creator, John Lambert, repeats the maxim heard at new instrument design conferences: “We’ve got pretty fed up with watching people twiddle knobs on stage.” Naturally, that means… turning to the Bassoonist, that sex icon of the orchestra? I’ll run with it.

One other tidbit from that article:

He says there is one high-profile musician who is about to take delivery of an Eigenharp, but won’t give any names.

Yeah, Herbie Hancock, we know it’s you. (Okay, they are an English company, so maybe it’s an English celeb, but really the question is whether Herbie is who they mean, or whether he’s filling out the pre-order as we speak. He’s like what we would all be like if we had a budget.)

Anyway, consider this a first look. I hope to get closer to the actual instrument soon.

Seeing a tracker interface for the first time can be intimidating. But dive in a bit deeper, and you’ll discover what’s actually a very efficient interface for programming in musical sequences and working with samples. With just ten days left in the Renoise – Indamixx music production contest, there’s still time to get up and running using even the demo version of Renoise (into which you can import samples). And this could be a great excuse to learn a new tool.

Dac, who’s a big part of support and community for Renoise, has put together a nice tutorial showing off the workflow in the tool. It’s nothing all that unusual: bring in samples, assemble patterns, make music. Some of the voice over is hard to hear, but this is a good start. Now, I still like reading and writing better than video just in terms of how I learn, so I may try to work on a written version for the end of the week; feel free to shout encouragement.

For more Renoise inspiration, forum regular djnick sends along a PsyTrance video made in Renoise – so, yes, you can make PsyTrance with a tracker, too, if you like. He samples Peter Jennings talking about ecstasy. Yeah, whatever – as if you can make Peter Jennings any more trippy. Watching Jennings is the ultimate natural high.

And here’s the original jerk beat tutorial. (Hey, who are you calling a jerk beat? Sorry, that just can’t sound not strange when I hear that phrase…)

Enjoy. Got specific requests for how-to’s, other tips or tutorials you’ve found useful, or questions you’d like answered? Do let us know.

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.

A monome-like grid controller built for Live, shipping in November for $199 – and I’ve got a first hands-on look with the hardware.

The feature that makes Ableton Live Ableton Live has always been its Session View, an array of Lego-like blocks of music triggering samples and patterns. In the grand tradition of the MPC, mapping hardware controls that make music non-linear has been a major theme of computer music, leading to the monome and the Tenori-On. Usually, consumer gear has only combined these with traditional drum pads, knobs, or faders.

Enter the Novation Launchpad. It’s $199. It’s a grid controller and nothing else, with a set of on/off buttons in an 8×8 array, plus additional shortcut buttons around the sides for switching modes. It’s set up out of the box to integrate with Ableton Live, but it also acts as a generic MIDI controller. It’s bus powered, really lightweight, and compact. Even following Akai’s earlier APC40 this year, there’s something special about the Launchpad: its radical simplicity, and the fact that it is this compact and cheap and plugs in via USB without power, makes this a potential no-brainer for any Live user with a laptop.

I’ve just gotten one of the first Launchpads to arrive (unit “#16″ on the back), so I’ve been playing around with it and can provide some initial impressions and details. I’ve also gotten input from Ableton’s Dave Hill as well as Novation, and I expect to fill in more soon.

monoming the sincerest form of flattery? Of course, one design more than any other championed the radical idea of a minimal grid of buttons — and nothing else. That design statement was the partially open-source, fully-homegrown monome. I’m sure as a result Novation will be accused of ripping off the monome design. I think the opposite: I think the availability of the Launchpad is a huge victory for monome, and an enormous compliment. More than any other design – including the APC40 – the Launchpad really says that an affordable, mass-market device can take on the monome’s radical form. It says grids could become ubiquitous. It’s an enormous validation of what the monome project has done. Furthermore, I think the monome community can continue to reinvent what to do with grids, with software and interaction. There are also many things the monome is – locally produced, sustainably produced, running with open source software, fully community-supported, available in kit form, working with OpenSoundControl, built in a premium form factor – that the Launchpad is not.

[edited for clarification] I think the Launchpad is unlikely to dissuade a person who wants a monome from getting a monome. But what’s significant here is that the design of musical instruments and controllers can adopt new forms. The monome was seen as radical when introduced. It seemed as though the music tech industry wouldn’t produce anything without slapping on some arbitrary knobs somewhere. The Launchpad really does follow the monome’s design cue, and maps control in Live in some new ways. That gives me hope that other designs could likewise tread in new direction, both from independent and larger designers.

Onto the details… The big picture aside, here’s a first look at how the operation of the Launchpad works. I’ll have a short video a little later on today.

Control Modes

The Launchpad has a series of modes that act allow the single 8×8 grid to perform multiple duties. Different modes and shortcuts bring up different visual feedback (by lighting up the buttons) and allow you to control different parameters.

Session mode

In Session mode, the Launchpad does exactly what Akai’s APC40 does. You can trigger clips and view clip state (playing, recording, ready, empty) by color (green, red, amber, and off). You can trigger scenes. You also get the red rectangle that highlights which bank of clips is active.

Unlike the APC40, though, the Launchpad is cheaper, smaller, thinner, lighter, and bus-powered. You can pick it up like a tablet, or squeeze it into a small club space. You can also easily chain multiple Launchpads together (or Launchpads and APC40s), so long as you have enough ports or a USB hub.

Multiple units can simultaneously access integrated control surface functions and clip triggering in Session View. So, for instance, you could have two Launchpads controlling clips, or one controlling the mixer and one controlling clips, or… you get the idea.

Mixer mode + parameter pages

Hit “mixer,” and you see an overview of all your tracks, eight at a time. (You can navigate through your set using the “page” buttons.)

Each row has a different function:

• Volume
• Pan
• Sends A + B
• Stop clips
• Track on
• Solo
• Arm

The “stop” row allows you to either stop an individual track or stop all clips by hitting the “stop” button itself on the right. Solo, arm, and track enable are self-explanatory.

Where things get a bit cooler is if you press the “snd A,” “snd B,” “pan,” and “vol” controls. These allow you to use each column to set parameters. So, for instance, if you want to adjust the send level on your second track, you’d hit “mixer,” then “snd A,” then use the second column to adjust the send up or down. You can fake a “fade” by dragging your finger up or down the column. Now, this doesn’t give you the continuous control a knob or fader would; there’s no interpolation between values. On the other hand, if you’re trying to create stepped, rhythmic changes, that could make the Launchpad (or any grid controller, including the monome) more interesting.

User mode

“User modes” provide open access to the pads for use as MIDI inputs. By default, “user 1″ sends MIDI note messages, and “user 2″ sends control change values.

In the video, you’ll see these modes used for some crazy things, like programming in a sequence and having it continue to light up as you add other layers. In my test – keeping in mind launch date is still over a month away – I couldn’t replicate any of these behaviors. Some of this interaction may require the upcoming Max for Live; I’m awaiting confirmation on details.

In the meantime, you can at least use the Launchpad as a MIDI input in Live or any other software.

Use with other software

Every single button on the Launchpad sends MIDI; I opened a MIDI Monitor session on my MacBook while testing it. There’s not a single menu key that doesn’t send a message. Also interesting: each sends both an on and an off value, which makes it more useful as a button.

It should also be possible, as with the APC40, to use MIDI to light up the Launchpad, complete with color and limited dim levels. I’m assuming the mappings may even be identical to the APC40. I don’t know yet how to do this, however.

Another big selling point for Novation, of course, is Automap support. Along the top, there are alternative labels for the buttons: learn, view, page, instrument, fx, user, and mixer. These will work with Automap and Automap Pro, in case you want to use another host or map to third-party instruments and effects. I didn’t get a chance to test this functionality yet, however.

Physical form factor

The Launchpad feels really good. It’s thin, it’s light, it’s easy to toss in a backpack (as I did today), and yet the plastic case feels very solid. The pads feel good, though I find the throw a little long, making them rock slightly if you don’t hit them dead-center. Angled pads indicate the center, and four pads around them have slight nubs on the surface for additional tactile feedback.

Rubber strips underneath the unit help grip surfaces.

One possibly unfortunate decision was to put the USB port on the side rather than the top, which means you can’t easily put two Launchpads side by side.

Software

The Launchpad ships with a copy of Ableton Live Launchpad edition (aka Live Lite), version 8.0.6. On both my Mac and Windows boxes, I simply installed that version and it automatically found my full Live license. I expect that the 8.0.6 build will get pushed to everyone else in time for launch.

You select the Launchpad as other control surfaces, by looking for “Launchpad” in the Control Surface menu. This presumably means that, like the APC40, a software handshake is used to enable the red clip selection box. I’d still like to see a universal solution from Ableton, one resizable to other controllers. Why not plug in a 4×4 drum pad and bank through clips in a 4×4 rectangle instead of an 8×8 one? The red rectangle is also limited in that it’s tough to see which tracks are selected. (It’s also kind of tough to see, period.) That’s really become an Ableton complaint, though. I’m sure we’ll be working on Max for Live and Live API solutions for heads-up displays that replace all of this soon.

Questions and Initial Impressions

I like the Launchpad a whole lot. Sure, it doesn’t have knobs or faders – but you could throw the Launchpad into your backpack alongside a KORG nanoKONTROL, using the Korg for your fader and knob tasks while the Launchpad launches clips, triggers drum pads, and gets used for live sequencing and playing instruments.

I am a little disappointed that there doesn’t seem to be a way to control Devices. I’d like to be able to take the User Mode and use my eight columns to control the eight macro knobs on any active Device. Sure, you only get 8 values of resolution, but you could set up a Device so that those eight values were musically interesting. I’m investigating whether this is possible; if not, I may look into hacking a solution.

I still think there’s a big place for open tools. The Launchpad is already touting forthcoming use with Max for Live, but that’s only because it sends MIDI messages – and anything else that can send MIDI (or OSC, via work from the Live community to use it) will do the same. I think those of us working on open interaction, though, can find ways of building stuff that works in open tools and closed tools (Java, Pd, and the like are open, Max is not), and open and closed hardware (monome, Livid’s Ohm on the open side, things like the cheap-and-light Launchpad on the proprietary side). Having lots of grids could be a good thing. If everyone has the same thing, the pressure is on to make your performance different from everyone else’s.

But the bottom line is, I think this is going to be a huge hit with the Live user base. And even more than the APC40, I think it’s cheap, an easy impulse-buy, extremely compact, and complements other hardware. It also looks like it’ll be a terrific live visual controller for people who moonlight between music and visual sets.

Since I do have this Launchpad here well over a month prior to launch, and some folks at Ableton and Novation ready to share, if you’ve got questions or concerns, please don’t be shy.

Marrying open source and commercial development, or trying to bridge analog consoles and computers – either task on its own might seem improbable. But yesterday, a newly-announced tool promised to bring together all those dimensions.

Ardour is the free and open source Digital Audio Workstation software for Linux and Mac. It’s widely underrated and has some terrific architecture underneath, with tools that are maturing at a healthy pace. Harrison is not an open-source developer – they’re a commercial manufacturer of analog and digital consoles and do proprietary DSP development. Conventional wisdom says the two shouldn’t be able to work together, but they did. The result is something called Mixbus. It’s got Harrison’s technology for mixing, atop Ardour (on Mac OS X, for now) for recording, editing, and arranging.

The Harrison half of the solution uses Harrison’s own DSP algorithms for sound, which they claim match the EQ, filtering, compression, tape saturation, and summing on their large-format mixers. But aside from sound, this is also about design: the layout only ever has one knob per function and metering is done in a conventional way. The result is not just a set of plug-ins, but a real virtual console inside your Mac. Interestingly, too, while you can use your Mac Audio Unit plug-ins with the solution, Harrison chose the open LADSPA format to implement their channel strip.

I imagined that the pricing would be something like a thousand dollars, given the pro target market, but the whole thing costs just US$79.99 as its introductory price. If it sounds anywhere near as good as the makers promise, it’s probably the best deal in mixing and channel processing anywhere. Here’s the product page:

Mixbus [Harrison Consoles]

Of course, the advantages of free software are more than price; it’s the ability to keep the source available, to be able to customize it, and to be able to run it on a variety of hardware and software platforms. So how does free software coexist here, with Ardour under a GPL license? Creator Paul Davis says that the free code for Ardour remains available in Ardour’s Subversion repository; only the Mixbus components remain closed. As for Linux support and not just Mac OS, which would in turn support more hardware, Paul says they’re looking into the feasibility of binary Linux distributions of Ardour and Mixbus.

For any commercial developers who think that you can’t work with open source projects – or, for that matter, if anyone thinks open source projects can’t benefit from collaboration with commercial developers – I think you’re wrong. And licenses aside, this looks like a nice solution for music making.

jumping beans & .tape. from la bisogno on Vimeo.

What might a jar full of Mexican jumping beans sound like if composing their own ambient music? Scott Worley points us to a musical experiment by his labelmate Daniel Romero aka .tape, on netlabel yo.yo.pang!.
.tape programmed a sound environment in the free multimedia patching environment Pd (Pure Data). Contact microphones listen for the beans to jump, then use Pd’s onset detection (an analysis for transients) to trigger the sounds. Daniel reports the technique is “easy, but wholly effective.”

I’ll say – the music winds up being quite lovely, and rather than having a boring software-based random event generator, there’s something mesmerizing about watching the beans. You can download a free MP3/OGG file of the track, as well (and it sounds as though more projects may be coming):

pet-o-matic [asociación cultural la bisogno]

Descripción original en Español:

empezamos esta serie con la picante unión entre el músico Daniel Romero (aka .tape. ) y Pancho, Emiliano y Marcos, tres frijoles saltarines mexicanos

Sonidos y programación por .tape. secuenciación en directo por los 3 frijoles saltarines mexicanos micrófono de contacto + un “onset detection” en pd para disparar los sonidos. fácil pero rotundamente efectivo.

In other Pd news, the creators of the RjDj interactive/generative iPhone music app, which employs Pd patches, will be holding another sprint. This one will be located in London October 2-4.

Musicians and artists now have the power to fuse visuals, sound, and interaction, to make a spectacle, an album, and a game all at once. But with the blank canvas of three different media before you, what form should that fusion take?

Space shooters with pounding electronic beats behind them have cleared some of the way. Now it’s ambient music’s turn. In the game Osmos, you become a mysterious particle, floating amongst gravity wells in various fields of material. By carefully navigating, applying just the right vector force to move through the shifting landscape, you merge with other particles and escape to safety.

http://www.hemispheregames.com/osmos/

The move from “shoot stuff” to “move” or “eat” seems to be rising in popularity, with games like fl0w and Spore’s initial “cell stage” encouraging nonviolent navigation. To me, there’s something happening to the zeitgeist, perhaps a renewed awareness of cosmic (micro- or macroscopic) being, and of movement that draws on free-floating physics.

Even amongst a wave of games in this mode,when you actually play Osmos, you realize that it is something different and special. The design makes ingenious use of different kinds of movement and pacing through its different modes, at one point calling upon you to hurtle around a black hole, then move at nearly imperceptible speeds through a seemingly impossible-to-traverse petri dish of massive particles. No less than a shooter, it connects to the id and survival instinct. Pac-Man, the most successful arcarde game of all time, and one of the few that sucked in men and women in equal measure, was noted for its emphasis on eating as the mechanic. Consuming stuff appeals to everyone.

Of course, this is on a music site, and with good reason: what makes Osmos work is that Osmos is musical. It’s immediately beautiful and delicate, a perfect aesthetic union of the texture of the music and the on-screen arrangements of particles. More importantly, the music is woven directly into game play, providing subtle cues for dangers, and underscoring the pace of gameplay. You can only solve a level by managing speed and motion, and the music helps provide both the literal indications of speed and help your head get into the right zone to lose yourself in the world. If blips in early arcade games helped create a zone of play trance, now we have spectacular ambient soundtrack of music by Loscil, Gas/High Skies [Microscopics], Julien Neto, and Biosphere.

The music isn’t simply a beautiful soundtrack to the game. The game really feels like an extension of the world of the music. Put it all together, and something magical happens in this $10 game: you hear the music in a new way.

I spoke to the lead designer behind the game, programmer/animator Eddy Boxerman, along with musical-sonic collaborator Mat Jarvis aka Gas aka High Skies.

Peter: I found it amusing that some of the game press have stumbled around looking for a name for a new genre here, the "eat other stuff" category. To me, the basic game controls could be traced back to early titles like Asteroids. What are the games that have inspired you, either specifically or generally?

Eddy: Some people are dubbing the gameplay type as "eat ‘em up", as opposed to the classic "shoot ‘em up". But it’s true, the physics/controls have more in common with classic games such as Asteroids and Gravitar. The only "modern" game that otherwise influenced me was Katamari Damacy. It’s funny: when I sent out the first prototype to friends, I was concerned they would think the game was too similar to Katamari. That’s when I heard about flOw, which I’ve tried to steer stylistically clear of ever since. I guess it’s an archetype though, and the comparisons have been inevitable. As for Spore, Osmos was about one year into development when I saw the first preview footage of its "cell stage". On top of that, I learned that Will Wright had hired Brian Eno to do the music! I definitely had a "why should I bother?" moment at that point. But here we are, a couple years later, and I think we’ve managed to put out a unique game with a great mix of gameplay, sound, and visuals.

Peter: Ha – well, I’m glad you “bothered”! One thing that I think is really unique about Osmos is the gravitational mechanic. How did this come about?

Eddy: I was (and probably still am) a sci-fi kid. And when I read about real phenomena like colliding galaxies, retrograde planets, and the like, my mind goes to stange and wonderful places. That said, the Spacecraft Dynamics course I took during my engineering degree definitely played a large part in putting those mechanics and levels together. Thanks, Professor Misra! :)

Peter: How are the physical mechanics of the game constructed? This is essentially two-dimensional vector math, yes? Were there refinements you needed to make in order to keep performance up, or to keep the levels playable?

Eddy: That’s a big question! But yes, essentially it’s 2D vector math, though we make use of some 3D math (including quaternions) on the particle systems. The majority of the physics is quite simple though — first year bachelor’s stuff: F = ma, conservation of mass and momentum, gravitational laws, basic time integration, etc. We follow the spirit of the laws, but not always the letter. For instance, if you look at the Earth’s solar system in its entirety, you wouldn’t even see most of the planets; that doesn’t make for a very playable game though. As such, we took many liberties when it comes to scale, constants and exponents in the equations. The majority of the work was in the tweaking of those values to make the game /feel /good.

Peter: How did you prototype the game? What was the process of evolution like? Were there any failed attempts along the way?

Eddy: I put together the first prototype starting from a NeHe OpenGL tutorial. I added some basic physics, mouse controls, some highly unoptimised collision detection code, and voila, I had something to play with. After that, I immediately integrated [cross-platform 3D audio API] OpenAL, as the game was just begging for sound and music. I then hunted for some good sounds (discovering freesound.org in the process), put together a simple looping song (my first rough and humbling attempt to create digital music), and sent it out to a few friends. I’ll make that version available for free someday… when I’m feeling brave.

As for failed attempts, there were tons of shelved experiments and features that were cut. One interesting problem was the difficulty curve of the gravitational levels. In fact, the first gravity levels looked a great deal like the "Warped Chaos" levels do today: several free-floating Attractors in a sea of regular motes. I found it incredibly difficult, however, to make a "beginner" version of those levels. If the gravity was too weak, the Attractors had little apparent effect; too strong, and the level became incredibly difficult. I stuggled with this for a long time, until I hit on the idea of putting one, immobile Attractor in the center, with everything else orbiting around it. This allowed for the creation of systems with strong gravity effects, but long-term stability. It seems so obvious now, especially given the example of our solar system, but it wasn’t back then. In the end, these are some of the coolest levels in Osmos — practically its "signature" level type. Moral of the story: necessity really is the mother of invention.

Peter: What is the visual engine like? The sound engine?

Eddy: As I mentioned, I bootstrapped from a NeHe tutorial, but that’s all been replaced at this point. It’s now a homegrown engine using OpenGL. It doesn’t make any use of pixel/vertex shaders, so it runs on a wide variety of hardware. The majority of our texture work is done in Photoshop.

[The sound engine is] a wrapper we’ve built around OpenAL. At a basic level, all we ever do is mix and adjust the gain and pitch of our sounds and music. This allows us to run on generic sound hardware. But we do make extensive use of those "effects", and it’s possible to get a great deal of variety and feedback with them. In the end, it’s all about the quality of our sound sources, and the algorithms that adjust and smooth the gain and pitch of each.

Peter: For pitch shifting, were you able to do that natively in OpenAL?

Eddy: Yes, OpenAL supports pitch shifting at the software level. I ported our sound engine to use DirectSound at one point, and found that it’s pitch shift range is rather limited. We reverted back to OpenAL.

Peter: One thing that really strikes me about the game that is its use of pacing. Even without the obvious technique of allowing the user to control speed, there’s this extraordinary contrast between levels that require you to move quickly, that require you to anticipate the rate of movement along a vector of other objects, or that require you to move almost imperceptibly slowly. Was this an early goal, or something that evolved out of developing the game concepts?

Eddy: It evolved from the game concepts themselves. We tried to fully explore the fundamental controls and game space of Osmos, and converged on a number of interesting regions and structures that were fun to play with/in. Some people actually "complain" that the pacing of the game isn’t consistent across levels — some are fast, some slow — but that wasn’t our goal. In a sense, we’re merely presenting the results of a great deal of research and exploration into the space, with our sole requirement being that the levels are fun and interesting. We wanted it to be a game of concepts and understanding, not speed. The addition of time-warping allowed us to break free from that, expand our scope, and include a much larger variety of levels, as some have both fast and slow moments in them; we wanted the player to be able to control the pace and difficulty to their level of comfort.

Peter: Connecting the action to music, how important is the use of music in conveying time?

Eddy: I think pitch-shifting the music and sound effects helps players track time-warping in an inutitive way. Without these aural cues, the mental connection would be incomplete. That said, I sometimes test the game without sound, and it’s totally playable — just much less immersive.

Peter: At what stage did you involve the musical element? How was that relationship established?

Mat: Eddy first contacted me two or three years ago about using one of my tracks on Osmos (“Gas – Discovery”). He sent me a basic alpha version where the game was literally flat circles on a plain background, but even back then with the simple graphics and no sound it was compelling. I think it was at this early stage that I sent him a copy of another High Skies track, “The Shape of Things to Come,” which he also used a section from. It wasn’t too long later that he sent me a version of Osmos with most of the music that made it to the release version and it all just complimented each other beautifully.

Eddy has done a great job choosing music that compliments the game and graphics, and they also compliment the music. I think he’s done a great job overall as well, keeping his vision consistent for the look and feel of the Osmos world. Even though some of the levels are quite varied; some are quite chilled, others fast paced, nothing seems out of place. He has created a new world that’s both microscopic and macroscopic.

Peter: The musical and sound effect elements really do blend effortlessly. Mat, I know you made substitute sounds – how did this help blend the aesthetic?

Mat: I made the rebound noise when you bounce off the walls/ boundary. The original sound was quite hard and metallic with a lot of reverb, and I suggested a softer echoey sound. There was nothing wrong with the original, but it made the boundary feel quite hard and cold like being in a metal tank. I sent Eddy some analogue samples, using a [vintage Roland keyboard] Jupiter 6 with varying delays/ echoes. Because the tones are so pure and tuned, Eddy pitched them slightly to fit with the various keys of the different music.

Eddy: In general, it was a matter of searching and experimentation for the "right" set of sounds that fit well together — which can be a lengthy but rewarding process. Once integrated, minor gain and pitch adjustments helped fit it all together.

Mat provided the bounce sound, as well as the continuous absorb/being-absorbed sounds. The other sounds were created/shared on freesound by the users Elektrocell, fran_ky and Jovica. (Check out the Osmos credits in the readme.html for details.)

Peter: I recently spoke to Crystal Method, and while they’ve done some notable game scores, they actually said they wouldn’t want their music to be placed in a game context at which the speed changed, that it’d lose something. This seems like the opposite of that. Now, maybe it’s easy to take for granted with ambient music as opposed to something beat-driven like Crystal Method, but do you think there’s something special that allows this music to be adaptive in that way?

Mat: I think that in the right circumstances music with drums could work well and may even highlight the time-shifting more. Of course with the wrong game and wrong music it could sound terrible too.

Eddy: It’s a delicate issue. Out of the context of the game, I think it would seem wrong. There were also some pieces of music I tried which didn’t lend themselves well to this kind of manipulation, and which didn’t get included as a result. But with these songs, and everything working together in-game, I feel the whole experience is stronger as a result. I’m just glad Mat and the other artists agreed — or at least… didn’t object. ;-)

Peter: Hey, I think if you can write music that sounds good played at a different speed, that’s nice.

Osmos seems to me a musical experience, in that the sense of the music is transformed by the visuals and the interaction with them. Do you think it’s possible that audiovisual interfaces could go even further in terms of their impact on the music?

Mat: Yes, it almost seems as though Osmos creates a world for the music to exist.

I’ve always liked music visualisers like the Processing and Cymatics stuff, they’re quite compelling to watch how they react to the music, so it would be interesting to go the other way; by manipulating/ sculpting abstract shapes which then modify or even create sounds and music, especially using the new controllers like the Wii, [Microsoft’s] Project Natal and Sony’s Motion Controller instead of the mouse.

Eddy: I totally agree with Mat. Yes, please! More feedback between music, visuals and interactivity — in all directions. I’d love to experiment more on all of these fronts. In general, I think games such as Audiosurf and Auditorium, while great, have only begun to scratch the surface of what’s possible. Interactive musical "toys" such as [Nintendo/Toshio Iwai’s ]ElectroPlankton or Dub Selector are another great direction; and Rock Band Network is about to expand the market in a huge way. It’s exciting!

Peter: Along those lines, this is obviously a new take on music distribution in a way that goes well beyond what titles like Rock Band have done. Are there other cases in game history that to you have done that? Is there potential in these new outlets, outlets that are more accessible to independent developers (Steam, Direct2Drive, Xbox Live Arcade, iTunes App Store), to really change game development?

Eddy: Wow, that’s another big question. Really, I just felt the music was such an important part of the experience in Osmos that we should show the artist and track names during the game. But now that you mention it, I can’t think of another game that has done this, besides games like Rock Band where the song /is/ the game/level. That said, one way I’d love to push this evolution is to "augment" music videos with interactivity: ie. into music video-games. (The term "game" could be used rather loosely here.) Everyday Shooter does this, though Jon Mak actually created the music /for/ the game in that case — which rocks — but collaborations could lead to some really amazing things in this direction.

Peter: Eddy, Mat, thank you. Whether it’s in the form of a game or an audiovisual performance, we’ll certainly continue to explore these areas. And – hint, hint – Osmos 2, with multiplayer? Just a thought.

Osmos Trailer from hemisphere games on Vimeo.

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.