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

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

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

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

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

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

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

www.native-instruments.com/traktorkontrolx1.info

multi-touch the storm – interactive sound visuals – subcycle labs from christian bannister on Vimeo.

What if you could mash, mangle, mush, and morph sounds with your fingers on a screen, watching the waveforms dance in response in three dimensions? That “what if” is expressed beautifully in a project by musician-developer Christian Bannister of Portland, Oregon, who works as Subcycle Labs.

The result is like being able to touch sound directly.

Three-dimensional forms morph and vibrate using visuals programmed in Processing, making architectural-organic shapes and spaces that really begin to “look” like sound. These forms can represent synthesis and effects parameters (Christian has done some work with the Massive synth from Native Instruments), or can allow navigation through loops using touch. Gestures remap offsets and duration for audio, scrub and slice, and apply granular resynthesis.

Controls use multiple touch points on a screen (apparently via Community Core Vision and reacTIVision), with sound from Logic, Reaktor, and Max/MSP, and auxiliary control with a joystick array and KORG KAOSS Pad.

Here’s what happens with a Massive bass line:

low frequency entity – subcycle labs from christian bannister on Vimeo.

It’s spectacular, gorgeous work, and I can’t wait to see more. It’s well worth reading through the whole description on the blog for more details, technical, musical, and artistic:

http://www.subcycle.org/

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.

It’s a strange and wonderful sampling instrument and live rig, capable of mangling and remixing live, synced to tempo. It’s proof that live computer performance doesn’t have to be in only one tool, or use one technique. It’s a ready-to-play, affordable instrument you can pick up and use. It’s a Reaktor patch gurus can pick apart and learn from, along with other resources from one of Reaktor’s masters. It’s a new blog and an opportunity to talk about live performance. It’s an EP release.

It’s actually all of these things – a tool, but more than a tool. The Finger, a US$79 / EUR 69 instrument, is a product, first and foremost, created by master live electronic performer and hacker Tim Exile. Tim is such a dedicated Reaktor user that he once managed to give himself a repetitive stress injury from connecting patch cords. (Not recommended.) You can run this thing out of the box using the free Kore Player, or get in deeper with a full version of Kore, or get into the patch itself with a copy of Reaktor 5 (also included in Komplete 5 and 6). It’s quite a product, too. I could try to explain it, but I couldn’t possibly do as good a job as Tim does in the video.

I’m not sure I agree with the marketing material’s claim that this is “a new type of live performance and remix effect.” In fact, Reaktor, Max/MSP, and other tools have led to all sorts of similar, original performance tools. Unlike going into a gig with just an Ableton Live set (something I’m doing in, literally, fifteen minutes), having a custom tool means focusing on performance techniques. And “new” hardly matters – Tim is a ninja at working with Reaktor’s deep sound DSP layer, Core (not to be confused with Kore). Whether it’s new or not, this is the ultimate patch from one of Reaktor’s masters. Along with Reaktor creator Stephan Schmitt’s Spark, it’s proof that sound packs from NI – or anyone else for that matter – don’t have to be limited to stock presets.

More than that, though, The Finger is connected to a music release by Tim, and is already triggering discussion of live performance and sound design – issues that go beyond any one tool. Tim has started a new blog to talk about his own take on live performance, starting with more info on his EP and some tracks you can hear:

http://thenowwave.blogspot.com/

Other folks I know have picked up The Finger and started to play with it, including the underlying Reaktor patch. Most notably, see Richard Devine transform The Finger from a Sound-Like-Tim-Exile machine into a Richard-Devine-Sonic-Insanity-Generator. (See, just because you use someone else’s tool doesn’t have to mean you need to sound like them.) With Max for Live coming, hackers getting smarter and slicker with open source tools like Processing, ChucK, SoundCollider, and Pd, and techno-literacy again on the rise – more connected than ever by these Interwebs – I think we could be in store for a really wonderful age of creativity, in which people make part of the craft of music making the craft of tool making, as well. Designing a tool, after all, is designing a system, in the same way that composition (in any medium) is about designing a system. Finally, instead of keeping that to ourselves, we can actually share the whole process.

