Pure Data is a wonder: a free and open source environment for creating your own musical and multimedia creations with graphical programming, from Miller Puckette, the original creator of Max. You can produce everything from interactive sequencers and drum machines to synths to video performance tools by connecting patch cables visually, and you can run on virtually any platform, from BeagleBoards and Rasberry Pi to Mac, Windows, and Linux desktop. Via libpd, you can target other development languages and environments, embed engines in games, or work with Android and iOS.

It’s so important, in fact, that CDM invites Hans-Christoph Steiner, one of the key developers of Pd-extended, to give us a tour of what’s new. (Note: because Pd-extended includes various additional objects or “externals” that Pd Vanilla lacks, you should be careful when building patches for libpd. What I like to do is use Pd-extended as my editing environment, then double-check patches by opening them in Vanilla to make sure I haven’t accidentally used an object that’s not part of the bare-bones version. I can then substitute an object, copy an abstraction, or if necessary build that external.) -Ed.

The Pd-extended 0.43 release has been brewing an extra long time, about 18 months now, mostly because there are lots of big improvements. We wanted to make sure we got it right, so your patches all work, but the improvements all shine, so its taken a while. It’s now solidly beta, so we’re looking for testers. Download a beta build to try here:

http://puredata.info/downloads/pd-extended/releases/0.43.1

First off, the pd-gui side of Pd has been rewritten from scratch. The focus for most of the recent work has been on the editing experience, making your patching experience as productive and flexible as possible. To give some background, Pd has always been made up of two programs: pd is the core engine and pd-gui is the GUI. Since basically all computers now come with multiple CPU cores, this means that pd-gui will usually run on a separate CPU core than pd, so they don’t step on each other’s toes. pd can entirely take over its own core. If you want to make your patch use more CPU cores, then check out the [pd~] object introduced in the last release, but fine-tuned in this one.

There are so many ideas for making a better editing experience in Pd; this release makes big strides to address the editing experience. There are new features like Magic Glass, Autotips, Autopatch and Perf Mode, all available on the Edit menu.

• Magic Glass lets you magically see the messages as they pass through the cords. Just turn it on and hover above a cord, and you’ll see the messages as they go by. You can even look at signal/audio cords.
• Autotips gives you tips about what an object does, what its inlet expects, and what comes out of the outlets.
• Autopatch mode automatically connects objects as you create them.
• Perf Mode, is a mode for performance that makes it harder to accidentally close windows that are part of your performance.

A whole new Pd Window

The Pd Window is also majorly overhauled. First of all, it’s fast. Much much faster than the old one. You can now print thousands of messages per second to the Pd Window and still edit your patch. No more will an accidental dump of info cause the GUI to freeze up (well, okay, maybe if you send 10,000 messages/second, but that is way too many). There are also five levels of printing messages to the Pd Window: fatal, error, normal, debug, all. If you are only interested in fatal errors, switch the Pd Window to 0 – fatal, and you’ll only see the worst problems. You want to see every single message to debug? Switch to 4 – all, and you’ll drink from the firehose.

There is also the new log library, which lets you easily send messages for those different levels. And all messages logged with the objects from the log library are clickable: when you Ctrl-Click or Cmd-click (Mac OS X) on the line in the Pd Window, it’ll pop up the patch where the message came from, and highlight the specific object that printed it. That even works for many messages from other objects, as well.

The Pd Window also includes very basic level meters for monitoring the input and output levels. And for those who want to play with the GUI in realtime, you can type Tcl code in the Tcl entry field, and directly modify and probe the running GUI.

Customize the GUI with Plugins

One thing that you can do now is customize the GUI using GUI plugins. You can change all sorts of colors, some fonts, and many behaviors. Want to create a new object when you triple-click? Try the tripleclick example plugin Want to make the patch cords disappear when you leave Edit Mode? Check out the “only show cords in edit mode” example. Those are the simple ones. There is also Tab Completion, a search engine for the docs, a category browser for the right-click menu, a buttonbar for creating objects, and more.

