It’s Richie Hawtin Watch time! The latest: NI teases an upcoming DJ controller by sharing video of Richie playing it in a club. The surprise: it’s actually what he’s doing with Maschine that seems most interesting to me. And if you recall the Twitter DJ app that he promised in the spring, it’s here, ready to use so long as you have Traktor and a Mac. (If you’re reading, Richie, do let me know if I’ve gotten my facts straight…)

Native Instruments yesterday pointed me to a video they’ve posted of Richie Hawtin DJing at Berlin’s lovely Saturday Adventure Club. The point of this is, of course, to tease an upcoming DJ controller they intend to announce in detail in November. You can already tell a lot from watching the video: it’s a hardware controller (or two chained together) that focuses on the Traktor working method. That is, there appears to be an emphasis on control of multiple effects, and cue and loop points, and it seems you can control Traktor’s full four decks. (At least, that’s what I get from squinting at the video; I could be wrong.) Regular Traktor users may be able to tell more, so … um, squint away.

To me, actually, it’s what Richie is doing with Maschine that looks most cool. He’s using NI’s drum machine to program in live beats and loop those, and it appears he’s then using Traktor as a sort of software DJ mixer / DJ source / effects unit. This shouldn’t be a big deal; in an ideal world, we’d have lots of DJs getting crazy playing their own beats atop their mixes and really mixing up the stuff they’re playing. Sadly, too often what you get is people playing tracks straight, which means you could just stay home and drink and dance in your living room. Richie’s sets do a lot more than that – and of course, what a lot of us are looking forward to is a rebirth of his original Plastikman stuff on tour, expected some time in the near future. If you’re interested in what he’s doing in his live sets, and his fellow minus mates, let me know and I can find out.

Before anyone complains about his line-up of gear, Richie was involved in the development of all these products, including the Allen & Heath mixer. So I would expect him to use the stuff!

In other news, the TwitterDJ app is now freely available, for Twittering tracks live from Traktor. The bad news is, the installation and setup is pretty involved, and it’s Mac-only. I like the idea – part of the vision of TwitterDJ is getting DJs reporting tracks they’re playing, so producers get paid when their music is played. And letting clubgoers discover tracks they’re hearing is also a great thing. I suppose the advantage of it being on Twitter is that it’s accessible to people at clubs with cell phones. But you do wonder if a Web-based format wouldn’t be better, and given that underneath is the cross-platform Icecast streaming server, it seems too bad to me that the app is Mac-only. Building networked apps is a perfect application for platforms like Java and Python. But don’t get me wrong: it’s great to see someone who plays out as much as Richie does experimenting, and sharing the tool he built. I’d like to know if the tool is open enough that other people could take it and adapt the idea to other platforms and servers / communication media.

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

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

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

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

xylobot run by monome from robb on Vimeo.

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

Project details

Debugging

Audio loop

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

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

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

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

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

Project Page

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

Hoping for a video of this, too.

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

I was one of the first people outside Native Instruments to lay eyes on Maschine, and immediately I saw something with real potential. Here was a software drum machine that was different: it was a real attempt to fuse some of the advantages of a software interface with some of the working methods of hardware. Software and hardware had really grown up together, instead of the latter simply being fitted to the former. And, of course, it had NI-style effects and UI look-and-feel, for fans of the software house’s style.

But 1.0 releases are a funny thing. As someone who spends a bit of my life developing tools, you always wind up with a choice of delaying the release, implementing something partway, or choosing not to implement it so it can be done properly later. And Maschine 1.0 lacked for me the one thing that was really essential to workflow – proper MIDI input and output support. Without that, I felt it was difficult to even give it a fair test. You’d wind up getting hung up on what was missing.

Well, good news: Maschine 1.1 gets all the little features I feel are essential to making it a viable and valuable part of the production workflow. It’s in public beta now, and I’m giving it a proper test. But here are the current changes in the present build, which includes all of the major items on my must-have list:

