“Studio” for many of us means packing musical production tools into a corner of our desk, then being able to fit the whole thing into a backpack and take it with us. It’s bringing along your entire production to a cramped rehearsal room and adjusting tracks in a hotel room. It’s putting together an assortment of unusual pieces of DIY hardware, mobile game systems and an iPod touch, and composing and performing a live PA set. So packing in functionality means a lot.

That makes it worth considering a hardware solution like Cakewalk’s V-Studio 100 in obsessive detail. Combining an interface with mixing, control, recording, and software functions makes the VS especially relevant to the computer musician.

I was one of the first people outside Cakewalk to lay eyes on the V-Studio 100. Part of the initial appeal to me was that it seemed to combine a lot of the tools I wanted into a single package.

Sure, its big brother, the V-Studio 700, is an impressive unit with loads of onboard options. But the V-Studio 100 was more my speed: it has that apartment studio, backpack-friendly attitude. And don’t let the “SONAR” in “SONAR V-Studio 100” fool you, either. While it’s great having a free copy of a special edition of SONAR on Windows you can use the VS hardware and even the plug-in bundle that comes with it on any host on either Windows or Mac. And — oh, yeah – you can also make use of all that audio I/O and mixing to do some crazy stuff with your plugged-in portable game  consoles and iPhones and homebrewed electronics.

The real test is whether this one unit can perform the tasks you need. The V-Studio 100 tries to be a number of different things:

• An audio interface (up to 24-bit/96 kHz)
• A mixer
• A control surface
• A wave recorder
• A software bundle

Correction: The street price of the whole package is US$699. (I had incorrectly put the street at $800 instead of $700!)

Anything that does that much will naturally have to make some compromises. Some of those compromises I think are rather well-conceived on the VS, while others I hope will evolve over time.

This will be partially a review, but partially a description of what it’s like using the VS, so if you do have one of these, I can hopefully give you a sense of how to begin using it.

What’s in the Package

The VS-100 itself is a tidy rectangular box with the main two audio ins on the front, USB, MIDI, and remaining audio I/O on the back, and mixer controls, menu, transport controls, control surface shortcuts, and flying motorized fader on the top. The unit feels terrifically solid, both in overall feel and the details of all of the controls. I wish it came with a carry case, but it’s the right size to fit a lot of generic gear cases out there. Documentation includes a Getting Started Guide, Hardware Manual, and two discs. One disc contains the SONAR V-Studio for Windows, a special edition of the SONAR DAW, plus a big bundle of plug-ins that will work with either Windows VST or Mac Audio Unit hosts. The other disc ships with drivers that work on both Mac and Windows. (In other words, Mac users miss out only on the free SONAR VS – not a deal-killer since you probably have a copy of GarageBand or another DAW, anyway.)

The whole unit weighs just over four pounds and can easily fit into a compartment in your laptop backpack or larger briefcase. You do need its power source – because of the pres, motorized fader, and mixer functions, this is just too power thirsty to draw all its electricity from USB – but the 9V power adapter is relatively compact.

Audio Interface

The VS-100 is a 10-in, 6-out interface. Of course, that’s actually relatively modest for interfaces of this price range. At the same time, those interfaces are just interfaces, the quality here I think is really good, and this could be a pretty practical set relative to what many people actually need.

Here’s the basic configuration:

Inputs 1-2: XLR mic jacks and balanced TRS 1/4” jacks. Input 1 has a Hi-Z (high impedance”) switch that switches to a 500 k ohm impedence for guitars. There are also mic preamps on both 1 and 2. There are also physical knobs on the front of the unit for adjusting input sensitivity of 1-2.

A phantom power switch is located on the back of the unit for mics that need power.

Inputs 3-4: Dedicated mono TRS jacks (balanced).

Inputs 5-6: Stereo phono pair (unbalanced).

Input 7-8: Digital S/PDIF input on the back. (Input only; there are no digital outs.)

Input 9-10: The mixer output can be selected as a separate two ins.

Outputs 1-4: Four channels of balanced TRS 1/4” output. Can you say quad sound, anyone? (Hey, it’s actually the most practical option for live performance.)

Outputs 5-6: Unbalanced stereo output.

You do get 1-in, 1-out MIDI, accompanied by Cakewalk/Roland MIDI drivers, which traditionally have given me good results on both Mac and Windows.

The mic pres on inputs one and two sound really transparent, much higher-quality than I would have expected, and the one indication that Cakewalk and Roland aren’t thinking of this as just an entry-level unit.

For the one-man/one-man performer, it’s a pretty ideal configuration, it’s great having unbalanced I/O, it sounds good, and you have dedicated level knobs where you need them. I’ve played out with the VS, and it’s an ideal solo computer audio interface.

Even given that, you probably wouldn’t buy this box for its audio alone. You could get a MOTU Traveler, for instance, with FireWire audio, lots of additional analog and digital I/O, more pres, and internal mixing capability. But it’s the other features that make it a contender.

Mixer Operation, Interface Operation

The VS adds to its interface mixing functions and a built-in set of effects. And note that on the mixer side, this isn’t a “software” mixer as you provided by some of the VS’ competition. You get a compact but very functional set of hardware controls that allow the VS to handle mixing functions, even when you’re also using it as an audio interface, and even when you’re in cramped spaces.

On the effects side, the VS includes a dedicated compressor and 3-band EQ for tracks 1-6 (as inserts on 1, 2, 3/4, and 5/6). Via some cleverly economic menus, you can edit parameters for these settings using the toggle buttons above the mixer knobs, in conjunction with three dedicated encoders and the value knob. It’s not hard to get the hang of toggling around, and while you don’t have dedicated controls as you might on a full-blown mixer, functions are rarely more than a button press or two away.

While it’s a bit harder to get to, there’s also a decent-sounding internal reverb included, as well. It has specific sends for each channel (1, 2, 3/4, 5/6) and adjustable send level, though you’re hard-wired to some basic modes (ECHO, ROOM, SMALL HALL, and LARGE HALL).

Quick tip: Hidden in the settings is the ability to route audio to your USB port pre-EQ. (Look for Menu > Utility > To USB > PreEQ.) Generally, recording with in-line EQ is a very bad idea, because there’s no way to go back to the raw audio. With this setting adjusted, you can use EQ for live performance but without impacting your raw tracks if you want to master, say, a live session later on.

The VS-100 can operate both as a standalone mixer – something you’d take to your gig while leaving the laptop at home – and a combination between a mixer and an audio interface. Because of that, its operation is a little different, so let’s actually walk through the signal flow itself.

Navigating Signal Flow

Scenario 1: You’ve got the VS plugged into your computer.

You might plug a guitar into input 1, depressing the Hi-Z switch, and a mic into input 2.. You can then adjust input level on the “SENS” knobs on the front. There’s no dedicated LED level meter, but you do get a level meter on the LED screen on the top of the unit.

Monitoring is a little different than on most audio interfaces. You have two places at which you control the level you hear. The “MAIN MIX” knob controls the level for the mixer – which is also your zero-latency, direct monitor level, the level from your input before it reaches the computer. For the output from your computer, you would adjust the “PLAYBACK” knob.

The advantages of working this way: you can use this as either a traditional interface, or as a mixer – handy with multiple ins plugged in. And you get dedicated knobs for 1, 2, 3/4, 5/6, and (the digital ins) 7/8 for use in mixer mode. You can also feed the main mix out to a PA, so for live performance you can keep a mix going to your audience without carrying along a separate mixer.

Embarassing side note: In my haste, I initially assumed the “PLAYBACK” knob controlled only the flash Wave Recorder. It actually controls playback of your audio interface through the main outs when you’re in USB mode. You’ll, um, want to turn that knob down before you plug in the unit, as the outs are pretty hot. You can imagine what happened to me. Happily, my monitors survived. Oh, PS – Cakewalk actually should have put that in their manual, as there is a prominent warning about the “MAIN MIX” knob, but not “PLAYBACK” – and this is called SONAR V-Studio, so they should expect people will be connecting it to the computer straight away!

Scenario 2: You’ve got the VS operating standalone.