You can find many GUI plugins in the new section of the downloads page as well as documentation for making your own. (What kind of GUI plugin will you write?)

Write Pd objects in more languages

Traditionally, Pd objects are written in Pd (abstractions), C and some in C++. This new release includes two “loaders”, Lua and Tcl, which allow you to write regular Pd objects in either Lua or Tcl. Pd is not the best for processing strings, so if you need to do that, you can now easily use Lua or Tcl, both very easy scripting languages for working with strings. Lua is often used for OpenGL work, so you can also run Lua objects to work in conjunction with Gem. Also, the Tcl loader lets you write GUI objects in pure Tcl, no C needed.

Multi-processing, Pd-style!

The [pd~] object now works out of box. In case you missed the introduction of the [pd~] object in the last release, we’ll introduce you now. [pd~] is Pd itself incapsulated into an object. You can run any patch inside that instance of Pd, the difference is that the Pd in the [pd~] object runs in a totally separate process. So if your computer has multiple CPU cores, which basically all computers do these days, then the Pd process inside the [pd~] object will run on a separate core. This means you can have a heavy Pd patch spread across multiple cores or CPUs. Or for people who work with video and audio together, you can have one instance for video running at a normal priority, then another instance for audio running at a high priority to make sure there aren’t clicks in the audio caused by heavy video processing.

Autotips, generated from help patches

This release also provides a new “autotips” feature to provide instant information about objects and their inlets and outlets. It is one of the first new developments to showcase all of the meta data that is now included in all of the help patches. (Check out the [pd META] subpatches.) When you hover above an inlet or the object itself in Edit Mode, you’ll see a short text description pop up on the lower left corner. But, of course, using a GUI plugin, you could customize how they are displayed to make it how you want to see it. If you want to add autotips to your object, then just add a [pd META] subpatch to your objects’ help patches, and fill out the description, etc. Voila! They’ll have instant information.

What’s next?

The core pd process still handles a lot of the GUI stuff, but we are working on splitting that out for the 0.44 release. That is a big chunk of work, but it will also bring big gains. In particular, it means that it will be possible for people to write their own GUIs for Pd, covering not just the display of the patch, but also the editing, and everything else. You like OpenFrameworks, Python, iOS, JUCE, Qt, etc.? Write your own pd-gui using the toolkit of your choice. That’s the idea at least. That will take a solid chunk of work, so we are looking for people to join that effort.

Try it yourself:

http://puredata.info/downloads/pd-extended/releases/0.43.1
http://puredata.info/downloads/pd-extended

Where to learn Pd:

Resources to start learning

-Hans-Christoph Steiner for CDM

Someone at Pioneer worked out how to combine the timer used in chess, the boombox, some DJ effects, and dance battles, and the result is this: the STEELZ AUDIO Type T, evidently new and under glass at Musikmesse in Frankfurt this week.

I think it deserves special mention for its sheer oddness. (And hey, maybe this is a product for someone somewhere!) One of the great things about it: it displays all sorts of little animations.

I would not normally copy and paste, but:

Auto Battle Mode*
STEEZ AUDIO incorporates “Auto Battle Mode” – Pioneer’s unique technology which makes it easy for dancers to battle anytime, anywhere. Simply set match-up (playing) time or music genre, and the mode automatically selects and edits tunes for dance battles. Select “Circle” for multi-dancer match-ups or “Normal” for one-on-one, two-on-two and team dance battles. STEEZ AUDIO covers what a DJ/timekeeper would normally do, and allows you to smoothly switch music for battle by cutting in on and echoing tunes. It even prompts you with your choice of voice or tone call signal, 10 seconds before a change of dancer in a battle is required.

It is nothing if not a clever idea. It also demonstrates you can imagine products that use music technology that aren’t conventional music products. Tempo control from Pioneer’s DJ line, for instance, is intended to aid practice, along with beat detection, skipping and cueing, and automatic mix. Companion software pre-analyzes your files.

