Not all users upgrade to the same version at the same time – least of all when it’s a paid upgrade. So, it’s welcome to see that a number of improvements and fixes are making it to the previous version of Live, 7.x. Not only does CDM count numerous Live users among its readers, but users of 7.x are especially frequent, and we’ve been getting your questions – like whether you’ll be able to use the Novation Launchpad controller.

John Kuan, DJ and “culture industrialist,” alerts us that release 7.0.18 brings a lot of improvements, including:

• Support for the Novation Launchpad, Akai MPK line, and improvements for the APC
• Major bug fixes for the APC40 and Novation Remote SL under Mac OS (something I think I’d seen people complaining about in comments)
• Major, bug fixes for show-stopper crashes

There’s even an M-Audio Axiom Pro fix in there. In short, if you’re using 7.x, it looks like you want this upgrade. Full details on the Ableton forum:

Live 7.0.18 change log

And yes, this news is from last week, but it’s news to me.

In LA’s DubSpot Live 8 Sessions, I shared a panel with Daedalus, talking about design, live playing, the monome, and how limiting tools for performance can be powerful. Austin gets its own cast of presenters this weekend.

Sadly, I can’t be in all places at once. If I could, I’d be in Austin – twice over – this weekend. Handmade Music session two hits with an all-new set of learning and noise-making. Whether new to electronics making or an old hand, there’s something to absorb from some of the best mad sound scientists in the world. And our friends at DubSpot are in town, too, with a big lineup of production, recording, and performance techniques centering on Ableton Live 8. And on top of all of that, the city is host to the brilliant art + sound East Austin Studio Tour – a fantastic idea coupling events, studio tours, and art exhibitions I hope we steal in cities like my home New York.

This is all of interest to a tiny fraction of a percent of our readers since it’s really relevant only if you’re in Austin, but therein lies my plea — if you are in Austin, we could use your help documenting this weekend’s events. Get in touch, and we should be able to hook you up with a free pass for the DubSpot event, plus — well, whatever I come up with to thank you for videoing and/or writing about Handmade Music.

First up, Handmade Music:

This sunday is Handmade Music Austin #2.

We’ll be building 4ms’ Autonomous Bassline Generator. The upper division class is filled but there should be some space in the beginner class. Even if there aren’t any seats available, there will be all kinds of things happening in the gallery space for EAST. You can play with the Thingamagoop 2, Eric Archer’s noisemakers, Andromeda Space Rocker kits as well as other handmade instuments.

Noon – Gallery space opens. Bleep Labs, Eric archer, and friends interactive exhibit.
4 pm – Free beginner class
6 pm – Upper division synth class $45 at door
6:30 – Free performances :
Red X Red M
Douglas Ferguson/Steve Marsh
TelepathiK Friend

Red X Red M
Douglas Ferguson/Steve Marsh
TelepathiK Friend

As always, see:

http://handmademusic.noisepages.com

DubSpot’s event includes two full days of programming covering production and performance. It’s about Ableton Live 8, but it’s also more broadly about how to make your tracks sound better, how to get them into the world, and how to be successful as an artist both in your releases and live. Austin includes many of the folks I’ve been hanging out with in NY and LA, plus favorites like Ableton veteran sound designer and Keyboard contributor Francis Preve. Christopher Willits will also take a first look at Max for Live and talk about how he uses Max/MSP to process his playing. And Saturday night is a FunkAid benefit with DJ OBaH, Ocote Soul Sounds, Akina Adderley & The Vintage Playboys, and Daetron Vargas.

I expect we can get a guest in if you cover the event for CDM.

http://www.dubspot.com/abletontour/austin.html

A new, free software release for Novation’s Launchpad could make your device a lot more usable – and it shows how useful OSC can be for hardware, even if that isn’t OSC hardware. (Now, imagine what OSC-native hardware can do.)

There are plenty of misunderstandings about OSC and the monome out there. Among them, there’s the notion that OSC won’t work without “extra software,” or that the only reason to use OSC messages with something like Novation’s Launchpad grid controller would be to emulate a monome.