The mixer functions are pretty self-explanatory. In this mode, the Wave Recorder can record from your main mix, it can play back tracks, and it has loop playback. The ins and outs work otherwise as they would in DAW mode, and you still get the built-in effects. The one downside in this mode is that the DAW controls – the shortcut keys, track select buttons, and flying fader – are all basically meaningless. It’s too bad that they couldn’t do some sort of double duty. But it’s still nice to have this box as a mixer and effects unit on the go. There’s even a metronome feature, so it could be a decent box to carry around to rehearsal with you, especially with the built-in Wave Recorder, if you don’t already own such a unit and just want to budget for the VS alone.

Scenario 3: Disaster strikes.

Here’s the best thing about having two modes: try yanking out the USB port while the VS is plugged in. Normally, that’s a very, very bad idea (and it’d be an especially bad idea when using FireWire, as you could theoretically fry your computer or interface). But with the VS, the hardware will automatically switch its routing to the wave recorder, and the mixer will continue operating normally.

In other words, you can have a cable come unplugged or a computer crash and save a gig by keeping sound going on the VS. With WAV playback on the WAV Recorder, you could even switch over to a flash card for backing tracks.

The Control Surface

At its simplest, the control surface gives you just the basics: transport controls, mute/solo, and arm, plus the main feature – a motorized flying fader. Of course, in a lot of situations, that’s exactly what you need for basic recording. In fact, thanks to the fact that the fader is motorized, you may not need other faders, given that most mixing scenarios involve adjusting just one track at a time. (Riding more than one fader can tend to cause you to overcompensate when fine-tuning levels, a bit like oversteering.)

The track select keys toggle tracks. (It doesn’t matter which track is selected in software, even in SONAR.) Using the shift key navigates buses (SONAR only). The value knob can also be used for additional manipulation.

Transport keys can move not only the transport but, using the shift key, from marker to marker.

For those of you who have managed to escape the experience in real production, using motorized faders is a joy. The fader will near-silently shift to whatever setting you choose. I remember using Digidesign’s motorized faders when they first came out and finding the effect almost magical, though in those days the technology was priced as high as a compact car and the faders moved with a little “thump” sound. Happily, technology marches forward.

In ACT (Active Controller Technology) mode, Cakewalk maps its own SONAR software more intelligently. By default, this includes the Value encoder and the three encoders below the LCD, so that if you, say, bring up an instance of one of the included Studio Instruments, software parameters automatically map to those hardware controls. It does make quickly accessing basic settings a little quicker, though if you’re a heavy synth user, this functionality is unlikely to compete with similar and more advanced  “automatic map” controllers and software like Native Instruments’ Kore, Novation’s ReMOTE line with Automap, and M-Audio’s Axiom Pro with HyperControl, or Cakewalk’s own ACT in combination with a range of hardware. There just aren’t enough controls on the VS, by contrast. In a pinch, though, ACT is still useful on the VS, especially if you enable the “DAW Full Asgn” setting in the menu. It automatically maps the mixer knobs for use with ACT, too.

Unlike technologies like HyperControl and Automap, ACT is limited to SONAR, but SONAR users, I think you will find yourself using it at least a little, just because it’s there. My one criticism would be that it’d be great if there were a keyboard shortcut for switching to “Full Assignment” mode without digging through menus. That way, you could easily toggle between using mixer controls for mixing and using them for ACT.

Confused by all these options? Given that all these technologies rely on MIDI, anyway, I think we badly need an open spec that allows you to easily support any host with any hardware, without the fuss. Someone out there adept at Reaper scripting, for instance, I’d love to hack into this.

What if you don’t use SONAR? Mackie Control Support

You can still get basic control with V-Studio using Mackie Control. It’s just as easy to set up: choose Mackie Control as your control surface, then select the V-STUDIO CONTROL port as your input and output. In software like Ableton Live, Apple Logic, Reaper, and others, the VS will automatically map to basic mixing functions. Transport controls work perfectly, the motorized fader jumps to the right level, and mute/solo/arm buttons work. I tried it in a number of apps and had no problem.

There is one catch: because of some of the limitations of Mackie Control, you don’t get to use those extra knobs. While Full Assignment mode remaps all the controls to MIDI and should allow you to manually create your own MIDI maps for your favorite software, it also enables ACT mode. That means that you lose all the functionality of Mackie Control if you turn it on. You can have one or the other, but not both.

It’d be nice to see Cakewalk modify the functionality of Full Assignment mode so that it can coexist with Mackie Control. That way, you could use the rest of the control surface as a MIDI control surface rather than losing the functionality of those controls. It’s a subtle point; as I said, I think people will use the transport and mixer controls far more than synth controls because of their relative convenience. But it would make a nice firmware upgrade.

Speaking of firmware upgrades, make sure you’ve upgraded to at least 1.19 firmware before attempting to use Mackie Control. This release fixed a number of bugs, including one that prevented me from switching to the “OTHER” DAW mode (from SONAR.) Once I updated, though, this performance was seamless.

The Wave Recorder

One of the reasons you might want to drop the VS in your gig bag is that it combines a mixer with a wave recorder in one box, and can replace a computer or a mixer+recorder combination. Pop in an SD card or SDHC card – capacities up to 32GB via SDHC – and you can record the stereo mix of whatever is plugged into the mixer. The Wave Recorder also supports easily-accessible playback, which could make the VS ideal for backing tracks. You could, for instance, use it in its computer interface mode in the studio for production, then load all your tracks onto SD and play them back onstage with the VS running as a mixer. Alternatively, you could record a mixed-down rehearsal or performance and take it home with you.

Like Roland’s mobile recorders, you also get basic marker and looping functionality, which could help you practice or transcribe a tricky portion of a song or create more sophisticated backing arrangements if you were feeling especially ambitious.

True, you could bring along a mobile wave recorder, but the convenience of combining the recorder with mixing functions makes it ideal in cases when a portable stereo recorder is not.

There’s one major caveat, however. Playback from the wave recorder and recording of the stereo mix are both possible when the VS is operating in standalone mode. But when it’s connected via USB, each of those functions is defeated – no playback, and no recording. The transport controls are reassigned to become software control surface functions, and the SD card slot becomes useless. That’s too bad, as one of the first things I wanted to do with the VS was to be able to record live sessions without relying on my computer hard disk, recording the same live mix I’d feed to the PA.

I was able to confirm with Cakewalk that Roland is aware of this limitation and investigating possible solutions; it may be technically possible to resolve the issue with a future firmware update. They were not able to confirm at this time when a fix was coming or what form it might take, but I’ll provide updated information if it becomes available.

In the meantime, it can still be useful to have the VS wave recording function, as it does mean you can leave the laptop at home for various recording and practice scenarios.

Driver Support

As with previous Roland/Cakewalk outings like the SONAR Power Studio, the VS-100 comes with extensive documentation on how to tweak driver settings under Windows, and you can expect extremely up-to-date and reliable support for Windows technologies, including the WASAPI adjustments made in Windows Vista. (WASAPI is Windows’ general audio interface for software; it’s supported on the software side by applications like SONAR, but it’s essential that hardware driver implementation be robust in order to acheive proper support under Windows. Translation: Cakewalk gets their drivers right, so Windows works properly and you don’t have to worry about it.)

Installation on Windows winds up being pretty easy. Install the driver disc to get up and running. Install a second disc, and you install a huge suite of plug-ins as well as the special edition SONAR VS software. The bundle installed over my existing Cakewalk SONAR Producer Installation just fine, and then the newly-installed effects became available not only to SONAR VS, but my existing SONAR install, too, as well as all my other VST-compatible DAWs (like Live and Reaper).

The Mac installation winds up being easy, too, however. The Mac version fully supports Core Audio, and I got excellent performance in Logic Studio 9. Logic also mapped easily to Mackie Control.

Bundled Software Gems

The VS Production Pack includes a set of effects and instruments for both Mac and Windows:

• VX-64 Vocal Strip – a combination deesser + “compander” (compressor/expander) + tube-emulating EQ + Doubler + synced Delay. That could have been a bunch of gimmicks. But it winds up being all awesome.
• Native Instruments Guitar Rig LE
• Boost 11 Peak Limiter – actually a pretty decent and relatively transparent limiter
• Channel Tools – a set of channel utilities for enable/disable/swap L/R channels, adjusting stereo and mid-side mode, and adding delay.
• LE versions of Dimension (sampler), Rapture (synth)
• Studio Instruments Bass, Drums, Electric Piano, Strings: all some very lovely-sounding, lovely-looking instruments

Bundling light-edition software with hardware is a popular choice, but the VX-64 is the real stand-out. The set of tools integrate beautifully, there’s a fantastic live spectrograph tool for a view of what you’re doing on each of the modules, there’s a lovely drag-and-drop routing interface, the UI is clear and well laid out, and the whole think sounds utterly wonderful. I don’t think it’d be hyperbolic to say the VX-64 is the best software plug-in Cakewalk has made yet; it just packs in all the goodness you might like for vocals in a single window.

There are enough unique capabilities here that, even if you have a collection of plugs or a DAW with lots in it from a rival maker like Ableton’s Live Suite or Apple’s Logic Studio, you’ll find something useful. The danger to all of this is that there’s a sort of kitchen sink feel to the suite, and it could well overwhelm beginners, but the VS generally feels better suited to intermediate-to-advanced users, anyway.

SONAR VS

The sleeper hit of the whole package is the VS edition of SONAR. Usually I like light editions of DAWs about as much as I like diet soda – it’s just not as sweet as the real thing. But the VS is a pleasant surprise. It feels a bit like GarageBand for grown-ups. One of the complaints about SONAR from non-converts is that its do-everything user interface can feel cluttered, particularly by providing lots of different routes to the same thing. I think that’s a fair criticism, even as I respect what SONAR does.

What’s remarkable about SONAR VS is that it feels like it sacrifices none of the functionality of its big brother, but wraps it into a much cleaner interface. Channel strip pop-ups on the left allow easy access to every parameter. A reduced toolbar icon provides essentials without being overwhelming. There are still some hard-to-read icons, and the software is likely to, again, be a bit complex for beginners. But for users with some experience, there’s a real sense that tools and options have been thoughtfully chosen.

All of this may be overkill for those of you loyal to an existing DAW, but it’s still worth noting the job Cakewalk has done. Of course, the message to Cakewalk should be clear: SONAR itself needs a window layout that’s this clear, either as the default or something you can switch on easily.

Note that you actually don’t need SONAR VS to get any special integration with the V-STUDIO 100 hardware and drivers. Driver setup is the same for SONAR VS as SONAR; it takes a few steps but in either tool, you get excellent driver support, and I don’t think there’s any question that Cakewalk’s support on Windows is exceptional – enough so that Windows really isn’t a hassle.

Conclusions

The VS hardware brings together something I’ve been waiting for in hardware for a long time. It’s beautifully compact, too – but, naturally, that means it also has to make some trade-offs to put together so many elements in one package. It’s simply worth considering if it’s the right set of trade-offs for you.

The good:

• The unit is physically lovely to work with, in terms of its layout and feel.
• The pre’s sound great, and while the audio I/O isn’t as extensive as on some interfaces, it’s practical for a lot of real-world, one-person, mobile producer situations.
• Using the motorized fader is addictive, and works in any Windows/Mac software.
• The control layout winds up being very usable, and it’s nice having compressor/EQ instances within easy reach.
• You get rock-solid Roland audio and MIDI drivers (particularly important on Windows).
• SONAR VS is actually a great little audio package.
• The VX-64 is a real gem for anyone working with vocals, and overall the software bundle is a terrific value.

The mixed:

• The WAV recorder gets defeated when you plug in a USB cable.
• The VS would be more useful as a control surface if you could more easily map the rest of the surface to MIDI – without having to use SONAR and without having to defeat Mackie Control.
• The ACT controls can be a little confusing on such a compact control surface.
• Even with those two great pre’s, the VS probably won’t be your first choice if what you really want is just an audio interface.

Despite some weaknesses, though, to me the VS’ strong points are what can make it a terrific choice. A remarkably compact mixer combined with the flying fader and transport control and the audio I/O you’re most likely to need? That could be enough to sell you, before you add in additional value from some of the software gems that come with it.

At US$699 street, there are cheaper options around, but by the time you add a control surface, a mobile recorder, a mixer, and an audio interface together, it’s a different picture. There are also other control surface-mixer-interfaces out there, but some skimp on audio quality while others lack the VS’ elegant compactness.

The VS still counts as the most control, mixing, and audio functionality I’ve seen in any backpack-friendly box. And as such, for the laptop music production warrior wanting to maximize space and power, it’s part of a handful of essential gear to consider.

Cakewalk V-Studio 100 Minisite

For another review of this unit, check out this post from Boing Boing Gadget’s excellent Rob Beschizza. And Rob takes some really gorgeous photos of the VS, too.
A Weekend with Cakewalk’s SONAR V-Studio 100 [boing boing gadgets]

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.

Getting handy with the $60 KORG Nano Series controllers and Ableton Live keeps getting more sophisticated. I did a "quick hack" using the text-based MIDI Remote Scripts with the nano as an example, and provided a download. Next, Raymond Weitekamp modified those scripts and added a monome for a full-blown Live performance. But now James Waterworth aka Myralfur takes the whole idea to the next level, with a fully custom set of scripts with control of additional channels, more control over tracks, and most importantly, interactive scene triggers.

I’ve built a custom python script for the nanoKontrol based on the hacked python scripts for the Axiom controller decompyled from live 7. It adds the ability to switch up to controlling channels 9-16 by changing midi channel (or changing up to scene 2 on the nanokontrol, which I had sending out on midi channel 2 instead of 1). It also has track on/off, solo/cue, panning, and also has the bottom row of buttons triggering clips on the relevant track, with forward and reverse skipping up and down scenes, and the loop button triggering the selected scene.

Best of all, you really don’t need to know – ahem – what you’re doing with scripting to make this work. Just follow the instructions below, and you’re ready to play – so you can get back to your set.

Now, James has polished off the script and fixed compatibility with Ableton Live 8, and this is ready for public testing. Give it a go and let us know what you think. I’ll work on a permanent home for all of this stuff, but for now, let’s just use comments for any issues. For some insane sounds, be sure to check out Myralfur’s music and DJ mixes on Soundcloud, too! He’s working on a rig that also incorporates a Sony PlayStation 3 controller.

nanoKONTROLMyr

A midi remote script for use with Ableton Live 8 and the Korg nanoKontrol.

Set-Up

1. Download and Unzip the file.

2. Move the nanoKONTROLMyr folder to the MidiRemoteScript folder within your Ableton Live application folder.

3. Open your Korg nano series editor and load the presets within the NanoKontrol Presets folder, over-writing your previous settings.

4. Select nanoKONTROLMyr as a control surface in the midi pane of the preferences window.

Mappings

Banks

Bank 1 controls tracks 1 – 8

Bank 2 controls tracks 9 – 16

Bank 3 maps the encoders to the selected device and provides functions for moving tracks and devices.

Bank 4 is free for mapping to whatever you like, sending on midi channel 4.

Global

The Ninth Slider is Always mapped to Master Volume, regardless of bank or midi channel.

The Ninth Encoder is Always mapped to Cue Volume, regardless of bank or midi channel.

Transport

Transport functions only work when receiving midi cc numbers on channel 16.

Different functions are called when in session view and arranger view for some of the buttons. The Loop button acts as a Shift to allow more functions to be called with the other transport buttons.

Loop = Shift

Play = Play (Scene Launch when Shift held)

Stop = Stop (Stop All Clips when Shift held)

Record = Record (Overdub On/Off when Shift held)

Session Specific

Rewind = Scene Up (Scene Up by 5 when Shift held)

Forward = Scene Down (Scene Down by 5 when Shift held)

Arranger Specific

Rewind = Cue Position Left

Forward = Cue Position Right

Encoders