This may be the first and last time CDM mentions a car stereo product from anyone, so have at it:
STEEZ AUDIO Type S

Pure Data (Pd) is already a free, convenient tool for making synths, effects, and sequencers and other musical generators. But imagine stripping away all the things that tie it to a platform – UI, specific hardware support – so it will run just about anywhere, on anything, in any context.

That’s what libpd, a free, embeddable, open source (BSD) tool for making interactive music, does. Coders can take their favorite language and their favorite platform, and just plug in the power of Pd. They don’t even have to know almost anything about Pd – they can let an intrepid Pd patcher create the interactive sound effects and dynamic music for their game and just drop a patch into their assets.

One of the most powerful applications for this is the ability to add interactive music and sound to mobile apps, on iOS and Android, without writing and testing a bunch of custom DSP code. And that has enabled the use of libpd in apps as successful as Inception: The App. With music by Hans Zimmer and a custom “dream” experience created by RjDj, that app racked up millions of downloads in under a couple of months, and then, far from sitting idle on the app launch screen, went on to clock in over a century of user “dreamtime.”

Okay, so, you’re sold. You want to see what this thing can do, and maybe try it out, and you’re wondering where to start. So, here’s some good news: there’s a new site and a new book to get you going.

The site: libpd.cc

libpd has a new home on the Web, both in the form of a new GitHub repository to organize all the code and docs and samples, and a site that brings together a showcase of what the apps does and points you to where to learn more. The single destination is now hosted here by CDM:

http://libpd.cc

I built that site, so please, if there’s anything you’d like to see or you’ve got your own work created with libpd, let me know about it.

Even just having selected a few key highlights of apps built with libpd, it’s impressive what people are already doing with this tool:

libpd Showcase

The book, and a chat with its author

A new book published by O’Reilly focuses on building mobile apps using libpd, for iOS and Android. (iPhone, iPod touch, Android phones and tablets, and yes, even that “new iPad” introduced yesterday are therefore all fair game.)

You can read a section of the book right here on CDM, for a taste of what’s in store:
How to Make a Music App for iOS, Free, with libpd: Exclusive Book Excerpt

It’s an exceptional, comprehensive look at development using libpd, covering iOS and Android, but also a complete look at the libpd API and how to use it. For Pd patchers just getting started with iOS and Android, it includes all of the basics of how to use libpd in your mobile development environment. For mobile developers new to Pd and patching, it makes clear how you’d communicate with Pd, so you can either dive into Pd yourself or properly interface with patches made by musicians, composers, and sound designers with whom you may be collaborating. It’s an ideal title for anyone interested in taking a game and giving it a more dynamic soundtrack – in sound effects, music or both – or for people building mobile musical instruments and effects, sonic toys, interactive albums, or, really, anything at all that involves sound or music. Since it walks you through the entire development experience, you can sit down with it in the course of a few evenings, and get a complete picture of how to integrate Pd with your development workflow.

Dr. Peter Brinkmann, the principal developer of libpd, is the author of the title. I asked Peter to explain a little bit about the book, who it’s for (hint: you!), and what’s in it (hint: stuff you want to read!) …

CDM: How did this book come about? And the book process really helped drive improvements to libpd, too?

Peter B.: Shawn Wallace, an editor at O’Reilly, contacted me last summer and asked whether I would be interested in writing a short book on libpd. I was interested, and so I talked to my [Google] manager (“No conflict — we all have time-consuming hobbies!”) as well as a couple of colleagues who had written books for O’Reilly. They made a token attempt to dissuade me, but it was clear that they had enjoyed writing their books, and they seemed quite proud of the result, too.

Once I had made up my mind to write a book, the next question was whether to self-publish or go with O’Reilly. Self-publishing is a viable option these days, but then I decided that I really wanted an animal on the cover. Besides, I had never written a book before, and having the support of O’Reilly’s editorial staff made the prospect seem less daunting.