In the meantime, let’s watch those videos, on Reaktor, The Finger, and more.

Richard Devine takes on The Finger:

Native Instruments The Finger vs Richard Devine from Richard Devine on Vimeo.

Tim Exile performing in Reaktor:

Tim shows his Reaktor-based setup – not just The Finger, but beyond:

Related tools:

Updated based on feedback in comments See also…

Sugar Bytes Artillery2, which focuses more on effects – and offers a whopping amount of effects variety, from step-sequenced buffer scratchers to vocoding. As with The Finger, the idea is to map effects to keys.

Rekkerd notes that Sugar Bytes has just discounted Artillery2 to 50% through October. Devoted loop manglers will buy both. I’m going to wait for a Richard Devine video in which he routes Artillery2, Lucifer, and The Finger together in one chain, then randomizes all the settings – your move, Richard.

The Lucifer plug-in is now discontinued, but Devine Machine offer a range of related looper/performance tools – from the practical tools to the manglers.

The basic ideas here I think are worth copying: making use of the keyboard to control things live rather than having modulation all running automatically, routing different effects together for mangled results, and loop recording and effects that are synced it time are all useful concepts to combine. I’d love to see people push those concepts in various directions, and the exact combination of ingredients you want is likely to be personal, so it’s well-suited to DIY concoctions, too.

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.

Code, hardware, and software: Hack Days are all about getting actual stuff made. Berliners, the Music Hack Day that took place in London at The Guardian now gets underway in Berlin this weekend. For anyone who thought the first event was overly Web-centric, there are some new players in Berlin. Ableton is a sponsor, and Ableton, Native Instruments, and RjDj are all presenting hack sessions (in addition to the more Web-focused / consumer-focused 7digital, Songkick, Cloudspeakers, Mufin, SoundCloud, and Echonest). The awesome German musician magazine DE:BUG is also in on the action. I also see our friends at Future Audio Workshop (developers of Circle) in the lineup.

Check out the details:
http://berlin.musichackday.org/
Weekend schedule

So, German readers, who’s going? I’d love to have some spies tell us what the discussions are with NI and Ableton.

I’m, as always, interested in how we can get past geography and share work internationally. So if you’re doing a project, be sure to take lots of pictures, screen caps, code pastes, and the like, and we’ll feature your work here on CDM.

Future events are planned for other cities, and I hope CDM will be involved in some of them. Boston will be the first US event, but it’s on a date I can’t make it. Anyone have a space here in New York you’d like to suggest?

Updated: See http://createdigitalmusic.com/snowleopard for a running report.

Apple’s “Snow Leopard” 10.6 ships Friday, which means it’s time to start compiling information about the new OS flavor. Just don’t upgrade too fast, as always.

Want to push an operating system to the breaking point? Ask a musician. Between the demands of real-time performance and the complex ecosystem of mix-and-match hardware, software, and plug-ins, odds are your local audio geek will break an OS faster than anyone else. Not every operating system upgrade is going to have a big impact on music software, but keep in mind that even subtle changes can cause issues that may interfere with your work.

Of course, all of this means music users should treat any OS update with caution. :

• If you’ve got a critical, primary production machine, your best bet is often simply to wait. Confirm that software works before you upgrade rather than after.
• If you’ve got some time to invest in an upgrade or have more than one machine, be sure to do a full backup and system image so you can revert to the previous, known working OS.
• Best solution: Boot off an external hard drive. Don’t commit to installing internally until you’re sure everything is working. Once you are, go enjoy. (as noted in comments, and yes, I should have said this initially… still, the latest 10.5 build is still the preferred OS for now.)

So, sit back. Enjoy life. Go for a walk on a beach. Recline in your favorite chair with your MacBook running Mac OS X 10.5 Leopard. Isn’t it great? Need to waste time? Plants vs. Zombies is out for Mac.

What? Still want to upgrade?

Fair enough. We’ll be tracking changes to Snow Leopard and which of them may impact audio.

The short version: Snow Leopard introduces only small changes, but if a developer hasn’t been on top of those changes, you could see issues. And as for the 64-bit mode that’s attracting most of the attention, the short answer is, you can’t use it for music yet.