The Encoders map to the Pans of the tracks. When sent on different midi channel numbers they map to different tracks. Channel 1 maps to tracks 1 – 8 and Channel 2 maps to 9 – 16 etc.

When sent on midi channel 16 they map to the selected device. This works in conjunction with the pads and buttons sending on channel 16 which provide functions for moving track and controlling devices.

Sliders

The Sliders map to the Volumes of the tracks. The tracks they are mapped to changes with the midi channel they are sent on. Channel 1 maps to tracks 1 – 8 and Channel 2 maps to 9 – 16 etc.

There is as yet no function for when they are sent on channel 16.

Top Row of Buttons

The buttons on the top row turn Tracks On/Off. The Ninth Button on the row acts as a Shift and when this is held the other buttons Record Arm the tracks. They function the same as the sliders and encoders in that they map to tracks depending on the midi channel.

However, when sent on midi channel 16 the buttons select and view tracks 1 – 8 mapping the encoders above to the first device in that track.

Bottom Row of Bottons/Pads

The buttons, or pads, on the bottom row Trigger Clips. The Ninth Button on the row acts as a Shift and when this is held the other buttons Stop the relevant clips. They function the same as the sliders, encoders and top row of buttons in that they map to tracks depending on the midi channel.

However, when sent on midi channel 16 the buttons provide various functions for controlling devices.

Button 10 = Track Left

Button 11 = Track Right

Button 12 = Device Left

Button 13 = Device Right

Button 14 = Bank 1

Button 15 = Bank 2

Button 16 = Device On/Off

Button 17 = Clip View/Device View

Download:

nanoKONTROLMyr.zip

For many, mobile technology and developing for the iPhone and the iPod touch is a fad and a Gold Rush. Good designers, though, take a longer view of how interaction can be expressive. And there are few people with a better sense of the big picture of small devices than Dr. Ge Wang. The co-founder, CTO, and Chief Creative Officer of Smule has a background that goes well beyond the latest Apple platform. Along with Perry Cook at Princeton, Ge Wang is the co-originator of ChucK, a real-time programming language for synthesis so efficient some people use it live onstage. (ChucK, as an open source project, now has a terrific team of people behind it.) ChucK is the sonic engine that powers Smule’s projects. Ge Wang also teaches at Stanford, working with students and fellow researchers to explore new ways of interacting with music technology.

Ge Wang joined me for a lengthy phone conversation recently. He really contextualized why the iPhone is important in the grand scheme of things, but also how the people at Smule and Stanford (and Princeton) can approach technology for musical interaction, focusing on what devices are rather than what they’re not.

(The audio here, believe it or not, is extensively edited – Ge Wang is that easy to talk to. I hope the next time it’s over beers rather than Skype.)

The full interview can be played below, or downloaded directly.

Download MP3 of the interview

Thanks to KORG and the Nano Series for their support of programming on createdigitalmusic.com.

Lastly: a video of the Smule team headquarters and playing around with Leaf Trombone for a Zelda duet!

More information:
The Mule Chronicles [Smule Blog]
http://smule.com/
Center for Computer Research in Music and Acoustics (CCRMA), Stanford University

Previously, for more on Ge Wang and CCRMA:
Make:TV Meets Stanford Musical Inventors, Feedback Piano

Video + Audio Subscriptions, iTunes Podcast

CDM is now launching regular audio content on the artists and inventors we cover as part of our series CDM Sounds. You can subscribe (and review the podcast) via iTunes, where you’ll also find our new video series:

cdm Sounds Podcast [audio]
cdm TV [video]

Or using your software of choice, subscribe directly to RSS. (I like to follow podcasts with Banshee and Winamp this way.)

We’ve fixed some transcoding issues for iPod touch/iPhone on the video podcast. Please do test this and let us know if you have any issues on your software/hardware.

Defining and re-imagining performance with computers and technology is an ongoing theme of this site. In a special guest column, artist Primus Luta goes deeper into that question with some of our favorite artists to look at practical and philosophical dimensions of playing electronics.

Today, the fruits of electronic musical labor can be heard in every corner of culture, from academic to niche to popular. Still, there remains a perceptual disconnect between traditional and electronic music, especially in the context of performance. With traditional instruments, performance proficiency can be measured as a physical accomplishment. Electronic performance, on the other hand, is generally understood as music made by computers. That poses a question: if the music is being made by the machines, what exactly does the musician do? To find out, I talked with some of the best electronic performers on the road, and got a glimpse of what exactly is going on behind the screen.

Live Rig: Mark de Clive-Lowe

From the Studio to the Stage

Historically, performance long preceded recorded music. Early recordings weren’t what we think of today as studio productions, but rather recordings of performances. Electronic music is a bit of an anomaly. While some early electronic compositions were created for live performance, most electronic music today begins with a recording.

Translating the high production values heard on a record into a live performance isn’t an easy task. It isn’t always possible to recreate the same aesthetic on stage, but it is important to make the connection.

“We can multi-track sounds in the studio,” explains 8 Bit Weapon, “but live, you are stuck with all the limitations the vintage computers, consoles and sound chips have to offer. So we have to trim down parts or add parts that are recorded by recreating them live.”

For Richard Devine, assembling the live performance begins in the studio with “trying to translate all the programmed MIDI data and song transitions into Ableton [Live]. Ableton is running the pieces of my tracks. I have hundreds of audio clips running in session view.” Onstage, this allows Devine to “mix and match breaks, intros, or builds for different tracks, and even manipulate how those are played if I select them. I can really do anything with the arrangement of the original track. It is now total remixing and producing on the fly.”

What this means for electronic performance is the ability to condense what could be days of production work into a performance piece of a few minutes. “It’s really similar to my studio process, on fast-forward!” says Mark de Clive-Lowe.

“We create tracks in the studio in the normal fashion,” says J Tonal of The Flying Skulls. “They get broken up in to drum and bass parts, which get played live on the MPC, melody and lead parts which get played on the MS2000, and samples and other melody parts which get broken down into [Ableton] Live clips and played from [an M-Audio] Trigger Finger.” These pieces are then used live to create what they call deconstruxions.

As Mark de Clive-Lowe explains, “the idea of reinterpreting and translating the same pieces to different audiences with different bands and setups is nothing new.” In other words, rearranging electronic music for performance contexts does have its roots in a larger musical tradition.

For some, this has resulted in working to restore the historical role of performance as the heart of a recording. “The experience of participating in a musical happening is ephemeral and never translates to a record,” says Tim Exile. “I have developed a number of paths of improvisation which you could consider scores… these are adaptive positive feedback responses to features of the musical environments I’ve been in. These features can be very local, such as the slight manufacturing error in one of the buttons on the control surfaces causing it to be slightly harder to hit to be sure of pressing it, to the very wide, such as the proliferation of a new genre changing the way audiences categorize and respond to certain musical structures.”

This interplay of the studio and performance feeds the creative loop to take a new shape each time the artist goes on stage. “Most of my studio output is mellow,” says Daedelus. “Most performances are riotous or at least dance-able. So finding relationships and movement in my own output is quite fun, and leads to disaster in the best nights.”

Is It Live Or Memorex?

When it comes to electronic music performance, is the music is being performed or played? As technology like Ableton Live evolves, the line between the two may blur to the point of irrelevance. As Tim Exile explains, “the discussion lies more in the boundaries between performance of compositions and improvisation. Most of what I see being played live these days seems of the live arrangement variation, focusing mostly on compression or expansion of set arrangements in response to the environment. This is live and adaptive and of the same genus as the style of performance exercised in DJing.”

Whatever the prepared sources, this adaptive style is undeniably a performance. “I can’t always reproduce the same exact show twice now,” says Richard Devine. “There are now so many different variables that can change or be manipulated.”

“I employ a lot of pre-made loops,” says Daedlus. “In some regards the legos are in a large box and I try to make spaceships or castles accordingly.”

“There are a lot of our songs that have a prerecorded studio version,” says J Tonal. “That gets played for about two minutes, and then we switch it up into a deconstruction and play a live remixed version of the same song.” Over top of backing tracks from their songs, Seth and Michelle of 8 Bit Weapon “play the Commodore 64 and 128 live like pianos, and use the Apple IIc as a mono synth in the same fashion. The Game Boy can do very basic live sounds and sequences.”