The first draft was done in mid-November, but at that time it was basically science fiction because it presented libpd the way I wanted it to be, not the way it was at the time.

So, after the bulk of the writing was done, libpd needed to be revised so that it would actually be in agreement with the book. In particular, Rich Eakin and I rewrote the iOS components for better performance and usability. That delayed the book by a month or so, which turned out to be a great stroke of luck because that was when I discovered that Xcode 4.2 had changed the entire development model by introducing automatic reference counting, instantly rendering existing
texts obsolete. That included my chapter on iOS, and so I had to sit down and rewrite it.

After that, the rest happened rather quickly — getting reviews, revising the draft, going through the production process. O’Reilly’s toolchain is remarkably efficient, using asciidoc and docbook in a Subversion repository. The editorial staff is great, too. I’m amazed to see how quickly it all came together.

How did you approach writing the book?

For the first draft, I just imagined that I was teaching a class on libpd. When you’re lecturing in front of an audience, you don’t have time to polish every sentence; you just have to talk and maintain some sense of momentum. That approach helps a lot when facing a blank page. After that, it’s many, many rounds of revisions to eliminate weak or redundant sentences.

For the sample code, I picked one project that uses all major components of libpd. That provided a natural progression from idea to completion, while touching on all important points in their proper context. I’m basically providing running commentary on my thought process when making an app, including common mistakes and pitfalls. Like this, readers will know how to recognize and work around most problems.

Another trick is to write more than necessary. The first draft contained a lot of gratuitous editorializing. Those parts were never meant to make it into the finished text, but they were fun to write and they kept me going when I wasn’t quite sure what to write next.

Who it’s for?

The book explains how to patch for libpd, and how to write apps with libpd, with special emphasis on the interface between Pd patches and application code. It’s for mobile developers who want to add real-time audio synthesis to their projects, as well as sound designers who want to deploy their work on mobile devices. It’s light on prerequisites; if you know how to write a basic app for Android or iOS, you’re ready to read the book.

Ed.: I’d add to that, given that there are such great tutorials on app development for Android and iOS – even many of them free, including some very worthwhile documentation from Google and Apple — if you’ve messed with Pd, you should give the book a try. And if you haven’t messed with Pd, this could be a great excuse. This book won’t teach you Pd, but it’ll make very clear how to glue everything together. -PK

Why does a book like this matter? What do you hope will come out of it?

I hope that the book will help popularize real-time procedural audio, in games and other apps. I’m thrilled to see all the projects that use libpd, and I hope that the book will help people create even more awesomeness of this kind. One thing I only fully realized when writing the book is that libpd lets developers use DSP code like a media file: An audio developer creates a Pd patch, and the app developer just drops it into the resources of the app and loads and
triggers it as needed. I guess this was implicit in a blog post I wrote on workflow and prototyping a year ago, but I think the DSP-as-media angle is even more powerful. I hope that the book will bring this out.

The book project has already improved libpd. Whenever I faced the choice between fixing an awkward bit of code or explaining the awkwardness in the book, I chose to fix the code. That took care of all the little things that were sort of bothering me but didn’t seem significant enough to spend time on. It also gave us a deadline for a number of related things that we wanted to do, such as migrating to GitHub and launching the new website, libpd.cc. Ed.: Cough. Yes, glad that gave me that deadline – and thanks to Peter B. for the extra push! -PK

Congrats to Peter on his first animal-on-a-cover! It’s really a great book: you read it, and feel like making more new things, inventing new creations that produce sound and music. And that’s a very good thing.

For years, since the launch of Ableton Live, many have waited for a worthy rival, something that combines production and live performance for music users. Live isn’t without alternatives – Renoise, for instance, has earned some fans, though it isn’t necessarily built for live performance. But few provide the same real-time workflows.

