“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]

Having full control of a complete mix and session from your MIDI keyboard – without having to move your hands to the mouse or shift your focus to your computer screen – can be an addictive, if elusive feeling. Here’s a look at one way to accomplish that objective using the new Axiom Pro keyboards from M-Audio and CDM reader favorite Ableton Live, thanks to a first-look video provided to CDM first.

We’ve seen efforts to make this happen before, notably including the Korg Kontrol keyboard series working together with Propellerhead Reason and Novation’s Automap with software like Ableton Live. M-Audio’s Axiom Pro line has a new twist on the idea with what Avid calls “HyperControl.” Several details make HyperControl unique. For one, it doesn’t require any intervening software or drivers; the keyboard is USB class-compliant and plug-and-play, and you don’t have an additional software layer as with Automap. Also, the Axiom Pro is natively capable of sending keyboard commands, and even has a numeric keypad on the front panel of the unit. But most importantly, the Axiom Pro has its own workflow for different editing and performance functions. My suspicion is whether you love or hate HyperControl will probably hinge on how you adapt this feature.

Avid has been kind enough to give CDM an exclusive scoop on an extensive video they produced walking you through the process of setting up HyperControl with Ableton Live, step by step. Now, normally many of the videos from hardware makers make me cringe. John here has done a really terrific job, however. It’s really a tutorial and not a sales pitch, and while I’m a fan of writing and reading, this would be really confusing without the video.

Much of the working method focuses here on controlling the whole session rather than performance parameters. If that doesn’t appeal to you, skip to about seven minutes in for a discussion of “Device Mode,” which is when you finally map those eight encoders to the eight macro parameters for Device Racks so you can tweak your live synth sound. What’s nice here, though, is that you could couple that technique with the tips on recording clips, so you can play, record those clips, play back lips, and tweak all at once, one-man-band/one-woman-band style.

Have a look at the video, and let me know what else you might like to know. What isn’t covered? What other ways might you want to use a keyboard-and-software rig like this?

And don’t worry, while this week is becoming Controller Week (like shark week for MIDI nuts?), it doesn’t have to be The Ableton Live 24 Hour News Network. HyperControl also supports other software, including Avid’s own Pro Tools. Apple just released support in Logic Studio 9 and MainStage which I’m researching now. And while HyperControl is a slick moniker, I’m also researching more conventional control methods, which can even support Linux thanks to the fact that the hardware (unlike Novation’s) is class-compliant. So let us know your priorities in comments, and I’ll see if we can make them happen.