The Nucleus

At the center of any musical performance is the instrument. For electronic music, that instrument is the live rig. That rig can be a single laptop or an intricate hybrid of hardware and software; the possible configurations are limitless. Combining controllers, sound sources, mixing, and effects determines the breadth of available sound. The shape the rig takes becomes the defining point for the artist.

No matter how large, most rigs contain a center – a nucleus from which the soundscape is derived. For Daedelus that nucleus is the monome. “My preoccupation is with the Monome,” he explains, “especially MLR and added goodies tailored for use. I find it the most freeing from linear shackles, figuartive handcuffs, and my own preconceptions. It is improvisatory in the same way jamming in a jazz ensamble is, but with samples.”

Even if your rig is multi-faceted, the improvisational aspect is essential. As Richard Devine explains, his hybrid rig provides “maximum flexibility to change anything at any point in my show.” At the center is a MacBook Pro running Ableton Live 8 which syncs his three primary controllers. “The Monome is dedicated to doing random FM synth triggering with Max, and the MonoMachine is doing lots of synth and baselines, while the Machine Drum handles the huge analogue kick drums, and skeletal backbone percussion.”

Equally complex is the hybrid rig of 8 Bit Weapon. There’s still a laptop, but along with it they have “a Commodore 64 computer, a Commodore 128 computer, a Game Boy, a Apple IIc computer, Elektron Sid Station [containing a C64 sound chip], Nintendo Entertainment System, KORG microKORG vocoder, and a 12-channel mixer.”

While a laptop does all of the number crunching for Tim Exile, the true center of his rig is his two Behringer BCR2000’s and one BCF2000. “The 2-way control is perfectly implemented, and there are hacks around that allow you to use every single button on the surface. I’ve made my own context-sensitive control for layer switching in Reaktor. Pretty much all the state info I need is right there on the controllers.”

Mark de Clive-Lowe’s rig may look like that of a keyboardist with a Rhodes, Clavinet, and other synths. But what he calls “the heart of the show” is the MPC3000 he uses to program beats live. “The tactile interface means i can really get into playing the drum machine like an instrument.”

For The Flying Skulls, each performer takes different instrumental roles. Bringing those instruments together is the Rane Empath. “It operates like a master mixing console for several elements of the show: Snareface on the MPC, Jerome on the MS2000, and a channel from Live running on J Tonal’s laptop.” Using the Empath’s Flex-FX, they “get real-time access to over 100 effects that can be applied to any or all of the channels with touch-sensitive parameter control.”

Audience: Engaged

There is always the need to engage the audience. “This is crucial,” says Richard Devine. “You have to somehow connect with them. I usually try to play some songs that people know, and of course try to play out lots of new material that hasn’t been heard. I like to program large builds and breaks to take the audience on a roller coaster ride, if you will.”

Leading the audience through the performance is no easy task with all the variables in a complex rig, but getting the audience to link the performance to what they are hearing aurally is its own reward.

“Movement is as important as sound in this respect,” says Tim Exile. “I’ve noticed that audiences respond well when they make connections between movements and sounds which they’ve never made before. So if they can see you directly controlling a sound structure which they’d only heard devoid from its kinetic correlate before (a lot of electronic sounds) then they will have a transformative experience.”

“They are seeing a full studio production created at break-neck speed live on stage in front of them,” says Mark de Cliv-Lowe. “They go on a journey via the music – the rhythm, the harmony and the melody.”

Artists can adapt the journey by feeding off the audience. “They are the ocean currents,” says Daedelus muses. “Fighting directly against [them] is useless. I mean, you can tack the ship against the prevailing winds, but you don’t get very far. I like having a direction, but watching and listening and being willing to go elsewhere.”

This doesn’t eliminate the value of more traditional ways of audience engagement. “Definitely always have a mic to talk to yer crowd,” advises J Tonal. “We like to make sure the audience is on the same page as us,” 8 Bit Weapon shares. “We check in from time to time between songs using fun banter.” There is always room in any musical performance for fun banter, but Daedelus warns, “never let audience members try to speak to you in drug-addled states during performance. It is a careless whisper, no Wham reference.”

There Will Be FAIL

With all of the amazing things we’ve been able to do with technology, we’ve yet to perfect the anti-fail science. If only repairing a crashed hard drive were as simple as changing a guitar string.

“I’ve had MPC’s blow up and melt down right before and during gigs,” recalls Mark de Clive-Lowe. “I have played many shows,” says Richard Devine, “where my computer had crashed right before I was to play or I had some hardware sync problems.”

“We have sent the Sidstation back to Sweden for repairs 2 or 3 times,” 8 Bit Weapon recalls. “A drunk club patron tore it right off the stage and it slammed on the floor.”

Managing these inevitable situations is as much a part of the performance as anything else. “The biggest skill for a live performer,” Mark de Clive-Lowe says, “is to be able to take a mistake and flip it so it was never a mistake.” “When you have only a short amount of time to play — when something goes wrong, you have to have a back up plan, which may be having another computer ready to go on standby or another piece of hardware that you can use to play,” says Richard Devine. “There is nothing worse then flying around the world to play a show and running into technical problems.”

But perhaps the absolute worst scenario is, as Tim Exile says, “not being in the right mood. There’s very little you can do about that. There are no other mistakes.”

Primus Luta is a musician, technologist and a writer. When not working to finish his Heads Project, he’s trying to convince himself he’s got it in him to write that book he always wanted to write.

Primus Luta’s blog on noisepages, featuring computer music performance techniques, Plogue Bidule tips, and a lot more:

http://plpheads.noisepages.com/

See the companion video gallery for this story, featuring live performances from the artists interviewed. [about to be posted]

Inside a computer, digital music is entirely unseen. But translate it into the tangible world, and it can be anything you imagine – not limited by acoustic reality or practicality, music can become three-dimensional sculpture.

For artist Christopher Bauder and composer Robert Henke, ATOM’s light and sound sculpture found a three-dimensional matrix of balloons as its medium. Flashing in hypnotic patterns and moving into different configurations, accompanied by live laptop music from Henke (aka Monolake), music and visuals become an inseparable fusion.

ATOM received its North American premiere at Montreal’s MUTEK in May. That turned out to be perfect programming, as it placed ATOM in a week that featured complementary work from artists Artificiel. Henke says some of his matrix manipulations – and even the specific Max/MSP patches from ATOM – came from collaboration with Artificiel and their light bulbs. For their part, at MUTEK they unveiled a new audiovisual etude called POWEr Play involving a live-sampled Tesla Coil. The science fair ethos of ATOM and POWEr Play could have been gimmicky or overly fixated on spectacle, but in these pieces, it was anything but. Both works contemplated their subject matter so thoughtfully that balloons and electrical coils seemed perfectly natural media for the audiovisual imagination, and audiences were left marveling at phenomena in a way too rare in 2009.

Video episode at Blip.tv [includes mobile/desktop video downloads]
YouTube Part 1 and Part 2 (if you prefer YouTube for viewing)

It’s worth downloading the video above and really getting to soak up some of this piece when you have time. I also have an audio interview of a conversation with Robert and Christopher immediately following one of the performances.

You’ll hear Christopher’s voice first, followed by the unmistakable percussive enthusiasm of Robert. For me, the best part of the interview was hearing them discuss whether you should notice some of the unintentional randomness of drifting balloons or technical hiccups, and how they structured the work formally with a palette of possible balloon patterns.

Download the audio interview

For more on POWEr Play, see my Montreal flat mate Greg Smith writing for Rhizome – and stay tuned for the CDM audio interview, coming next week:
power play – artificiel at mutek [Serial Consign Blog]
Variable Frame Rate: Multimedia Performance at MUTEK 2009 [Rhizome]

More information:
Atom project Information at monolake.de
Text interview by Bertram Niessen for Digimag magazine, October 2007, also at monolake.de