Bitwig, based in Berlin as is Ableton and featuring some Abletronic veterans, today took the wraps off its own Bitwig Studio. The good news is, it’s looking as though it might shape up to be a viable tool for DJing, performing, and making music. The bad news is, in a market already crowded with lots of similar tools vying for your attention, the first release will look more familiar than radical. That is, it looks and works a whole lot like Live. There’s an Arranger view, a clip launching view with scenes, a tray on the bottom with effects and instruments (they’re even called Devices, like in Live). The screen layout, and even specific interface widgets and channel strip arrangements are all straight out of Live.

It’s not just a little like Ableton Live, either – it’s in some cases a direct clone. Nested drum machine Devices, for instance, work in a way that I’ve never seen out of Ableton Live. A channel strip similarity or two is almost inevitable; here, though, lots of little details add up to something that feels like Ableton, but didn’t come from Ableton.

What that means to you may depend on what you want: whether you just want an improved Ableton alternative that works like Live, or whether you want something more fundamentally different from Live as an alternative.

If you want “Ableton Plus,” Bitwig does take on features Ableton is missing. For instance:

1. Linux support. In fact, right out of the gate, this could quickly be the answer for Linux users waiting for something they could use without booting to Mac or Windows.
2. Proper multiple document support. You can share content between projects in Ableton, but here you can actually open and freely exchange media with multiple files at once.
3. Mix audio and MIDI on the same track. Tracks are content-agnostic.
4. Per-note automation, with the mixed MIDI and audio, promises more detail-oriented editing.

Those are three significant breakthroughs. And it looks like there are lots of tweaks and improvements throughout the tool, many of which I’m sure we’ll hear about as people begin testing the beta. (One nice example: a vertical pane lets you view arrange and clip launching views simultaneously.) Multi-monitor support, while present in many tools, is sorely lacking in Live but available here. Plus, as some readers note, you do get 64-bit support, though that seems an advantage over Ableton that won’t last long.

The challenge is, as a new entrant to the market, your first obstacle is telling a story about what you are. And here, there seems a missed opportunity to make a first impression as something truly different, rather than something “similar, but better.” Ableton Live 1.0 when it was released was a significant departure from what had been seen before. So, too, were the first trackers, the first audio+MIDI DAWs, and the first graphical sequencers. Bitwig Studio isn’t that kind of breakthrough – not yet.

Not that being different is easy, or even always desirable. Amidst so many things users want, and so many expectations they have about how things will work, it’s tough to do something genuinely new without simply confusing everyone and driving them away. But it has happened – Ableton Live’s original release being a notable case. One question is whether you make some sacrifices to release the most significantly-different tools initially, or whether you choose to cover the basic bases to provide a workable solution from day one, and the Bitwig devs seem to have chosen the latter.

The most interesting features remain on the horizon. LAN multi-user jamming and multi-user production are both on the roadmap – features we’ve seen in other tools, but which have yet to catch on. And there’s an integrated modular system that lets you build your own instruments and effects with graphical patching – something seen in various forms from Buzz to Max for Live, but one that could use a fresh take in integration with the tool.

In the meantime, we’ll have to hear from beta users whether Bitwig is something worth a look. You can sign up now:
http://bitwig.com/bitwig_studio.php

We’ll be eager to hear what you think.

Pics:

In a responsive, real-time sculpture, the simple sonic qualities of a rainstick become electronically enhanced. Rainlith, a “kinetic sound art” work by Rui Gato, makes the rainstick itself robotic, its sounds transformed in space in a way that is itself sculptural. Responding to movement in the space using Microsoft’s Kinect, the apparatus is a geektastic brew of just about every tool you could imagine involved in this sort of construction.

The artist shares full details, reproduced here in both English and Portugese – and Rui, thanks for sending this in:

Rainlith 2 – Kinectic sound art piece.