Native Instruments and Plogue have each responded to CDM with information on their software.

Executive Summary

• NI and Plogue have tested their software as functioning on 10.6
• Neither NI nor Plogue recommends you upgrade your OS yet – Plogue uses stronger language to discourage you
• 64-bit support, expanded in Mac OS 10.6, is not yet relevant to music use because nothing (not even from Apple) supports it yet, but don’t worry – you can get more RAM through other methods
• Audio MIDI Setup gets a tune-up, and built-in audio support appears to be improved

Native Instruments

If you’re a Mac user who uses NI products on any version of the operating system, you should stay tuned to this URL:

http://www.native-instruments.com/en/support/compatibility/mac-os-x-compatibility/

NI tells CDM they’ve just updated it today with Snow Leopard information:

Native Instruments has conducted initial compatibility tests with Mac OS X 10.6, which have shown all current NI products to work without any specific issues under standard installations of this operating system.

However, users involved in professional audio production or live performance should be cautious about upgrading to Mac OS X 10.6 until compatibility with third-party audio software and hardware has been widely confirmed by the relevant manufacturers.

Native Instruments is currently conducting further systematic compatibility and performance tests with Snow Leopard, and will provide additional information on this page as it becomes available.

The second paragraph sounds like what I just wrote, huh?

Plogue

Plogue, an independent developer of a variety of software ranging from the awesome modular environment Bidule to sampling engines for Garritan’s orchestra and piano products and an upcoming library of vintage chip sounds have been doing their own work. Privately, I talked with them about some of the work they had to do after Apple rewrote underlying operating system plumbing with Objective-C (from C and Carbon). Here’s their official statement to CDM on Snow Leopard and, in the parallel Windows dimension, Windows 7:

10.6 and W7 each caused only minor modifications to our code base, however these mods are necessary for proper functioning of our products on those platforms. Most of our transition efforts as a company will be of a user support nature.

Any musician foolish enough to jump on new OSes without a hint of caution, inevitably makes me wish for a new kind of Darwin Award prize.

(Emphasis mine. Consider yourself warned.)

Ableton (Unofficial) and a Plug-in Warning

From the Ableton forums, via comments:

It’s currently being tested internally over here, so the current version is not officially compatible yet – on the other hand this does not mean that it doesn’t run.

We will release an update after the tests during the next weeks that will be officially compatible, but we don’t recommend upgrading yet if stability is your main concern.

It’s likely that a few new third party plugin problems will show up due to the changes under the hood in 10.6 and experiences show that the latest 10.5 versions now are the way to go after the gfx performance problems with earlier 10.5 and 10.4 versions.

So, in other words, now is a great time to upgrade to 10.5!

More in the thread here:

Ableton Forums

Now, note, mostly what this extensive discussion reveals is that Snow Leopard is poorly understood, partly thanks to a very successful hype campaign on Apple’s part. (Ahem.)

There are not magical performance and speed improvements found by installing Snow Leopard – or, most likely, any OS. (Would that such things were true.) The presence of a set of multithreading tools, for instance, is specific only to developers for whom that set of tools is useful. Audio software already has finely-tuned multithreading implementations specific to real-time applications, and in the case of something like Ableton Live, it really needs to work across platforms.

If you install a new OS with the expectation that it’ll be “faster,” you’ll almost certainly be disappointed. If you install a new OS hoping you’ll “break things,” then you probably won’t be disappointed. I don’t mean to suggest don’t ever upgrade or live in fear of all software, just that you should imagine that, like redoing the plumbing in your basement, long-term advantages will come, but with significant effort and time.

PreSonus Hardware

See a separate post: at Snow Leopard launch, PreSonus audio interfaces are likely to be entirely incompatible.

About 64-bit (Nothing to see here…)

NI notes that the 10.6 offers significant changes to 64-bit support, including a new 64-bit kernel mode – this being the rough equivalent of the “x64” 64-bit versions of Windows (and Linux) that have been available for some time.