Here’s the secret: even if you still don’t know what OpenSoundControl is, the idea is to make messages readable.

Novation released the MIDI message mappings for its Launchpad — that’s a good thing! (See previous post.) But because of the utilitarian and somewhat arbitrary way in which MIDI describes devices, MIDI messages just aren’t terribly readable. For instance, one button is called 50h (in hex), or 80 (in decimal). Where’s 80? Uh…. yeah, no one knows. And simple grid devices like the Launchpad and monome illustrate just how abstract MIDI is. The Launchpad has an 8×8 grid of buttons. You might expect them to be numbered from 0,0 to 7,7, or 1,1 to 8,8. But that’s not actually possible in MIDI.

Will Crossland to the rescue. He’s been working on an OSC wrapper for the Launchpad in Max/MSP (easily ported to other environments if you like). This makes the Launchpad more usable and more logical. It’s just one of what I think could be plenty of efforts to use arrays of buttons on music controllers more fluidly and flexibly. That, in turn, could take the DIY musical ingenuity shown by the monome community to the next level.

Oh, and Will even has an open MIDI networking tool, also built in Max – relevant to the earlier discussion of the day.

http://www.chippanfire.com/SoccoChico/Software

Will’s full description follows.

I thought you might be interested in an OSC wrapper I have been making for the new Launchpad.

From the off, this IS NOT simply a way to make the Launchpad act like a Monome. Oh no. This is a wrapper for converting the MIDI communication provided by Novation into a more human readable (and memorable!) OSC formatted protocol. Additionally the wrapper incorporates a banking system that provides one layer of unaltered MIDI communication (for connection and use with Ableton Live, with all the expected features in-tact) and eight layers (switchable from the Launchpads surface) of OSC transmitting (and controlled) decoupled grid action.

The wrapper is based in MaxMSP, but uses it only for selecting MIDI IO ports, udp communication to the ‘localhost’ (via netsend/netreceive to make it Pd compatible) and a single [js] object with the actual handler/wrapper inside it. Oh, and there’s a local loopback function for testing you have the write MIDI IO selected for each Launchpad you hookup… The wrapper (theoretically, not that I own a fleet) supports up to six Launchpads, each uniquely addressable. If you get really greedy, the javascript could be altered to support more; it is just a 3d array of data elements at its core, currently limited to [6] in one dimension…. The limit of six is a reflection of the maximum number of control surfaces Ableton Live supports.

Specs at a glance:

– Supports up to 6 Launchpad devices, each individually addressable via OSC/MIDI
– Retention of the default MIDI mode for use with Ableton (via internal midi bus)
– 8 OSC mode ‘user banks’ (per device) where the Launchpad (well, technically the wrapper) sends/receives OSC using a markup similar to that used by another popular ‘grid’ device [though it does not directly support Monome markup, as row/col/frame etc messages are not used)
– user bank switching from the Launchpad via top row of buttons
– retains all data received on any bank (even if the Launchpad is not currently focused on it) and updates the surface accordingly when swiching banks

As the handler magic is ALL done via a single javascript file, ANYONE can edit the functionality in their favourite text editor. You then need only MaxRuntime to run the code inside. While this is not an ‘open-source’ solution by any stretch, it can at least be tailored to an individuals needs without spending any money. As the wrapper will communicate happily with Pure Data, an avenue exists for freeware development of OSC patches that use the Launchpad as an interface (via the wrapper).