Design in music in a digital world can be about the object as the sound – musical ideas translate from one medium to many others. And just when you think you’ve seen it all, someone comes up with a new visual metaphor, a new creation for manipulating music.

OTTO is a functioning prototype combining interactive hardware and computer software, the invention of Luca De Rosso. He produced the design as a thesis project for his masters’ degree in Visual and Multimedia Communications at IUAV University of Venice. It uses the Arduino open source hardware platform and Cycling ’74’s Max/MSP software, and Luca accordingly is quick to credit the assistance of those two communities. In that sense, two, I think it points to lots of new design in the field of integrated hardware and software – not just standalone hardware or standalone software or generic controllers for anything, but hardware that itself behaves like software.

All photos here courtesy Luca and used by permission; see his Flickr account.

OTTO ~ demo.01 from Luca De Rosso on Vimeo.

Luca sends along some more details of the behind-the-scenes workings just for us. (Thanks, mate!)

Luca actually had assistance from his father working on the case. (I love that – father-son collaboration!) All the electronics are on a single Arduino board, and the patch works in Max. (Max has features that make it well worth using, but it’d be nice to see a Pd port, too, making the whole setup open source – and giving you an easy way to run it on Linux.)

OTTO ~ Getting Started from Luca De Rosso on Vimeo.

Luca sends us a view of the innards of this device – you saw it here first:

The first prototype is done, says Luca, with three more coming in coming days as he heads to a festival in Croatia. Plans for the future: no commercial availability yet, but Luca says he’d be happy to hear from anyone interested in manufacturing. (Capital remains the big challenge, even as fabrication gets easier.)

I also love the way he’s designed the documentation. Music tech industry, please, this is how it should be done – with all due respect and without naming names, we really would love if you just showed us your gear and didn’t have some swarmy dude gushing about lots of hype. In fact, we’d be equally happy to buy your gear if the design spoke for itself rather than having your name and circuit diagrams and random text plastered all over it.

But this is really visually inspiring, creative work. And to top it off, it looks insanely fun to play. Putting the beats in a circle opens up all kinds of other possibilities, and suggests thinking in terms of cycles rather than the grids we see on other hardware. As with the monome, you can imagine other software applications that would hook into this basic, minimal hardware design. I hope we see more of this design and concept.

http://www.lucaderosso.com/otto/otto

More videos:

OTTO ~ demo.02 from Luca De Rosso on Vimeo.

OTTO ~ demo.03 from Luca De Rosso on Vimeo.

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

Manual MIDI

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

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

monome Emulation for APC40 and Korg padKONTROL

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

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

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

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

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

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

APC40 Customization, Performance Tweaks

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

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

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

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

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

…and really, that deserves a separate post.

MIDI for Lights

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

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

Midi confusion with APC40

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

OK, let’s hack the APC

The Hardware Handshake: First Clues

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

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

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

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

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

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

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

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

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

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

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

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

A Video to Close us Out

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

Creating digital music is about more than audio. Notation remains an essential way to communicate among musicians. Notation is deep and complex, so there’s plenty to talk about. As a long-time Sibelius user, though I want to discuss some core techniques that I find open up a lot of other possibilities, techniques to which I continually return. I happen to be sharing this at a discussion at the City University of New York Graduate Center today, so the timing seems right.

Teachers and experimental, avant-garde composers have something in common: you often need to convince notation software to behave in a way that’s contrary to the expected norm.

To save you time, notation software generally assumes that all music has bars, and that those bars go from left to right with everything visible. This is especially true in Sibelius, which is able to perform as quickly as it does because everything you see on a score is relative to a position in a bar, rather than being set up arbitrarily as you would in a page layout program.

That works much of the time, but what if you have music that isn’t in a time signature? What if you’re transcribing early music or world music that doesn’t operate in 4/4? What if you’re making a quiz in which you don’t need bars, or want to have a blank space for students to fill in answers?

Updated: Just days after this feature, Sibelius announces Sibelius 6. Relevant to this story, this means at least some of the manual hacks for things like beaming across bars and feathered beams will now be automatic! Neat! I’ll have to do new tips for Sibelius 6 when it arrives.

Technique 1: Staves and Instrument Types

Oddly enough, the answer to all of these questions is basically the same: change the way the staff is displayed. You’ll still need to account for bars behind the scenes, but once you learn how to handle Sibelius’ staff options, this isn’t so difficult. This step is a bit confusing for those of us (hand raised) who have been using Sibelius since 1.0, as Sibelius 5 changed the name of this option from Staff Type Change to Instrument Change. (The latter makes more sense in conventional music, even though the former will make more sense for this tip.) But the technique is basically the same.

To insert a new instrument type, right-click (or ctrl-click on Mac, or choose Create) and select Other > Instrument Change.

Select Choose from > All Instruments and Family > Others (for the most generic type).

You’ll see some useful options already. In addition to choosing different numbers of lines, there’s an option that entirely hides a staff — “No instrument(hidden)” – and options that show just barlines or just bar rests.

Try selecting the “No instrument (bar rests shown)” option, then click in the score where you want the change to happen. You’ll see a blue rectangle around the barline at which the change is inserted. Clicking this barline in the center will allow you to select the change itself. Once selected, you can drag it left and right to change the point at which the change occurs, or press Delete to remove it. (That’s important for hiding portions of staves, as you’ll need to be able to select them even when hidden!)

You can imagine lots of possibilities for using this simple technique. For quizzes, for instance, you might simply hide the portion in which you want a student to fill in an answer. Or you can use those hidden bars to help space out a quiz. Or you can use some hidden bars to provide space for a graphical notation in a contemporary / experimental score.

For all of those applications, though, you may need some different variations.

To create your own instrument type, choose House Style > Edit Instruments.

Choose Ensembles > All Instruments, then Families in ensemble > Others to get the generic types.

Let’s try creating a staff type that looks like a normal treble staff, but hides the barlines. Select “Unnamed (treble staff)” and choose New Instrument… to create a new instrument that will be based on that existing instrument. Sibelius will ask if you’re sure. (It can smell uncertainty. You’re sure.)

Under “Name in dialogs,” choose a useful name, like “Treble staff (barlines hidden).”

There are actually lots of powerful options here, but skip straight to “Edit Staff Type.”

Under General, you can choose the number of staff lines and what objects are shown.

Uncheck Initial barline and Barlines, and you’ll have a staff with hidden barlines.

Also make sure to uncheck “Used as default staff.”

Bar rests won’t make much sense if you don’t have bars, so click the Notes and Rests tab, and uncheck “Bar rests.” You’ll want to leave the Rhythms options, because you probably do want rhythms in this case, just not the barlines and bar rests. (Unchecking Rhythms could be useful, though, for things like plainchant.)

Again, to insert, you’ll right click, choose Other > Instrument Change, and use the blue arrow to click where you want the change to go. Here’s our result:

And yes, this can be handy for printing out blank notation paper if you’ve run out / forgot your manuscript notebook. (Been there.)

One last note: you may have noticed that you still have bar numbers. Check House Style > Engraving Rules > Bar Numbers. Other global score settings are found here, so you should get in the habit of a trip to the Engraving Rules any time you’re creating a new score or developing a new template.

Technique 2: Noteheads

Just about anything you can’t do with staff types, you can do with noteheads.

The most useful notehead, of course, is a dead notehead.

Okay, that sounded like some sort of anti-notehead bitterness. But seriously, by hiding noteheads, again, you can create all sorts of alternative notations, and because stems are still visible, musicians can more easily see where beats are. You’ll also need noteheads for percussion notations and the like.

To change notehead types, make sure the floating Properties window is visible (Window > Properties). This is useful for changing other settings, too, so it’s well worth exploring. In the dropdown, you’ll see headless noteheads (position 7).

You can also edit your own Notehead types, just as with instruments and staff types, by selecting House Style > Edit Noteheads.

One other neat trick using the Notes panel is that you can turn on and off tuplet brackets. That allows a little hack that gives you feathered beams. You’ll find instructions under Feathered beams in the manual (p. 79 in my edition).

Technique 3: Locking Layout