Here’s the bottom line: 64-bit support on Mac OS isn’t yet relevant to audio users, period. It’s not supported by Apple’s own Logic Studio, or any other major host at this time. This is a situation we’ll be watching, as it is something developers appear to be investigating.

But before we get too far into that issue, you should consider why you’re asking about 64-bit in the first place. 64-bit computing offers two potential advantage. First, running processor computation natively at 64 bits offers a marginal improvement. Second – the issue most people care about for music – 64-bit memory addressing offers access to massive amounts of memory, beyond the approximate 4 GB barrier that applies to 32-bit applications.

More memory is a very good thing. But you probably don’t want to sacrifice compatibility just to get it. Fortunately, you don’t need the 64-bit OS to get beyond that 4 GB barrier. On the Mac, some workarounds have extended the practical life of 32-bit memory addressing for music applications – thus avoiding the need to get a 64-bit native version of every driver and every piece of software you want to use.

On Windows and Linux, you can indeed get a number of audio applications (like SONAR on Windows, for instance) that have excellent 64-bit support, and a number of the drivers have followed suit. Even, then, though, many users choose to stick with 32-bit versions in order to have superior compatibility.

Note that processing “64-bit audio” – that is, digital audio represented using 64-bit data – is a completely different issues. A 32-bit processor and 32-bit operating system and 32-bit software can all do 64-bit audio processing. Whether you really need 64 bits for audio production is a whole other can of worms I won’t open here.

Getting More Memory – Without Any 64-bit Snow Leopards

When I spoke to Apple earlier this month, they downplayed the 64-bit issue and pointed out that their own EXS24 sampler in Logic Studio can access additional installed memory just fine with 32-bit – that means if you have Logic 8 or later, Pro or Express, Tiger or Leopard or Snow Leopard, you can use additional RAM. Each EXS24 sampler instance has its own memory space, so you can use as much memory as you want.

Apple even has a support doc on the subject:

Logic Pro/Express 8: How the EXS24 sampler addresses RAM in Logic 8

Last month, we looked at the situation for Native Instruments’ Kontakt. Again, using some of the flexibility of the memory architecture unique to the Mac, they’ve managed to access bigger amounts of RAM even on 32-bit OS.

Kontakt, Battery: Enhanced, More Compatible, 64-bit Memory

Kontakt is able to get up to a whopping 32 GB thanks to something called the Kontakt Memory Server. Again, you can get still more than 32 GB using 64-bit Windows, but for most users, that’s overkill.

All of this is to say, 64-bit is not a reason to upgrade to Snow Leopard for audio work – at least, not yet. Some of the built-in applications (like the Finder and Safari) get performance boosts from 64-bit optimization on 10.6, but none of that is critical to audio and music – and it’s certainly not worth upgrading too soon only to find some compatibility wrinkle we haven’t yet found.

Updates to Audio MIDI Setup

A reader tips us off to some small changes to Apple’s centralized Core Audio settings panel, Audio MIDI Setup. Audio and MIDI are now separated into separate windows, and Audio gets some nice improvements.

Note the per-app settings and adjustments for sample rate, bit depth, and Format. As in previous recent versions of Mac OS, you can also aggregate multiple physical audio interfaces into one – one of a number of reasons we really love Core Audio as a sound system.

The reader also notes that the update seems to improve support for his built-in hardware:

It’s now possible to choose a higher sample rate and resolution for all inputs/outputs on the built-in sound card of my MacBook Pro early ‘08, which is pretty cool. Before there was clearly hearable, annoying digital fragments when playing back any sounds, especially on low volume – all magically gone, i don’t hear anymore noise.

Got More Information?

Help us continue our “More Than You Wanted to Know,” obsessive series of coverage on CDM and tip us off!

Corrections and clarifications are welcome, too – that’s why I enjoy the maleable nature of the Web.

Here’s someone who really, really loves Native Instruments’ B4 (II) software rendition of the Hammond B3 organ. The work of Markus Berger, this dead-ringer for a real B3 is actually a carefully crafted replica with elaborate MIDI control inside. The body is built by hand from cherry wood. Electronics were prototyped with the open source Arduino platform and implemented with electronics from Doepfer, then finished with manuals (that’s “keys” for you non-organists) from Fatar (as seen in Nord’s organs). Authentic-style drawbars finish the project. Correction: I got my wires crossed and originally claimed this had Fatar drawbars, but it’s Fatar manuals. Thanks to comments for spotting that.