MIDI Out Mode for sounds
MIDI In for sounds and groups
Drag-and-Drop audio export for scenes and patterns in host
Record and trigger scenes switches via MIDI notes in host
Scene retrigger option in plugin mode
Loading groups without patterns
Additional slicing sizes (1/8th etc.)
REX file import
Scene naming
Adjustable metronome volume
Record Count-In option
Quick adjustment of group and sound volumes on controller

MIDI capabilities mean, for instance, you can throw Maschine into your host of choice (including the popular Ableton Live) and make really use of it. And you can drag and drop audio with the host, as well. The ability to have more slicing sizes is absolutely fundamental, as well.

Stay tuned, as this is just a first look at what’s in the beta.

http://www.native-instruments.com/index.php?id=publicbeta [Public beta signup]

The usual disclaimers apply: you need Maschine 1.0.3, backup projects made with 1.0.3 before opening in the beta, once you save a project with the beta, it can’t be opened in earlier releases (though it sounds like it can be opened in the final 1.1.0), and don’t expect technical support – expect to fill out bug reports! That’s what makes it a beta!

Also on the NI front, there are some excellent new Ableton Live templates for the KORE controller – yes, KORE, not Maschine – recently added to the KORE build, so I hope to cover that, as well. What I want is a Native Instruments Timepak(R). Add it to your existing KOMPLETE(R) or KORE(TM) setup, and instantly have more time for sound programming and less need for sleep – aka SCHLAFEN(TM) and – what I often get – SCHLAFEN LE.

Pronunciation of some common music tech terms has been a source of debate. Generally, though, there’s only one right answer. I had hoped to kick off a pronunciation guide yesterday or today, but now I really can’t resist – not with none other than Tegan & Sara getting together to debate the right way to say Moog.

Don’t get me wrong. I love cows, and the sound “moo.” I suggest if you have something you want to name Moo, you should, like your own MooVerb max patch or something. However, here goes, a few of my favorites:

Moog: Rhymes with “brogue” or “rogue,” not the sound a cow makes. Don’t say “Moooooog” unless you want to get funny looks from synth nerds, or if you’re teaching synthesis to livestock in a dairy.

Monome: The community-based, (partly, at least) open-source controller rhymes with “MA gnome,” not the Spanish-sounding “Ma gnome ME.” You should not be able to use it in a couplet with paper mache. Get it? Two syllables. Sure, this pronunciation varies, but the two-syllable version is what the device’s co-creators call it.

OSC: Pronounce the letters of the open communications protocol, as in “O.S.C. / oh ess see”, not “osk” – though that would have been kind of cool. Think, “Rah, rah, rah, Give me an O! Give me an S! Give me a C! What’s that spell? Better than MIDI! Time-based messages, higher resolution, transport-independent high-speed networked communication with auto-discovery, gooooooooooOOOOO O.S.C.!” (People sometimes say this site is geeky. I have no idea what gives them that impression.)

And for now, O.S.C. stands for Open Sound Control, even though in one spot on the JazzMutant website it’s called “Open-Source Control.” Just get ready for this to change – because OSC really isn’t specific to sound, it may need a new name, like Open System Control. (A recent paper suggests dropping the “sound” in the name.)

MIDI: Rhymes with G. Gordon Liddy, or P. Diddy, or Tweetiebird saying “Piddy.” And, actually, it occurs to me I’ve never heard anyone mispronounce this. Fascinating – an acronym that’s actually intuitive. Oh, but “C.C.” stands for “Control Change,” NOT “continuous controllers” — look at the CC specs; most aren’t continuous. There. I got to be anal about something anyway. Updated: consensus is actually that “mee-dee” is a mispronunciation for native-English speakers, but likely makes more since than “mi-dee” in other languages — particularly if you speak French. So, in other words, it’s an acronym, and makes the most sense to pronounce in the natural way you would in your native tongue. (For English speakers, who knows what vowel sound is appropriate given how screwy our language is, but the creators of MIDI all say middy.)