On Rainlith, the primitive naturally granular sound of a big rainstick gets explored in real-time by cyber-age sound manipulation tools.
It’s an interactive piece in witch the movement of the audience’s body activates an electric motor, making a reflex movement on the structure that embraces the instrument.
The sound of the rainstick is captured and processed in realtime, and sent 24 meters above, filling the empty space of a old industrial cereal container. The reverberated acoustic mix is then received back by the audience in the spot right below the opening of the container.

Na peça Rainlith o som primitivo, naturalmente granular, de um pau de chuva é explorado por ferramentas modernas de sound design, em tempo real.
É uma peça interactiva em que o movimento do corpo do público activa um motor eléctrico, provocando um movimento reflexo na estrutura que sustenta o instrumento.
O som captado em tempo real é processado e enviado 24 metros acima, enchendo o espaço de um silo de cereais industrial. A mistura acústica reverberada é absorvida pelo visitante no local imediatamente abaixo da abertura do silo.

hardware:

microsoft kinect
arduino duemilanove
H-bridge (hand made)
24v 6A DC motor
CPU
zoom H4N
FM emitter / receiver
ion ipa3 portable speaker

software:

MAX/MSP
Max for Live
OSCeleton
OpenNI
Nite
toxiclibs

agradecimentos especiais:

Nicola Henriques
Susana Luiz
Luís Pereira
Paulo Carocinho
André Sier
Daniel Coimbra
Ruben Santos

By the way, if you’re intrigued by the potential of Kinect, be sure to read sister site Create Digital Motion for more. Just today, we have news of a new version of EyesWeb that could be relevant to musical use:
EyesWeb, Powerful Computer Vision Software for Windows, Adds Kinect Support, Fixes, More

Sound and music for games is already a growing frontier for professional music careers; mobile, then, triply so. But with the expanded opportunities come unique challenges. Learning about them requires real-world experience, and short of word of mouth, that kind of knowledge is often scarce – even in the Web age.

Composer, sound designer, and audio director Ben Long has put his sonic thumbprints on games and TV networks alike, and has recently turned his attention to sharing some of the industry secrets of the mobile realm, with work in game design textbooks and GDC China. Now, he has a new book entitled “Game Audio 101: Mobile” that assembles all that experience into a single reference. Launched at South by Southwest Interactive, it could prove invaluable to people aspiring in this area.

What’s especially unique about this title is not only its focus, but its insights into real-world case studies – fairly legendary ones, at that. Long gets tips and background on the making of sound for hit titles Angry Birds (iOS, Android), music app Drumkit (iOS), and RPG hit The Harvest (Windows Phone).

Nor is this generalist advice, painted in vague, broad strokes. There are specifics of platforms (not only iOS, but Windows Phone and Android), sound design technique, technical information, and career advice. Covered in the book:

• Basics of the mobile market, MIDI and mobile design
• Anatomy of specific titles and the techniques they used to make effective music and sound direction
• Particulars of everything from looping to sound cues, coupled with interviews with sound designers
• Tips on improving sound design, catering to specific platforms, and managing your career and negotiations

I should caution that this is more of a white paper of assembled research and tips than a front-to-back textbook. My one complaint is, therefore, it does feel a bit abridged, under fifty pages. There’s sometimes a copy-and-paste sense to the content, as well, in case you’re expecting something with the level of polish of, say, an O’Reilly e-book. The tips you can glean from it, though, could be worth the price of admission if this is a field about which you’re serious – and a lot more than you’d get out of a similarly-priced workshop or the massive cost of attending conferences. You’ll have to do a little digging – the title really picks up somewhere about halfway through – but you could easily get some nuggets that could transform a career.

To make things easier, we have a CDM-only discount code for readers, bringing the price down 50% off its current sale price to just $19.95. Enter the following code at checkout:
AT101ebooksxsw45

More information:

http://www.gameaudio101.com/about_book.php

Ben Long has also written a terrific reference exclusively for CDM, from January – much shorter than the book, but good if you want a taste of his writing:
Creating in 2011: A Composers’ View of Mobile Game Audio, From Trends to Slot Machine Sound Design