Axiom Family at M-Audio (now Avid

I Want My CDM TV

We’ll be putting more videos onto CDM TV very soon, and now you can subscribe to videos easily via iTunes, Miro, and RSS. Transcoding is fixed, too, so you can load up this video on your iPhone / iPod touch and balance it on the end of the Axiom Pro while you practice these techniques, if you like!

Subscribe to CDM TV with iTunes
Subscribe to CDM TV with RSS
Subscribe to CDM TV with Miro

Still a little thinner than we’d like, but expect this channel to heat up for the …um, fall season.

Here’s a switcher story of a different color: from the Mac, to Linux. It’s one thing to talk about operating systems and free software in theory, or to hear from died-in-the-wool advocates of their platform of choice. In this case, we turn to Kim Cascone, an experienced and gifted musician and composer with an impressive resume of releases and a rich sens of sound. This isn’t someone advocating any platform over another: it’s an on-the-ground, in-the-trenches, real-world example of how Kim made this set of tools work in his music, in the studio and on tour. A particular thanks, as he’s given me some new ideas for how to work with Audacity and Baudline. Kim puts his current setup in the context of decades of computer work. Even if you’re not ready to leave Mac (or Windows) just yet, Kim’s workflow here could help if you’re looking to make a Linux netbook or laptop more productive in your existing rig.

Stay tuned, as I’ll have some other stories on how to make your Linux music workflow effective creatively, particularly in regards to leaping over some of the setup hurdles Kim describes. -PK

Historical Evolution

I’ve been working with computers since the 1970s. Inspired by the work of composer David Behrman, I taught myself assembly language and programmed a simple digital sequencer on a KIM-1, single-board microcomputer, controlling an Aries modular synthesizer I had built. I discovered a then-new magazine called Computer Music Journal at the local computer shop and bought every copy I could get my hands on. (I still have them, too.) Later, I helped a friend’s father, an executive at IBM, unpack and set up the first personal computer IBM made. The manuals alone took up two or three feet of bookshelf space.

Fast-forward through a couple of decades of owning Commodore 64s, Apple computers, and PCs. In 1997, I purchased my first laptop: a woefully-underpowered Compaq Presario. It wasn’t fast enough for real-time audio, so I had to render sound files to hard disk using the audio programming language Csound. I created many of the sounds this way for my CD ‘blueCube( )’. But the capacity to work anywhere was enough for me to give up ever owning another desktop computer.

Frustrated with the ‘code-compile-listen’ process of working with Csound and wanting to work in real-time, I switched to the graphical multi-media programming language Max/MSP, which necessitated a move back to Apple hardware, so I bought a PowerBook. Having Max/MSP running on a laptop was the perfect environment for me. I could build the tools I needed whenever an idea presented itself. The computer functioned as both sound design studio and stage instrument. I worked this way for ten years, faithfully following the upgrade path set forth by Apple and the various developers of the software I used. Continually upgrading required a substantial financial commitment on my part.

Apple Seeds of Discontent

When I’m on the road, I use my laptop as a music studio, performance instrument, and administration office. I don’t like surprises on the road. Having a computer fail means a loss of income, and makes for an embarrassing moment if the failure happens during a performance. If watching laptop music bores some people, watching a musician reboot is even worse. So to be safe, I stress-test all new hardware or software in my studio for at least a month before I take it on the road. Max/MSP patches run for hours, software is used for weeks, and hardware is left on for days at a time to help induce failure before I leave home. But as fate would have it, an iBook I was touring with died a few years ago. I brought the laptop into an Apple repair shop in Berlin, where a technician diagnosed the problem as a faulty logic board. The failure rate on logic boards was high for that model of iBook, and in response to public pressure, Apple instituted a logic board replacement program. Luckily, my laptop qualified and the logic board was replaced for free. But the failure and ongoing buggy behavior impacted my work schedule and added to the stress of touring.

I’ve now replaced logic boards on three computers; the other two I paid for out of pocket. The out-of-warranty cost of replacing a logic board on an Apple laptop is around six hundred dollars — cheaper than buying a brand new laptop, but still significant.

If you make your living with applications that run on OS X, there are no options if a laptop fails. You either repair expensive Apple hardware or buy new expensive Apple hardware. This is called ‘vendor lock-in.’

Then, during my 2009 spring tour, my PowerBook G4 exhibited signs of age, with missing keystrokes, intermittent backlighting, the failure of a RAM slot, and reduced performance. As an alternative to repairing the PowerBook, I investigated what a new MacBook Pro and upgrades for all my software would cost. A quick back-of-a-napkin estimate came to approximately $3,000, not including the time it would take tweaking and testing to make it work for the tour. If the netbook revolution hadn’t come along and spawn a price-wars on laptops, I might have proceeded to increase my credit card debt. But as a wise uncle once advised, “you invest either your time or your money; never both.”

Meeting Ubuntu

I had tried Linux in 2005 on PowerPC-based Mac laptops, though at the time I couldn’t get audio working, even after extensive tweaking. But I had kept an eye on Ubuntu ever since. After considering MacBook Pro prices, I checked out the new netbooks coming to market and picked up a refurbished Dell Inspiron Mini 9 with Ubuntu pre-installed.

I loaded up my Dell with all a selection of Linux audio applications and brought it with me on tour as an emergency backup to my tottering PowerBook. The Mini 9 could play back four tracks of 24-bit/96 kHz audio with effects – not bad for a netbook. The solution to my financial constraint became clear, and I bought a refurbished Dell Studio 15, installed Ubuntu on it, and set it up for sound production and business administration. The total cost was around $600 for the laptop plus a donation to a software developer — a far cry from the $3000.00 price tag and weeks of my time it would have cost me to stay locked-in to Apple. After a couple of months of solid use, I have had no problems with my laptop or Ubuntu. Both have performed flawlessly, remaining stable and reliable.

Getting Past Ubuntu Audio Complexities

There are a few differences between how audio works on Mac OS X and how it works on Ubuntu Linux. OS X uses the Core Audio and Core MIDI frameworks for audio and MIDI services, respectively. All applications requiring audio services on OS X talk to Core Audio, which mixes and routes multiple audio streams to the desired locations. Core Audio is simple, monolithic, and easy to set up, and all the end-user controls are accessible from one panel. You can even create a single aggregate device from multiple sound cards if you need more inputs or outputs than one sound card can supply. To Apple’s credit, Core Audio and the applications that make use of it are the reason why you see so many laptop musicians seated behind glowing Apple logos on stage.

On Ubuntu, audio is a rather different story. Apple’s slogan ‘Think Different’ would be good advice for musicians encountering Ubuntu’s audio setup for the first time. Audio in Ubuntu can appear at first to be a confusing jumble of servers, layers, services, and terminology. Go to System->Preferences->Sound, click on the Devices tab, and check out the pulldown menu next to ‘Sound Events’ at the top of the panel. You will see various acronyms, possibly including cryptic-looking technologies like OSS, ESD, ALSA, JACK, and Pulse Audio. These acronyms represent a byzantine tangle of conflicting technologies that over time, and due to political reasons or backwards compatibility, have ended up cohabiting with one another. ‘Frankenstein’ might be an accurate metaphor here.

Thankfully, there is a simpler way, which is the combination of ALSA [a high-performance, kernel-level audio and MIDI system] and JACK [a system for creating low-latency audio, MIDI, and sync connections between applications and computers]. The battle-scarred among us have learned to ignore all the other audio cruft bolted on to Ubuntu and just use ALSA and JACK. One can think of the ALSA/JACK stack, the heart of most pro Linux studios, as the Core Audio of Linux and in my opinion Jack should be the first thing installed on any musicians laptop. I’d go so far as to suggest placing it in the Startup Applications so it’s always running.

The ALSA/JACK combination is a little more complex to set up and tweak than Apple’s Core Audio, but there’s a lot of good information online. [Ed.: ALSA, JACK, and the real-time Linux kernel also have some advantages over Mac OS X that can be worth the effort. While JACK has been ported to Mac, Linux has more JACK-aware tools, which is necessary for transport sync. Just as importantly, once configured, you can build rigs with Linux that have greater low-latency performance than may be practical on Mac or Windows. In other words, while it may require an investment of time, it can be both free and better! -PK]

Workflow

Over the past ten years, I’ve developed a workflow that has worked well in the studio and on the road. Since I created most of my tools in Max/MSP, they could shape-shift to fit any musical task I encountered. A sound mangling tool I’d written for studio use, for instance, I could then adapt for a performance with Tony Conrad. I modified parts of my performance patch for sound installations. This environment served me well over the years – until recently, when my aesthetic focus changed from using randomness in my work to taking a more deterministic approach. This happened to coincide with my change of operating systems.

I do a lot of location recording while on tour. My rig consists of an Olympus LS-10 digital recorder and an Audio Technica AT-822 single-point stereo microphone. I record at 96kHz/24-bit to a 16GB SDHC card in the LS-10. When I want to audition sound files in the field, I use my netbook’s SDHC reader, renaming sound files directly on the card. I can look at some of the files in Baudline if I need to check for low-frequency rumble or technical anomalies. I have come to use Baudline on a daily basis.

Back in the studio, using the sound editing program Audacity, I remove voice slates, trim heads and tails, adjust gain and EQ as needed, then save them to a project folder. And because I don’t like surprises in the studio, either, this folder gets backed up onto a remote network drive as well as a local USB drive.

Building my sound library takes weeks or months. During this time, I start filling a notebook with ideas, drawings, plans and marginalia, from which a score emerges. I import all my project sound files into the open-source Digital Audio Workstation Ardour, arranging them to loosely resemble the score in my notebook. Once my Ardour session is set up, I move sounds around, try different effects, create new textures by layering, then render and re-import sub-mixes until the piece starts to take shape. I use a KORG nanoKONTROL as a mixing surface. I assign faders, pans and switches assigned to the DAW allowing me to quickly play around with different mix ideas.

Once the piece sounds finished, I mix down to a stereo .WAV file at 24-bit/44.1kHz, without using compression or EQ on the mix bus. Tip: mastering engineers really appreciate getting a raw 24-bit master that hasn’t been fiddled around with by the musician. For performances, I also use Ardour and the nanoKONTROL to do an acousmatic presentation. This version of the Ardour session will have compression and/or EQ on the mix bus, since I want the material to sound more polished. As a side note: I am looking into using the mastering tool JAMin [JACK Audio Mastering Interface] for this purpose in the future.

Sayonara, Apple

After ten years of working on Apple laptops, I’ve left the fold. Not only was the expense of owning and maintaining Apple hardware a key factor in my switch, but the operating system had become a frustration to me. Details like not having a tree-view in the right hand panel of the Finder window slowed me down. Ubuntu, on the other hand, feels more like an operating system made for grown-ups. And what’s especially nice is that Ubuntu scales nicely to the expertise of the user. Your cousin the computer geek or your Grandma can install and use Ubuntu and get as deep as they like. Combine this with the recent rash of cheap, powerful laptops, and Ubuntu’s market share is bound to grow.

A Request

It’s important that kernel and audio application developers (1) ensure all audio creation software has support for JACK, (2) improve and update tools for JACK to make it easy for musicians to install, configure, and use, (3) ship distros with the realtime kernel already tested and configured for use, (4) to integrate the real-time kernel patches into the mainline kernel. [Ed.: On each of these points, distributions and kernel builds are steadily improving, partly thanks to feedback from communities like the music production community. The realtime kernel likely won't be the default, mainline kernel, but it's important to have well-maintained optional packages at the very least. That doesn't mean you have to wait for improvements to happen, though, and in future articles I'll talk a bit about how you can configure your system now to take advantage of this functionality. -PK]

Most importantly, consider paying a subscription to support developers of JACK and your favorite Linux audio software, or, if you can write code, proofread text, write a manual, do a translation, contribute graphic design, or create content; please help by contributing something to the development of the software you use.

I would like to thank Ken Restivo, Mike Rooke, Paul Davis, Philip DeTullio, Jörn Nettingsmeier and Matt Griffen at Canonical Ltd. for advice and inspiration in the writing of this article.

Kim Cascone is a composer, sound artist, touring musician, lecturer and writer. He lives in the San Francisco Bay Area with his wife Kathleen and son Cage.

Links:
http://www.osnews.com/story/6720/Introduction_to_Linux_Audio
http://www.alsa-project.org/main/index.php/Main_Page
http://ardour.org/node
http://audacity.sourceforge.net/
http://www.kokkinizita.net/linuxaudio/
http://www.baudline.com/
http://jackaudio.org/
http://drobilla.net/software/patchage/
http://www.ladspa.org/
http://lv2plug.in/
http://dssi.sourceforge.net/
http://jamin.sourceforge.net/en/about.html
http://linuxaudio.org/
http://www.ubuntu.com/
http://code.goto10.org/projects/puredyne/
http://www.bandshed.net/AVLinux.html
http://rt.wiki.kernel.org/index.php/Main_Page
http://www.pulseaudio.org/
http://developer.apple.com/audio/overview.html

Corrections / clarifications:

Ed.: I originally claimed that JACK Transport sync is not possible on the Mac OS X port of JACK. As kindly pointed out by a reader, this is not correct. JACK Transport-aware applications on the Mac will work.

Secondly, Kim argued that you could pull out a drive without having to go to a lot of trouble unmounting it first. At least one commenter argues that risks data loss, and given that users may be using something like FUSE to access foreign file systems like NTFS or the Mac’s own HFS+, I don’t yet know what the exact details will be. As I said in comments, however, Nautilus and the command line eject function for me are quicker and more effective than similar unmounting on Windows and Mac, so I still notch this one for Linux. -PK

Here’s a superb reader tip: DJ Josef Prusa has been using SugarSync to synchronize Native Instruments’ Traktor Pro DJ software, so that he and his brother have their full music collection at the ready at gigs. (Naturally, this same technique means that if one of their MacBooks should die, bro to the rescue!) Not only does music get synced, but playlists, collections, MIDI mappings, and settings do, too. Now, you could use something like the ubiquitous free command line utility rsync to do the same thing, but SugarSync has the advantage of giving you cloud storage, too, so you have an additional backup and always-on access to your files.

Traktor is just one example. You could do the same with any other essential files. Josef also syncs Max/MSP patches for monome, plus a promising-looking, in-progress wifi controller. File sync in SugarSync works across Mac, PC, and now iPhone, Windows Mobile, cell phones, and Android. (One gripe: no Linux support, something DropSync can muster.)

Synchronize multiple collections of Traktor PRO automatically

Before this becomes a SugarSync ad, though, I am interested in what other solutions people are using. There are various cloud storage and sync services. SugarSync is fairly unique in providing both true sync/remote access with cloud storage. But maybe you have added your home server to the mix, or found another solution.

Josef seems to be the perfect geek DJ – check out his iPhone-MIDI hack and (while not musical) iPhone R/C car control.

When software has “Live” as its name, you know control will be everything. So it’s great that many control surfaces will behave intelligently out of the box with Ableton Live, including devices like the Akai APC40 and Novation ReMOTE SL. If you’ve used one of these products, you’ve no doubt been able to click a device rack in Live and have a blue hand icon appear in the title bar, automatically assigning, say, the first eight macro knobs in a drum rack to your eight hardware encoders.

But what if you have hardware that isn’t covered by this functionality that you want to use? The easiest solution is something called MIDI Remote Scripting. It’s been available since Live 6, but it seems not many people know that it’s there or how to use it. It’s not a perfect solution, but it’s such an easy hack that it’s worth at least exploring.

For this tutorial, I’ll take the example of the Korg nanoKONTROL and nanoPAD. They’re a likely candidate, at about US$60 street each and with some handy controls (kontrols?) for mixer channels and drum racks. But you could take any hardware and apply the same technique — even something you’ve built yourself — so long as it sends simple MIDI messages.

The upshot: you get simple “automap” functionality without something specific like Automap (or drivers, in general).

Required for this tutorial: Ableton Live 6.x or later. I’ve tested only the full version of Live on Mac and Windows, though I think at least some of the “lighter” versions should work, as well.

This is a long article but a relatively short and easy process. I’m just giving you everything you could possibly want to know about the nanoSERIES and MIDI Remote Scripting!