The problem with just hiding barlines and such is that you still have bars underneath, and they’ll continue to automatically flow as Sibelius adjusts the layout. With most scores, that’s a good thing, but with ametrical scores or quizzes or short example snippets you want to export, that’s obviously a bad thing.

The solution? It’s time to learn the keyboard shortcuts for locking your layout in place.

System breaks: Click a barline and hit the enter key. You can insert forced system breaks just like carriage returns (line breaks) in a word processor. You’ll see an icon above the score both in the line with the break, and the line immediately following.

Page breaks: Ctrl-Return / Cmd-Return breaks the page.

Special breaks: You’ll find other options in Properties > Bars, including a Special Page Break that inserts a blank page. Click a barline first, then choose from the drop-down menu in Bars.

Indentation: You can move a line left or right by clicking the left-hand side of a stave, then moving it right with the left and right arrow keys. Hold down ctrl (PC) or cmd (Mac) to move by larger increments.

Expand or contract bars: Invariably, you’ll find some of the automatic spacing doesn’t look quite right – especially in these special cases. Click a bar, then press shift-alt (shift-opt) and the left and right arrow keys to make a bar wider or narrower.

If you ever get lost with any of these steps, Layout > Reset Position restores the default.

Technique 4: Exporting Score Snippets

At a certain point, as a composer or a teacher, you don’t always want to do all of your page layout in Sibelius. Likewise, I’m surprised that people don’t more often use little snippets of scores to communicate ideas, whether it’s highlighting a specific comment on a bigger score, or using notation software to quickly communicate short bits of music. Obviously, this is useful for musical examples in essays and the like, too.

When you’re ready to export parts of a score, you have several methods in Sibelius:

The graphics-copying way. Choose Edit > Select > Select Graphic (Alt-G), and Sibelius gives you a bounding box that allows you to select a portion of your score. (If you select your bars before choosing this option, it will attempt to snap to the right area, from which you can adjust it further if you like.)

Once you have the area selected the way you like, use the standard copy shortcut (ctrl-C / cmd-C), then choose your word processing or layout app and paste. To cancel out of this mode, hit Esc.

Most of the time, this is really all you need to do, unless you’re concerned about higher-quality output. In that case…

The export way. If you need to fine-tune output options and DPI, you should instead use File > Export > Export Graphics. Here, you can select the format you like. OpenOffice isn’t listed, but choosing the Sun StarOffice(TIFF) method is your best bet. For Word, choose the explicit Word EPS setting for the highest-quality output.

The PDF way. If you’re on a Mac or have Adobe Acrobat Professional (or another PDF generator) installed, there’s an additional way, which is to export to PDF. I find that inserting PDFs is the best way to go for inserting later to software like InDesign. The default PDF creator on Mac is pretty good, but a full version of Acrobat is often preferable to other options.

Screencast: Sibelius has a screencast of these techniques, which you’ll find from the opening screen.

Technique 5: Making Teaching Materials

The other techniques all work for teachers and composers alike, but when you do need to teach…

Does all of this seem like a lot of work? Still not sure how you combine the layout techniques above to make something look like a quiz, flash cards, or the like? Need to teach something and running short on time?

A recent feature in Sibelius is a comprehensive, shared set of teaching materials. (If you want to share and share alike, you can also publish your own materials to the site and spread the love.)

You’ll find the site itself at:

http://www.sibeliuseducation.com/

When you open the program or choose File > Worksheet Creator, you can tap into these resources.

Choose Template, and you’ll find a number of blank templates set up by activity (manuscript paper, worksheets and handouts, matching different materials, and flashcards).

If you want still additional help, ideas, and starters, choose Type of Material > Teaching and learning materials. You’ll want to limit your search, or loading the possibilities will take a long time. But from there, you can find all kinds of additional examples. Many of these come from the UK, so be prepared for English terminology and even UK-specific projects, but they’re still quite useful even if you’re American and tend not to call things “breves.”

Pick a category, and you’ll find other layouts that can be the basis of your own work, as well as some relatively generic materials that are useful to everyone.

Here’s what you’ll see as you dig into worksheets:

Pull up an example, and you’ll find something that you may be able to use as-is, or at least a template that could be useful for adapting to your own coursework.

There’s even a Circle of Fifths ready to go. (The only change you might need to make, depending on the part of the world in which you live, is to call it the Circle of Fourths!)

Other ideas?

This is a bit of a departure for CDM, but I know lots of you out there are producing notation for various reasons. I hope this was helpful, and if anyone wants to do a similar story for Finale or another tool, I’m happy to have it. Let us know what other tips you like or if you have additional questions.

Addendum

Having just done this workshop, it’s worth noting a couple of things I discovered.

First, Sibelius I see now has an option in Preferences to account for laptops that don’t have numeric keypads, making entry much easier (though I still prefer the numeric keypad layout):

Next, I was reminded that a lot of tricks use the Beam line type, which you’ll find in the Line dialog. Any old line will do, but this will look like your other beams. This way, you can manually draw in notations that the software itself may not recognize.

And it’s worth noting that a lot of beaming tricks can be accessed in one of two places:

1. Beam display in the Staff Type House Style (there’s a checkbox buried in there for forcing “horizontal beams,” alongside the options for hiding rests and such above)

2. Beam groups and beaming rules (including the ability to beam across rests) in the Time Signature dialog.

For Finale users, most of these basic strategies will translate to your notation tool of choice. Generally, Sibelius lets you select objects directly, whereas Finale uses specialized tools, selected by toolbar icons, for each job. That also means that when you’re using Finale, you may need to select the tool before you’re presented with variables related to that type of object, whereas Sibelius consolidates those settings under House Styles.

For instance, Finale edits the staff types via an item, accessed from its staff tool, called Define Staff Types. That dialog is very similar to the Staff Type and Instrument dialog above.

Ultimately, in fact, both Sibelius and Finale have a lot of the same strengths and shortcomings once you learn them, because fundamentally they do treat scores according to regular bars and barlines. Interestingly, Finale has the abilty to have independent time signatures on different staves, but it’s almost useless, because it still puts the barlines in the same place. (That is, both tools are limited in this respect.)

What do you really want from a recording tool on a computer? The Digital Audio Workstation answer to that question has for years been on giving you a generalized set of tools that try to anticipate every possible need. The “workstation” approach puts a whole bunch of functionality in one place, in particular adding features like plug-in hosting for supporting third-party effects and instruments, video editing and scoring, and music notation.

Record is a different animal: it’s a specialized tool focused on making music with audio, instead of a generalized tool. Reason has focused on synths, with a distinctive set of hardware-styled modules in a virtual rack. Record focuses on sound, with a distinctive set of hardware-styled modules in a virtual rack. Get it?

What’s left out is important. There’s no plug-in support, but by limiting use to the internal sound modules, Record is entirely agnostic about things like sample rate and can be far more flexible with modular audio routing and fluid tempo changes. (There’s also no MIDI out support, but if you’re looking to sequence external hardware, I might look elsewhere, anyway – especially with gems like Numerology out there.) Record also supports ReWire and has various export features, so the assumption is that – as with Reason – when you really want plug-ins, you can use your existing environment of choice.

Maybe you can call the results a DAW, if you really want to. But the one thing that isn’t debatable: Record is Reason for sound.

CDM was first with the official story from Propellerhead over the weekend, talking about the philosophy behind Record. Now we can talk about the specifics inside – and I have a test version here I’ve been working with while on the road.

Basically, Record combines comp-based recording with Reason-style racks and a whole load of goodies for processing and mixing your sound, including Line 6 guitar effects and an emulated SSL mixing desk. Why am I excited to begin working with it? Basically, it’s what happens when you flip the Record interface around. The most important screenshot (see any of these shots bigger by clicking on them):

Here’s what you get:

• All about “Record”ing – with comps: As the name implies, the real soul of Record is recording. Comping is built in from the beginning so that you get a take you want, and each track even includes an integrated tuner by default. This is really a tool that assumes you’re actually one person plugging in an instrument and playing.
• Music and tempo-based sound: “Tempo-independent” audio is almost the reverse of what this is. When you record sound, the idea is that you always have some musical information in mind – beats and bars. Record lets you then change the tempo of that audio fluidly, without ever having to think about warping or slicing or markers or loops or anything like that. Propellerhead says they’re especially proud of the audio quality of the stretching algorithm working behind the scenes to make these changes sound good, which is what we’re already hearing (unofficially, of course) from beta testers in comments and elsewhere.
• Tempo changes: Unlike other tools that have focused on DJ-style or electronica-style master tempo, Record assumes fluid changes in tempo from version 1.0. There’s always a “conductor” track, a main tempo lane, which can have subtle, curved tempo changes (accel./rit.). When you export your audio, that information is exported as MIDI, so this musical information travels with you to other tools.
• An integrated recording/mixing/arrangement environment: This is the one DAW-like part of Record, though it still feels more like Reason than anything else. Each track gets three things: a channel routed into the mixer, an individual device module you can insert into the rack (as in Reason), and a sequencing lane for MIDI and audio.
• Sequencing: This is the most traditional part of Record – you do get conventional sequencer lanes. Clips can arbitrarily contain audio, MIDI, and automation data. The important thing to note is that, because Record doesn’t support plug-ins, you can count on consistent integration of automation – if there’s a knob in a module, you can automate it in the sequencer, just as in Reason.
• Hardware-style mixing: No software-style mixer here: the mixer inside Record is a direct simulation of hardware, not a loosely-inspired emulation. The Record mixer is modeled after an SSL 9000k analog mixing desk, so that it intends to look, work, and sound like the real thing. (SSL was not officially involved, so you’ll just have to count the Propellerheads as SSL fans.)
• Reason-style effects: In addition to the mixer, you get Reason-style modules for EQ, dynamics, and other effects.
• Line 6 guitar effects: Line 6’s virtual POD is built in, so you get their guitar amps and cabinets built in. I’m guessing those should be quite nice with keyboards, too.

Arrangement: Looking at the birds-eye view, Record does admittedly look like a DAW. But dig in a little bit to how these modules work, and there’s more Reason DNA than anything else. It’ll be interesting to work with these modules over the coming months. Also, most important to recognize is that when you see audio in Record, it will always obey tempo changes you make, including gradual speed increases and decreases – no warping or slicing required. When you do want to slice up audio, you could, say, drop Record as a ReWire client into an Ableton Live set, or even export your audio with tempo changes from Record as one track and put your sliced audio in a different rack.

The mixing desk:

The thing is, it’s not so much what Record does as what it does in a Reason-style way. So while this is a preview, not a review, here’s what makes Record more like Reason:

For Reason users, this one image pretty much sums everything up. The workflow is still essentially a Reason workflow – if you love that, you’re likely already salivating. If not, it’ll likely take more convincing from the other aspects of the tool.

• Every track is a rack: Each time you create a track, you get a modular rack, which translates to the inserts you see in the mixer. For advanced users, this means you can do anything with routing you want. You get a full-blown rack on each track, with all the usual goodies for routing. For beginners, it means you can call up easy presets for whatever you’re doing, and the parameters show up as plain-English knobs in the mixer. You don’t have to think about routing or what everything represents; you just focus on sound. For beginners and advanced users, the ability to “see” all of this routing with virtual cables and such means sophisticated mixing and routing setups aren’t quite so abstract.
• It’s a Reason interface: Everything looks and feels like Reason, even with a much more involved UI. All the new views continue on the theme of adjustable navigation panes. These views either get combined into a single-window interface, or can be detached if you’d prefer. But there are almost no dialog boxes, with one notable exception:
• You get Reason patches and patch browsing, for audio: Reason users will feel right at home, as Record extends the patch browsing metaphor from Reason. And because track effects inserts use what are essentially Combinators, those inserts just feel like Reason devices inside a mixer.
• Reason + Record: If you have Reason, you have access to all your Reason modules. And since Record has a big Reason rack – well, you get the idea. Instead of recording inside Reason, what Reason users get is Reason inside a bigger version of Reason that understands not only recording, but mixing and audio arrangement, and treats audio like music, with tempo.
• ReWire: Record is a ReWire client (slave), not a host (master). That should be your first clue Propellerhead aren’t trying to replace Pro Tools, Live, and Logic. But it does mean you could easily use, say, Record for recording purposes on your own, then drop it into a Pro Tools session in the studio, or Record to do some song-writing that you then bring into an Ableton live PA or remix set.
• Reason-style automation and control. Most notably, this is the first audio production tool I’ve seen that was set up from the beginning to be used with keyboards, as Reason was. It’s funny: right now, M-Audio are pitching using a keyboard to control Pro Tools with their Axiom Pro / HyperControl product. This essentially goes the other way: like Reason, Record uses the “Remote” protocol, which was effectively the first to “automap” your keyboard controller and control surface to the software. That means you can comfortably produce an entire work from your keyboard, while adding guitar or vocals as an audio recording.
• Oh yeah, it’ll be fun even if you only use synths: In case you haven’t guessed already, for Reason users, this means mixing and processing and arrangement tools that weren’t available before, so even if you never hook up a mic to Record, I imagine you could use almost all of these tools. (Only the tuner and audio comps become redundant.)

It’s really the relationship of the device rack to the mixer and tracks in Record that make it unique, and will be fun to explore over the coming months. When you create devices and Combinators, you can easily see them in the mixer and track sections. Sends are named as the actual sound parameter, too. Because it doesn’t support plug-ins, that also means you never have to worry about the way parameter names are handled in formats like VST, though you can always return to your favorite host when you do want plug-ins since Record is also a ReWire client.

Line6 guitar and bass amps are available out of the box as insertable modules. This is all you need for the interface: it’s aggressively simple.

The patch window will look familiar to Reason users. But if you’re new to this, what it means is that you can easily surf through, say, Line 6 guitar presets and hear immediately what they sound like.

So, what does the music sound like? Josh Mobley via Twitter tells us about his official demo song, “Push Me Down,” made in Record for Propellerhead. All the songs in the embedded player below were made in Record, with the exception of “Narrow Escape,” the demo for Reason 4.

About that Dongle

The other bit of news – and the one item that’s likely to be most divisive – is that Propellerhead is changing the authorization scheme in Record, as explained here:

Ignition Key

The good news: “demo” mode / non-authorized mode is actually only “open”-disabled. You can even save files in the demo; you just can’t open existing files. The Ignition Key comes free with the tool rather than being a separate purchase as with some iLok products, and if you lose or break it, a replacement is available for a nominal fee. (Some manufacturers actually have the gall to charge for the full purchase price of the product or close to it, which is utterly ridiculous.) Also, if you don’t want to use the key, there is an Internet authorization.

The bad news: it is still a dongle. Internet authorization requires a consistent connection while you’re working; the moment that’s dropped, the software reverts to demo mode. I would personally much rather have seen one-time Internet authorization as is available from Ableton and Native Instruments, among others, especially as Record would be fun to use on a bus or train without plugging in a dongle. Propellerhead say they’ve put some thought into this and wanted to do copy protection right, but I expect they’ll hear about it anyway.

The one upside I do see is for people who use a lot of machines (like myself, for one). You can use just the dongle without any other authorization, and you can use it on as many machines as you want. So that means you can move from a studio to a Mac laptop to a PC laptop to a netbook just by moving your dongle around, and never have to fill out a registration form or worry about if you’ve run out of authorizations.

Also, I’d suggest that people use this as an opportunity to freely try the demo without any annoying limitations and decide if you like the tool before you buy it.

Availability / pricing

Beta testing is starting now, today – sign-up at the site below.

September 9, 2009 is the official release date.

Suggested retail: US$299, EUR299. No word yet on what bundles will be available for existing or new Reason users, but Propellerhead says that it will have special bundle pricing of some kind.

Videos and more info at:

www.record-you.com

It’s been a long, long wait for side-by-side Reason and audio racks and recording in Reason, but there’s no question that this is a big announcement.

Since many of you will be beta-testing this alongside me, I look forward to hearing your opinions of the tool and any tips or techniques you discover.