Let us know what you think – and definitely if you happen to get a good gig in the industry.

Audition, a favorite, previously Windows-only wave editor from Adobe, is coming to the Mac this winter. Adobe is touting native surround support, multi-channel effects, and performance optimizations; you can check out how the new tool looks at Adobe Labs. The public beta is due this winter. Interestingly, Adobe is pushing the video side of this more than audio, even though Audition is popular with audio users. The demos are hosted by video specialist Jason Levine, and “post production” is the phrase that keeps coming up.

The Mac is quickly becoming spoiled for choice with dedicated wave file editors, maybe enough that the half-decade-plus absence of Macromedia SoundEdit can finally be put to rest. WaveLab from Steinberg was announced back in March, joining the likes of BIAS Peak, Audiofile’s Wave Editor, DSP Quattro, Sound Studio, Apple’s Soundtrack Pro, and Audacity. Readers are divided on whether such dedicated tools are even needed, given expanded editing features in music and video programs, but those who do love them are very particular in their tastes. That means lovers of Audition on Windows, and people looking for more serious post-production tools to complement Adobe’s video offerings, now have some good news.

What made Adobe make the decision early? Well, I don’t know if you can chalk it up to a scathing review by my colleague Chris Breen for Macworld. But I do think the message he brought – that Soundbooth CS5 wasn’t quite up to pro tasks – was probably one Adobe was hearing from a lot of other people, too. Here’s how Chris opened his review:

When you think Adobe, the first thought unlikely to pop to mind is audio. And yet Adobe continues to include its Soundbooth audio editing application in the Creative Suite 5 Production Premium and Master Collection bundles and sells the application separately for $199. Compare the latest version of Soundbooth with its predecessor, however, and you can be excused for thinking that audio is not among Adobe’s priorities. Soundbooth CS5 is a meager update that fails to address the application’s most glaring shortcomings.

Ouch. For what it’s worth, while I think you’d have to be pretty nuts to buy Soundbooth standalone for two hundred bucks, it’s worth trying out if you own CS. It’s great for quick edits and podcasts and such, though I agree with all of Chris’ criticisms.

Windows users, though, very often do think of Adobe Audition as a close rival with tools like Sony SoundForge and Steinberg WaveLab on the PC. (Now, only SoundForge hasn’t announced a Mac port.)

So, to what can you credit Adobe’s ability to port the tool? Without knowing the specifics of Audition, generally with Adobe apps, you can thank the use of cross-platform libraries and some shared code between applications. That could also mean that the announcement of Audition for Mac is simultaneously good news for loyal Windows users – it means Audition is getting some attention, and I wouldn’t be surprised if Audition for Windows gets an update around the same time.

What I wouldn’t read into this is any larger conclusions about Windows-to-Mac porting, as Synthtopia does:

Adobe Bringing Audition To The Mac. Could Sonar Be Next?

I can answer that question: no. Cakewalk has told me repeatedly that, while they’re enthusiastic about supporting the Mac, SONAR is closely tied to Windows. A DAW is also a lot more complicated than something like Audition. Tools like Cubase (in its current generation) and Ableton Live were built with cross-platform support in mind; adding it down the road is a much harder task.

I don’t think anything about this landscape has changed. Developers who can do it easily are happy to be on both platforms, most of all a company like Adobe that makes cross-platform support part of their business strategy.

But as I said, even Windows users may wind up getting a refreshed version of a favorite audio editor out of this.

Stay tuned for when you can audition this tool for yourse— oh, jeez. That’s a terrible way to end this post. I apologize. Someone must have dropped a CS5 box on my head or something.

Updated: Jim Dalrymple at The Loop talks to Adobe about Audition. Notable – Audition for Mac is getting some of the great noise reduction features from the Windows release (as noted by readers in comments), as well as some of the more unique and effective tools in Soundbooth (Paint Brush, Healing):