Maschine: Native Instruments’ drum machine software and controller is German-engineered, so say “muh SHEEN uh,” three syllables, as if you grew up in Berlin. Now, granted, Maschine’s own promotional videos — outsourced to the US — anglicize this to “machine” / “muh SHEEN”, but the engineers and product folks who built the thing use the German pronunciation and think you should, too. And, anyway, it sounds cooler, just as I have to admit a currywurst is tastier than a Nathan’s dog.

I’m sure this is only a small selection of potential mispronunciations. Other candidates? We’ll have to release a full pronunciation guide soon.

Can a software/hardware combination be as tactile as standalone gear like the MPC, but do, you know, computer-y things, too? That’s the question posed by Native Instruments’ new Maschine.

My Maschine just arrived in the mail, but one look in my inbox and I find that the folks at AudioMIDI have beat me to shooting a hands-on. What you see immediately is that you have immediate, hands-on hardware control of everything. With software behind that, that could lead to a lovely melding of hardware-style manipulation but software-style flexibility.

Conclusions of the AudioMIDI vid:

• Feels great; feels not cheap
• Roland-style step mode
• On-the-fly sampling
• Performance-style controls

Since AudioMIDI did shoot their video first, here’s your chance to say what you’d like in the CDM video. What do you want to see? What questions do you have?

And MPC fans, let me put it a different way: what would you have to see to be impressed by this?

Update/Clarification: Since this seems to be a point of confusion for some readers, both NI and AudioMIDI have confirmed that this isn’t an official review or special NI-sponsored promotion. This is a retailer excited about a box they got in the mail grabbing a camera and showing some initial impressions as they started using it. I am glad we put this up, though, because we’re getting some great feedback from all of you as far as what details you care about. So keep that coming, as I think I’ll be able to answer all those questions.

Maschine: It Has Hardware MIDI (Sort Of)

I’m only going to say one thing about Maschine: it has hardware MIDI inputs and outputs. A number of folks missed this yesterday.

This to me is a big deal, because Maschine is a really strong sequencer. I still want software MIDI output, so I can drop Maschine as an instance in Kore (or Live, for that matter) and drive soft synths or Reaktor patches or whatever. But while we’re not getting that in 1.0, we are getting MIDI output, so it could be an excuse to drive hardware synths.

Unfortunately, here’s the current situation: the MIDI output ports are only used when the Maschine is in controller mode. You have to be plugged into the computer to use that mode, because Maschine relies on the computer driver for MIDI output. And the sequencer can’t currently transmit out on the MIDI jack. So you do get controller features – meaning you could use as a controller for a hardware sound source, which is good. But as with software MIDI, we aren’t getting real output yet for the sequencer. I’m holding out hope we’ll see this in an update, which is possible – that’s the advantage of doing everything in software.

Akai APC40: It Doesn’t Need Max, It’s Not a Monome … We’ll Test to See If You Lose Your Place

You do not need a copy of Max for Live to get bi-directional control of Ableton Live with the APC40, or even to create custom mappings. In fact, it also sounds as though you don’t need Live 8, though I need to learn which features may be sacrificed in earlier versions. (In fact, word is Live Lite 7 will ship with the APC.)

I think the confusion was that Max for Live will ship with a patch for the APC. The APC won’t ship with or require Max for Live. And Max for Live might as well ship with a monome patch. (I expect by the time M4L is out, monome patchers will have ported a few of those patches so you can use a Live-style interface. Or you can do it yourself.)

For a quick hands-on, Lee Du-Caine did get to try out the APC on the show floor for Computer Music / MusicRadar. It’s nice that he sussed the controls immediately.

This is not a monome. Yes, you can use an example Max for Live patch to perform some sequencing tricks on its pads, and yes, that’s cool. But the real win is Max for Live, not the APC necessarily. If you really want a grid of pads to use as a customizable sequencing instrument, what you want is a monome. You can pick it up easily, move it around (with accelerometers, if you like), and it doesn’t have lots of faders and encoders getting in the way. And my sense is, while monomes were ridiculously hard to get in 2008, that won’t be true in 2009 – particularly with work on the arduinome clone. No, the big news there is that all the features monome inherited from Max patches can now be ported to run “natively” in Live, and by the end of the year once Max for Live has shipped, we should start to see monome take on Live-controlling powers it never had before.