The integration of the hardware design with the B4 is extraordinary: the creator notes that every single function is perfectly replicated, so you never have to touch a mouse or look at a screen. Of course, you can then make meticulous models tweaked on the B4 software that wouldn’t have been possible on the original hardware – and this hardware, while substantial, should be dramatically lighter.

More on those custom electronics:

The main controller electronics were actually custom developed and prototyped with Arduino. They were complemented by electronics from Doepfer for the two manuals.

Most of the electronics had to be custom developed as there was and still is nothing available to cover all the functionality of a classic Hammond B3 with the full drawbars set, preset keys and all the switches.

And yes, the bottom line is that this puts every controller for everything I’ve ever seen to shame. Thanks to Germany-based Twitter reader tillephone for sending this my way.

B4 Controller Project Page

I hesitate to even suggest this, but – is a Leslie cabinet next?

More photos after the jump:

ParamDrum TR Edition from Peter Dines on Vimeo.

Imagine a machine that lets you walk a thin line between control and chaos. You’ll be tweaking it, for sure – you’ll want to invest a sufficient amount of time shaping its sounds and adjusting its instruments to alter its flightpath. But once set in motion, it will give you variety and delicious insanity.

That’s the idea behind Peter Dines’ ParamDrum, a Reaktor drum machine with granular goodies inside providing sample manipulation and a set of clear sequenced controls for adjusting parameters. The “Param” bit refers to the parameters you’ll control – pitch + sample select + speed + size (of the sample) + smooth (granular) + swing. These parameters are unleashed against a sequence that you’ll likely never fully control – but that will never feel like it’s simply on autopilot, either. You can then load your samples into three players, which can be conceived as bass + clap/tom/snare + hat or something else entirely.

It may sound out of control, but “control” in the MIDI sense is essential. You can control step probability with MIDI velocity, tap in sequences with MIDI notes, and record playable automation with MIDI CCs from your hardware encoders. Pete has worked out a lovely template for Native Instruments’ Maschine controller, for instance.

ParamDrum, then, becomes a factory for variations. It allows you to iterate through plenty of results you don’t like to the one that’s perfect, for production or performance.

ParamDrum is a cheap US$12.50, though you do need a copy of Reaktor 5 (also included in Komplete) to use it. The upside is, it’s editable, and you get Pete’s immaculately well-organized patch macros, so it’s something you can modify easily or use as a model for your own patches.

Full details on Pete’s noisepages page, Modulations, which is also a new repository for his thoughts on sound design, Reaktor patching, SuperCollider learning, and other music technological geekery.

ParamDrum
modulations@noisepages

Planet ParamDrum

The other cool thing about ParamDrum in our throwaway technological world is that it’s already started to attract a little community of users.

Loopy C, master of strange sounds, has turned ParamDrum into his personal “hyperdrummer” for a track called Jah Frazzin Zooks, which he describes in a kind of experimental abstract poetry:

‘Frippish’, vari-tempo spectralisms meet Ornette Coleman-influenced electronica, hyperperformance machines jamming in the cafe at the end of the Universe (which for some reason look like fractal vaginas? (above)). Duo form.

The full track can be heard at his blog:
Jah Frazzin Zooks

Brettwiththedobro has a screencast (above) showing his own rig, with custom samples and the combination of Kore and Reaktor for control. (If you’re interested in the Kore and Reaktor combination, Pete’s previeous video tutorial is a great place to start.

This is a screen capture of Peter Dines Reaktor ensemble ParamDrum. I replaced the samples with my own kitchen/dobro sample map and hooked it into Kore to control various parameters. Fun, weird loops are a cinch.

Pete is also working with me on OpenSoundControl implementation in ParamDrum, which could enable cross-country ParamDrum collaboration, and via a project I’m building, visualization of parameters in Processing. Stay tuned.