An audio engineer himself, Levine said that Audition has a number of features that cannot be matched in other applications. Most notably, Levine said Audition’s noise reduction and restoration capabilities will be something to watch out for.

“There are plug-ins that can do noise reduction, but quite frankly, Audition is just better,” said Levine.

Audition will also feature some very familiar tools like a Paint Brush and Healing Tool. Photoshop users know these tools well and they work just the same in Audition, except with audio instead of images.

Adobe Audition coming to the Mac [The Loop]

Wish you could make any track swing? Tristan Jehan, grad of the MIT Hyperinstruments Group and c0-founder of The Echo Nest, made that happen at San Francisco’s Music Hack Day. The Python code uses the Echo Nest’s sound-processing magic, available to the world via open Web APIs, in order to analyze tracks and re-synthesize them in swing form. The results are — well, somewhat terrifying, though in a cool way.

Paul Lamere of Music Machinery points this our way and has a ton of examples on his terrific, sound geek-friendly blog. (The post must have captured people’s imagination, as it’s spread virally online, but I know this is the only site you read — right?)

The swing is definitely of the consistent/mechanical variety, but … well, it does serve to prove that not everything should swing, but anything can.

My picks for the trippiest examples:

Enter Sandman- the Swing Version by plamere

Around the World – the swing version by plamere

The iPhone’s glass touchscreen may be a thing of beauty, but despite its multi-touch capabilities, it would seem this device is incapable of responding to how hard you tap it. But the developers at Wave Machines Labs apparently didn’t want to take no for an answer.

The iGOG drum suite for iPhone provides drum pads and sample triggering in unique ways, most notably in its velocity-sensitive VelAUcity. How do you get velocity response from a device that’s supposedly not pressure-sensitive? Presumably there’s additional data in the touch events that makes this possible, but for now Wave Labs aren’t saying:

iGOG’s proprietary VelAUcity technology does the unthinkable and turns the iPhone’s screen into touch sensitive drum pads. Play loud, play soft, or play a full-blown crescendo on a crash cymbal, iGOG will capture every nuance of your performance. Just plug in your headphones and start playing.

Here’s the interesting twist: generally, when any of us say “iPhone,” what we really mean is “iPhone or iPod touch.” That’s not true in this case: “NOTE: VelAUcity is only available on iPhone devices. if you’re using an iPod Touch, VelAUcity is disabled.” That seems to suggest that the trick is the built-in mic, or at the very least some private API that’s iPhone-specific. (Audio triggering is most likely, as this app comes from a developer with drum replacement experience.) That would also suggest to me that you might be able to pull this off with non-Apple mobile devices and controllers in the future.

As a result, though, I can’t test it – I have only the iPod touch.

Unconvinced or uninterested? iGOG has some other approaches to how the small Apple handheld can be made more useful as a set of pads:

• Multi-positional pads that assign articulation based on location
• A mic trigger mode — which may be more useful than the VelAUcity. This mode assigns any nearby sound (like rapping a table) as a trigger. (That’s possible, of course, with a variety of software, but having the device itself be portable could be handy, so to speak.)
• Multi-samples, file management, and sequencing for doing more with the samples.
• No, real multi-sampling — 384 multisamples per drum!

Even if you’re skeptical of yet another iPhone app, I think there are some great ideas here for music software (mobile and otherwise). Here’s a look at the mic trigger mode in action:

Oh yes, and speaking of all this audio triggering, the same developer makes the superb Drumagog drum replacing plug-in. With pricing at US$199-379, you have to be pretty serious about drum replacement, but I know people who are who swear by it. There’s really nothing stopping you from whipping up your own solution, but Drumagog has a lot of niceties that make the process easier, quicker, and more powerful.

http://www.drumagog.com

If you are a Drumagog user, you can bring those files into iGOG. That makes this app all the more interesting – it can be both a fun toy for someone new to the idea, and a companion to a more serious (and more expensive tool).

More on iGOG:
http://www.wavemachinelabs.com/igog/

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/