One area to watch in testing. I’m a little concerned about feedback as to where you are and what you have selected, which is critical in a device that selects clips and parameters dynamically.

Good: A red outline on your computer screen in Live Session View shows you which clip you’ve selected. This must have made it into the current build, as Lee notes that he saw it there. (I’m hoping, actually, we can do this even without the APC in Live 8 – I’ll find out.) Good: The new magnification option in Live 8 should make it easier to see what you’re doing on the screen. Not so good: My biggest concern is that one of the nicest features is being able to dynamically select a rack and map the eight parameter encoders on the bottom right to that Device. I use this all the time on my Novation ReMOTE, but I have to select racks with the mouse. Akai gives and taketh away. They give you the ability to select devices with buttons on the device – no mouse needed. But that means you need to know which device you have selected, and which parameters are mapped, and you can’t, because there’s no screen.

I’m holding out hope that the magnification feature will compensate, but it does mean you either need to limit your devices to a couple you can remember, or look up at your computer for reference. And even there, Novation wins again for me with their implementation – Automap now has a huge heads-up display to show you what you’re manipulating on the computer screen so you don’t have to squint at your laptop, but you can use it for feedback. Kore has something similar, in which just touching a controller tells you what it is.

Anyway, enough ranting about that – I’ll test it and let you know if my fears have some ground. The rest of the layout still looks fantastic, of course.

And I do think the APC could be amazing controlling software that isn’t Live – like visual software.

If you could have an ideal drum machine and sample-slicing workstation, taking the physical control of hardware but the flexibility of software, what would it look like? We talk a lot about hardware control of software, but hardware usually comes second – software gets designed first, and then either you have to figure out how to map hardware to it, or someone else comes along and designs gear. That means there’s usually a disconnect in the design and workflow of the two, and most of the time, you have to reach for the mouse to make up the difference.

Maschine (pronounced as the German, mah-SCHEE-neh) was developed at Native Instruments with the goal to design the hardware and software simultaneously, not separately. That’s not an easy goal, and I don’t expect Maschine to be perfect or please everyone. But I got to visit the prototype at NI while I was in Berlin in October and see it in action, and I can say at the very least, the folks who created feel the way many of us do – they love software, they love hardware drum machines like the Elektron, and this is an attempt to be a real hybrid.

So, while contrary to rumors, NI does not have a box that does any audio generation in the hardware, this is a real attempt to fuse the controller and software in terms of design and workflow. The idea is to use the screen for visual feedback (you do have this big, pretty monitor on your desk or notebook), but to be able to work without a mouse.

Maschine can also work as a plug-in as well as a standalone app, depending on how you like to work (or how you want to play live). That means if you’re already in love with something like Ableton Live, you ought to theoretically be able to put the two together. Unfortunately, you can’t yet use it as a sequencer to drive other software, which would be an ideal next step; sequencing is as big a part of what Maschine does as sampling and sample manipulation. (No official statement on MIDI output has been made yet.)

Maschine’s hardware also works as a controller. So, for those keeping score, you could put Maschine next to the just-announced Akai APC40 and use them both to control Live – or Maschine could compete with the APC for your Live-controlling dollar – even before you touch the Maschine drum machine software.

Here’s NI’s intro video, which gives you a sense of how this stuff ties together (and we are officially the first to post it).

We’ll naturally be looking more closely at Maschine soon (I’m going to buy a new espresso maker and not sleep for the next few months). Here’s a quick overview:

• 16 pressure-sensitive pads, which light up for visual feedback
• Step sequencing
• Polyphonic recording (so it is a real sequencer, too)
• All software features are available quickly “on the surface,” so not only do you not need the mouse, but unlike a lot of hardware and even controllers, you don’t have a bunch of submenus and buttons to press to do stuff. That includes tasks like automation editing and even sound editing
• Automatic sample mapping, beat slicing, note repeat
• Real-time audio recording and resampling – so you can not only record, but resample what you’re working on, MPC style
• Effects sends “from conventional to experimental” (basically, you can enjoy the kind of sound mangling goodness we’ve had on Kore and Reaktor lately)
• Kore-style sound browsing, with a multi-gig library to get you started