The appropriate files (along with suitably concise/detailed) documentation can be downloaded from my website (http://www.chippanfire.com/SoccoChico/Software)

Finally, the OSC protocol I have used is fully detailed in the download. It is essentially an extended version of the basic subset (i.e. /press and /led) employed by the Monome. My intention is not provide a ‘Monome Emulator’; the similarity in protocol is both a courteous nod to the Monome creators, and logical progression. The Monome OSC protocol is clearly well thought and well suited to addressing a 2D grid so why reinvent the wheel? I’d expect any sensible grid based OSC controller to use a similar markup as the original is so well thought out…

I have added extensions that allow for the multiple device/multiple bank addressing, as well as some extra ‘data’ for the extended colour set available to the LEDs. If you want to use the wrapper with Monome apps you’ll have to get your hands dirty converting between the two OSC protocols (not that that would be too difficult). The lack of support for /row, /column etc messages is just one example of why this is technically an inferior device to the Monome; that said, i’d still be making a wrapper like this for the banking/multiple device features it enables if I had the budget to buy such a beautiful device…

p.s. Where I am saying OSC, at this stage I really mean ‘OSC formatted’. The implementation is limited to using the netsend/netreceive objects in Max (which perhaps limits their reception to Max/Pd?). I’m a bit too new to using OSC to say I am ‘definitely’ sending Full Packet Messages that could be picked up by any OSC client…. I’d be happy for someone with more know-how to take the final steps in making it truly OSC compliant…

I imagine this could generate plenty of feedback, so fire away.

Laptop musicians are feeling out of sync — literally. But we can work together to help the situation.

Computer music making can be an isolating experience. But when users try to use their eminently-mobile tools to play together in the same room, they often find that the technology resists. MIDI, as a serial protocol, isn’t designed for networked environments. Software interfaces are designed to be visible to only one user. Sharing between users rarely figures into designs. Input points are made to be single-user only.

And most importantly, just getting a couple of computers to sync can be a Herculean task — one that seems to have gotten worse with advanced computer software rather than better. In short, for all the technology we have today, we’ve actually regressed from the state of interoperability 20 years ago.

I’ve been hearing more and more frustration over sync, as people begin to collaborate with multiple computers as they would with a small ensemble of instruments. Ableton Live is the most frequent example, but it’s only one case – and I suspect part of the fault is that people are more likely to try to sync multiple copies of Live. When I spoke to Depeche Mode’s Martin Gore in the spring for Keyboard, Martin complained that they had trouble syncing his Apple Logic sessions with other band members using Pro Tools and Ableton. This weekend in Los Angeles at the DubSpot sessions, Glitch Mob’s Justin Boreta talked about the issues that group has had with multiple copies of Live.

Synchronization is, by definition, a tough thing to do. But musical engineering is replete with challenges; it’s no longer acceptable to simply say “live with it” and walk away. It seems we need both better shared knowledge about what sync is how to make it work, and better engineering solutions on the software and protocols side to support the way users want to work. And yes, we need a new sync standard that goes beyond what’s presently available in MIDI alone.

Focusing this discussion, I just got an essay in my inbox that I think focuses the issue. I will try to speak to Ableton’s engineers about the matter, but this isn’t really about Ableton alone, so I’m posting it here first. We could use more data about how you’re working with various software and hardware, what techniques you’ve developed, and what frustrations you’ve had. We have a wide community here of users and developers (and a whole lot of you are both).

Mark Kunoff writes:

I’m writing to you today about an issue which I believe has been a sore spot for many Ableton Live users – *reliable* syncing of two or more computers – particularly for those of us who are attempting to sync for the purposes of *live performance*.

My musical partner Patrick Petro and I (together we perform as “Othership”) have been struggling with this issue for several years now. At present time, we have a decent solution using midi time code. Initially we attempted to use Midi “clock” but our friend Steve Duda (partner of Deadmau5 in BSOD) informed us, “using Midi clock is as reliable as syncing to a boat motor.” He informed us that in BSOD, he and Deamau5 have reliable sync between their 2 laptops using MTC, although the main drawback is the inability to fluctuate tempo – you must run at a consistent tempo the whole time. (You may be aware of this already, but Steve is the person responsible for ‘Molar’ the incredible step and loop sequencer for the Monome, was a programmer for Devine Machine and has worked for many renown artists in the music industry such as Trent Reznor. We are very fortunate to benefit from his consultation!)

Currently we are both using Macbooks and syncing via Ethernet with Audio File Engineering’s “Backline” app to generate MTC. This method has been about 95% reliable, but after reading an article on Ableton Tweets (http://abletontweets.com/post/126300941/why-midi-sync-over-ip-may-not-be-a-good-idea and our response – http://abletontweets.com/post/224247258/midi-sync-in-ableton-live-why-so-complicated) we are going to acquire a dedicated external device to generate MTC such as a Motu Timepiece.

I feel strongly that Ableton has not addressed these issues sufficiently and could do a better job of educating their user base as to the challenges that face performers in achieving reliable sync. I’m not expecting a walk in the park, but as of yet Ableton has not provided comprehensive documentation regarding these issues and places most of the responsibility on users to figure it out for themselves. We are (and have been) perfectly willing to educate ourselves but for the most part this issue remains elusive to the majority of Ableton Live users.

The Ableton Live forum posts regarding sync are fraught with dissension and are excruciating to read to say the least. I feel I’m empathetic to the complexities of programming audio applications, but in my estimation Ableton tech support’s explanations toward this issue have been mostly open ended. Many users report these issues only to report back that Ableton’s tech support doesn’t respond. I have experienced this as well. Certainly there are enough customers who want a better solution.

I feel it’s time to launch a concerted effort to organize users and demand that Ableton addresses this issue once and for all. Perhaps this solution wouldn’t even involve midi at all. Ideally this would be an open protocol such as OSC, but I wouldn’t be opposed to a proprietary solution – just as long as there is a reliable one.

The main purpose of this correspondence is seek your and CDM’s assistance in sponsoring an effort to encourage Ableton to address this issue once and for all. I feel CDM could be quite helpful in garnering leverage toward this effort (a simple blog post, or ideally a dedicated section) to organize users and to demand better sync ability between two (or even multiple) laptops running Live – even from unlike computer manufacturers. I’m sure you know artists with valuable expertise in this area.

Even if the issues regarding sync via midi are insurmountable, there have to be CDM readers who have developed reliable methods of two or more persons performing with Ableton Live and it would be great to have one centralized portal where discussions of working methods can be discovered.

Thank you for your time.

Again, my personal intention is not to single out Ableton — I’ve heard similar complaints about other scenarios, and moreover, I think the “open-ended” tech support response occurs when there isn’t an easy solution. Tech support alone often can’t deal with something as multi-faceted as sync, so it’s time to engage other users in this, as well.

I’ve also spoken to Owen Vallis and other folks about how sync could be executed more effectively over network protocols, and specifically how the time stamp feature in OpenSoundControl might be used in conjunction with MIDI clock messages.

To kick things off, let’s comment here, but I’m also setting up a special Noisepages group for users to share experiences and tips:

Sync or Swim Group [noisepages]

(Incidentally, CDM contributor Matt Ganucheau is joining me Saturday at a WordPress developer intensive here in New York, so we’ll be picking up development techniques to work on the Noisepages community, too.)

Jump in, say hello, and let’s talk about how we can make sync work in real-life musical situations.

I’ll also be talking to more artists and developers about their experiences and suggestions, and will pass along your feedback, so expect a report back. In the meantime:

1. Are you routinely trying to sync multiple musicians?
2. What software (and hardware) tools do you use?
3. What have been some frustrations?
4. What techniques have worked, or what have you learned you might want to pass along to other users at various skill levels?

Max For Live Sneak Peak from max4live on Vimeo.

Suddenly, I have an image of American Ableton hackers patching on their MacBook over Thanksgiving turkey.

After a long, long wait, a public beta of Max for Live is available. The software incorporates the full version of Max/MSP/Jitter – complete with visual output, video processing, and 3D capabilities – with the Live host. Max patches operate with all their usual capabilities as devices inside Live. User interface elements are available to give Max patches conventional Ableton device interfaces, and there are even pre-built elements for useful functions like frequency displays and MIDI patterns. Via the Live API, Max for Live patches are also able to control most elements of the Live interface.

Because of Max’s networking capabilities, Max for Live devices can also be used to route OpenSoundControl data into Live. That isn’t necessarily with the same ease as you might route MIDI, and there’s still no native support in the Live interface, but it is a step forward.

Our friend Michael at max4live.info has been busy documenting the new software. His overview video is at top, and for OSC coverage, see his tutorial [part 1 | part 2].

Updated: Pricing has now been announced.
Max for Live is not included with Live 8 or even (perhaps surprisingly) Live Suite. It will be a US$299 / EUR249 download, available separately, on top of the cost of Live 8 or Live Suite 8. If you already own Max, you’ll have a set of crossgrades available:
1. You own Live. You can add Max for Live for US$99.
2. You don’t own Live, and want just Live. You can get that and Max for Live for US$449.
3. You don’t own Live, and want the whole Suite. Suite plus Max for Live crossgrade, US$699.

Total cost:
Max owners without Live: US$449-699
Live owners without Max: US$299 + cost of the upgrade to Live 8
Max + Live owners: US$99 + cost of the upgrade to Live 8

I think this could arguably be worth the investment, but given the discontinuation of support for developing VST, RTAS, and AU plug-ins in Max – a feature that was formerly free – I expect some resistance. Also, as previously announced, there is no known Max for Live “runtime,” meaning Max patch developers don’t really have a distribution outlet for work made in Max for Live, other than other Max for Live users.

Sign up for the public beta on Ableton’s site, and you’ll be able to grab the downloads (details below). You must be an Ableton Live 8 owner, though you don’t need to own Max 5:
http://www.ableton.com/maxforlive/beta

At the bottom of the page, you’ll have a direct link to download Live 8.1 (the official current build of Live is 8.0.9 otherwise), and a link to Cycling’s site to download Max. (Note: the Max link worked this morning, then promptly disappeared, so it’s possible they’re uploading an updated build is now back up.)

There are full instructions there. I was able to simply click a button and become a beta tester; hopefully you have the same experience. You’ll need to install two pieces of software, both Ableton Live 8.1 on the Live side and Max 5.1.

For the Python-based Live API, and the MIDI and OSC interfaces based on it, this should also come as good news. Live 8.1 should theoretically represent a more stable, feature-complete, fully documented version of the Live API under the hood in Live. That means even without Max for Live, it may be possible to, say, route an OSC input into Live as easily as a MIDI control surface.

If you’d like to join in with other people working on hacking Ableton Live and ask questions, try out our Noisepages group, which should now be functioning properly with a forum, wire, and networking features. More to come with this, with Max for Live, with OSC, with other tools, with… yeah, I’m glad I own a coffee maker.

http://noisepages.com/groups/ableton-hackers

As the company turns 10, Ableton has introduced a set of discounts and giveaways, the most notable of which is a new entry-level edition of Live. Live Intro smooths out a lot of the wrinkles between different starter versions of Live, from LE to hardware bundles. At $99, “Intro” finally gets a logical feature set:

• Full ReWire support, both as host and client (or “Slave” and “Master,” if you want to be all kinky about it)
• Full MIDI support, including remote control, output, MIDI clock (though none of the nifty “external device” support for outboard gear)
• Warping and time stretching, minus the “Complex” and “Complex Pro” modes
• 4 VST/AU instruments, 4 VST/AU effects per project
• Missing Vocoder, Looper, Multiband Dynamics, Overdrive, Frequency Shifter – but you do get SImpler and Impulse
• 2 in, 2 out audio, though you can have up to 64 tracks and unlimited MIDI tracks
• No track grouping
• Full WAV, AIFF, MP3, Ogg Vorbis, FLAC support
• New extras: 7 GB of audio content in the boxed version, 1 GB in the download version

In other words, you get a more-than-capable version of Live for a hundred bucks. It’s certainly enough for anyone who just wants to inject some Live functionality into their ReWire host of choice, and allows people interested in experimenting with Live a non-crippled version they can use. Mercifully, Ableton is offering a free upgrade to Intro from Live LE users — a good thing, because Intro includes some features and content LE lacks. (Okay, it’s still probably not great news if you spent $200 on LE, but at least you don’t miss out on the features.)

Live Intro product page
Live Intro comparison

Sound Packs, Discounts

Already a Live owner? Through January 10, Ableton has a number of deals for existing Live users:

http://www.ableton.com/able10

Discounts on Live upgrades, up to 20%

Free artist packs — from some wonderful artists, too, including Apparat, Mum, Thavias Beck, and our friends at Covert Operators, among others.

The artist packs are especially nice. And Novation is shipping the Launchpad. Of course, the big news today is really Max for Live, so I’d better … keep typing. (Damn you, fingers!)

Novation’s Launchpad, its affordable (<$200) "grid" controller, may have a big Ableton logo on it. But underneath, it's just a MIDI controller. Bi-colored LEDs, containing a red and green element for red, green, and amber output (amber = red+green), can be triggered using simple MIDI note and control messages. That means, whether you're looking forward to Max for Live or you're sequencing in a tracker or writing Processing sketches, you can use the Launchpad just like any other MIDI controller.

One of the things I thought was a major demerit for Akai was the fact that they failed to ship a MIDI implementation for the Akai APC40. MIDI implementations are the charts of MIDI messages we've had since the very first MIDI devices came out in the 80s. They're usually printed in the back pages of the manual, and even the cheapest gear has often had one.

Score: Novation 1, Akai 0. Novation has done the MIDI documentation, and then some. Its MIDI “Programmers Reference” is out even before the official Launchpad ship date. And rather than just doing a MIDI chart and assuming people know how to read it, they’ve taken the care to fully explain the way MIDI messages work, how to calculate the right messages, and how to really use this. Experts will have all the information they need, but newcomers will also find they can spend a little time and learn how to do what they want.

Launchpad Support with Downloads (see Programmer’s Reference at the bottom)
Via: Novation released Launchpad Programming Guide, and Protocol [Nezoomie's Zen Wave Blog - great read]

It’s listed as “for Max/MSP programmers,” but anyone using MIDI will want to have a look; that’s obviously relevant to far more than just Max. (In fact, there’s not a single mention of anything specific to Max in the document.)

What might people do with stuff like this? Well, as of just four hours ago, Matt DiFonzo lets us know he’s written a simple monome emulator. It’s even got a clever name:

nonome – monome emulator for Novation Launchpad

There’s some bad news mixed with the good. Even with something as simple as a grid of buttons, MIDI isn’t as friendly as it could be. I still would like to have a MIDI editor for the Launchpad so you can reassign buttons if you like — that’s a feature, incidentally, available on rival Ohm and Block hardware from Livid Instruments. Also, the documentation reveals that Launchpad uses “a low-speed version of USB,” which runs at a maximum of 400 messages per second, thus taking 200 milliseconds to update a Launchpad’s LEDs. (There are some workarounds, but they’re … more work. Clarification: Once you double up messages, though, you can get this to a more acceptable gap, and that’s for updating all the LEDs, not the latency of input messages.)

Also, here’s a hint to Novation: use a Creative Commons license for that document. That way, your users will be free to document even more ingenious solutions and friendly guides. You win, and your users win. For instance, I have the illustration here, which I should be able to do for purposes of reporting on this story. But can I write my own how-to guide using your guide? Why not make it explicit to encourage me to do so? (They list the PDF as “proprietary,” though there’s no explicit license, and I think they just mean “proprietary” as in “what we’ve done on our hardware.”)

That’s a difference between open hardware and closed hardware, but I don’t even want to belabor the point — CC licenses are something a commercial company like Novation could easily use. In fact, if anyone at Novation or Ableton would like to talk to me about why I think it’s a good idea, I’d like to extend an open invitation. I’m no legal expert, but I can explain what it means to me as a user and developer, and connect you with some of the right people at Creative Commons and the CC-using community.

But those gripes aside, kudos to Novation for getting this documentation out here. I think it’s really good news for people experimenting with grid controllers. And we’ll be looking at how all of these tools, hardware and software, fit together, and how open source development can make them more powerful.

Patchers and coders and hackers: if you’re interested in working on interoperability between all this stuff, let us know.

It’s round, it’s mechanically-resistant, it’s tangible, it supports multi-touch and gestures. Yep – it’s the turntable, and outdoing it would mean reinventing the wheel, literally. And so it is that more than a few Ableton fans have wondered how they might work vinyl into their software axe of choice.

Ableton and digital vinyl vendor Serato have announced they’re doing “something,” and then announced at the beginning of October that an announcement would be announced on January 14, 2010 at NAMM. Oh, and they said it will “unleash your creativity,” which sounds good. (It’s better than, say, “Ableton and Serato’s creative partnership will unleash two dozen angry badgers,” or “if you own Ableton Live, what we will say in 2010 is that we will unleash an unspeakable, nameless evil, known only to the ancients, which shall bring about the endtimes.”)

Here’s the surprise – you likely won’t have to wait for Serato to get integrated digital vinyl control. It’s already working with Ms. Pinky, and that means more choice, more DIY possibilities, and a broader variety of ways to integrate turntables and Live.

You see, there’s this little thing called Max for Live, which allows the use of Max patches inside Live as seamless instruments and effects. And one of the best – if least-known – vinyl control systems out there has long featured Max integration: Ms. Pinky. People have already made use of VST plug-in integration, but because Max for Live also connects to the Live API for control of Live itself, the functionality of the two can be expanded.

Via our friend Luthier.Lab, we get a first look at the Ms. Pinky plug-in. And this should be just the beginning, as Ms. Pinky and its Max/MSP support could be a great construction kit for building your own solution – something that may not be possible with Serato.

Ms.PinkyforLive [Luthier.Lab - en Español]
Google Translate (which has some very funny ideas about how to translate Spanish)
Discussion on the Ms. Pinky forum

While you ponder the possibilities, it’s time for a video from Daito Manabe demonstrating that not all turntablists sound quite the same.

Given a choice between boring and crazy, I always choose crazy. After all, craziness is part of the artistic persona. So bring it on.

It’s been a while since we had a celebrity saying things that didn’t really make sense. It’d be unfair to ask Ricardo Villalobos live up to some of the titans – Bob Dylan saying CDs have “no stature” and “have sound all over them,” and Elton’ John’s classic call to “tear down the Internet.” (Not to mention, in the end I think we wound up agreeing with them and turned Elton’s quote into a brand-new verb.) As with Elton John and Bob Dylan, I love and respect Villalobos’ work, no less so as he says things with which I disagree. But Ricardo Villalobos does get special credit for claiming in a recent Resident Advisor interview, among other things, that what has really hurt sound quality today is the lack of cheap drum machines from the 80s, because they were analog. Or they weren’t, but it was as if they were. Or something. (If you think this might earn some ire from Ableton loyalists, you’re right.)

No. I think the development is going in the opposite direction because everyone is making tracks in programs like Ableton, which has an OK sound engine. When I started making music 20 years ago, you had to at least buy a mixer, then some synthesizers, a drum machine—which is the best quality possible of a sampled drum. There was a pureness of the source of the music. It was analog, direct.

Ah, yes, the good old days. Back in the day, digital samples of acoustic instruments played through digital-to-analog-converters were real digital samples of acoustic instruments played through digital -to-analog-converters. It was analog, direct – well, aside from the fact that it was digital and not direct, but it was real … um … analog … digital. Pulse code modulation was real, pure pulse code modulation, not like the pulse code modulation you kids have today. Not like now, when people don’t … own… mixers. It’s not like you kids today, you people who use Ableton, people like… Ricardo Villalobos. (Villalobos is, in fact, a notable Live user.)

I mean, at least it’s a novel argument. Usually, you get the “mixing in the box is bad” and “computers aren’t real” argument from crusty audio engineers with massive outboard analog mixing boards, not electronic musicians. Recently, many experienced engineers I’ve talked to have come to the side of accepting that “in-the-box” recordings in software can be just as good as their analog counterparts. So, we may have reached a real landmark, a world in which electronic musicians claim digital’s no good and turntables are the only way to listen, while engineers experienced with analog claim just the opposite.

Let’s go back in time. For the record, twenty years ago by my calculations would be 1989.

The drum machine you might have bought then could be the Alesis HR-16, or perhaps a Roland TR-707. They’re fantastic, unique-sounding instruments. But “the best quality possible” is not generally a phrase associated with instruments of this era. We love them because they aren’t 192kHz, 64-bit multisamples recorded from 30 microphones and shipped on a 100 GB hard drive, because “quality” isn’t actually everything. And if you bought a new mixer in 1989, I assume you picked up something like Mackie’s just-released LM-1602, rather than an SSL. Of course, you really could go do that now. In fact, Ableton Live recently added 64-bit processing in the signal chain; the software that does more aliasing to account for lower bitrates is actually Pro Tools.

He goes on:

The thing is, you have the limitation of the program, the limitation of the digital mixing which is happening inside the computer, you have the limitation of the sound sources of the synthesizers—the virtual synthesizers. Even the sound engine is playing a very big role in the whole sound of the product. If you have a good turntable and good speakers, you can hear it is made in Ableton. Logic, for example, is very neutral in sound but Ableton…you can hear it in two seconds.

It’s hard to know where to begin. Live does have an overused sound – but that comes from people using effects presets as-is, people not knowing how to mix, people time stretching and warping without adjusting settings or taking care to think about the impact on its sound.

The idea that you have to use a turntable to hear these things, or generally to hear quality issues in a track produced entirely digitally is… well, an interesting theory. (It’d be like testing the fidelity of your inkjet printer by first taking a Polaroid of the output.)

They have all of these virtual instruments that are calculated by a computer, and you have a certain space where you have to put everything. And when you want to leave this space, you have to live with compromises, the compromises of digital mixes and recordings.

Now, perhaps I’m wrong, but I thought that if for some reason you thought you needed to mix on an analog board and record to, say, analog reel-to-reel, you were no less able to do that with the analog outs of your MacBook Pro than with your 606.

And what exactly was in those vintage drum machines, if not a computer making  calculations? Eleven secret herbs and spices? Elves with slide rules?

But this is the beauty of interviews – you can say whatever you want. And it definitely beats boring.

There is also one statement with which I wholeheartedly agree:

People are finding it easy to publish something without any controls. And this is the problem with the internet in general. There is so much information, and no one knows if it’s true or not. It’s just there. It’s an information monster.

It’s almost as though the Internet is a place in which people can make any wild claim they wish, without anyone questioning its basis in reality or fact.

http://www.residentadvisor.net/feature.aspx?1128

The Covert Seq – Creating patterns and Presets from Bjorn Vayner on Vimeo.

The Covert Operators and Bjorn Vayner have become my favorite go-to source for wild Ableton Live hacks. And even before the release of Max for Live, Bjorn has built some terrific, simple step-sequencers using Live’s Racks feature. That’s just the Racks feature – no Max patches or hidden features anywhere to be found. Sure, I suppose the clip view itself can be seen as a kind of step sequencer, but this gives you a unique way of generating sequences.

If you just want to begin playing with step sequencing in Live, Bjorn has a new download, aptly called The Covert Sequencer, as seen in the video at top. It’s free, it’s fun, it celebrates the 5th Anniversary of Covert Ops and the 10th of Ableton Live (good grief!), and it’s all voodoo built with dummy clips and MIDI effects.

Full post, downloads, and video tutorials:
The Covert Seq [The Covert Operators]

If you want to try your hand at the ninja skills behind all of this, Bjorn posted a screencast back in August revealing his secrets:

Making a Step Sequencer in Ableton Live. from Bjorn Vayner on Vimeo.

And if you like this sort of thing, definitely don’t miss The Covert Operators’ exclusive creation for CDM, making elaborate use of the racks and slicing features of Live 7 and later:

Exclusive: Free Ableton Live Slicing Pack by Covert Operators

Slice of Winter from Bjorn Vayner on Vimeo.