Availability: April 1

Pricing: US$669 list (EUR 599)

The hardware has a top-notch feel and metal casing; at least from what I could judge from the prototype, this should look and feel absolutely fantastic. My only real disappointment was that there’s no synth engine, but that’s just because I love drum synths. Then again, I love the simplicity of Maschine, so perhaps the best fix would be to add the ability to either host plug-ins, as Kore does, or to provide MIDI output capability to other software, so that you could drive synths and other creations. (Heck, you could even sequence visuals in that case.)

What’s unique to me about Maschine is that it isn’t simply an emulation of an MPC; it still takes a software approach to sequencing, it still supports plug-ins and the things you like about software, and it still has NI-style effects. By virtue of being software, in fact, you can really change how you use it relative to hardware. You can drop it in Live or even in a tracker like Renoise. You can use it not as a drum machine but a pattern-based effects unit and insert it after your voice or an instrument. Then you can switch to a VJ set, ignore the Maschine software, and use it as an intelligent plug-in for running live visuals for your friend’s band. None of this is nearly as practical with a conventional hardware drum machine – and this is a whole lot cheaper.

Also, unlike some attempts to unify hardware and software in the past, the visual relationship isn’t slavish. You see something that looks like it makes sense on a screen when you’re editing; it looks like software, but you can easily control it with hardware and not the mouse. (Nothing against the mouse – it’s fantastic for many jobs; sample slicing and music editing just happens not to be one of them.) When you’re ready to perform, the displays on the device mean you don’t have to look at the screen at all.

It’s also worth noting that this is very different from today’s Akai APC announcement. The Akai is clearly better suited to mixing and clip triggering, but the Maschine has velocity-sensitive pads the Akai lacks, and is better suited to hardware control of beat slicing and editing operations. (That said, someone may decide to use Max for Live to turn Maschine into a hybrid machine that also controls and edits Live itself, so everything is suddenly wide open.) And the APC is all about a host (Live), whereas Maschine is all about adding a drum machine / workstation to a host (which could be Live, or Renoise, or Pro Tools, or something else altogether).

In fact, to me, the real competition is Ableton Live’s Drum Racks, groove extract, and slice to rack features. It’s mouse-based, but it also integrates with a host and can host plug-ins itself. I’m personally excited about using both, so it’ll be interested to see which I wind up preferring for which tasks. And you can meanwhile bend your brain around the idea of Maschine instances running inside Ableton Live Drum Racks and other odd combinations.

If there’s any criticism of Maschine, my guess it that it’s likely to be criticized for over-simplicity: as opposed to the first release of Kore, the approach here is really minimalism; NI did less in the hopes that you’d get more out of hardware integration, and the rest you can make up by working with your favorite existing tools and plug-ins. That’s not to say it’s dumbed-down, from what I can see, though I just have to use it.

Whether NI has nailed this one is another question, of course, and one I’ll want to test vigorously. But I love the idea. Mainly, I just want to get my hands on one so we can try this out. You’ll definitely want to stay tuned.

http://www.native-instruments.com/maschine.info

Corrections: In the first draft of this story, I suggested that Maschine could output MIDI to other software instruments or host plug-ins; at least as of version 1.0, the software can’t. You can use it as a controller, though, and output MIDI to other hardware (so you could sequence hardware synths or even other drum machines). The thing I’d like to see there is MIDI output to other software; we certainly have enough hosts (NI’s Kore being one of those hosts). I also overstated the connection to Kore (which is why I was confused about plug-ins). Like Kore, Maschine is integrated hardware and software, it shares the Kore browser, and it shares some of the other design features of the current generation of NI software. But Maschine is its own creature – and honestly, that’s a good thing. Stay tuned for more details.