I like to do six impossible things before breakfast. You?

This is either the first death knell for the traditional desktop DAW, or an ill-fated attempt to squeeze a desktop DAW onto a tablet. Or, more likely, it’s somewhere in between.

Auria isn’t the first multitrack production studio for a mobile platform, but without question, it’s the first to look and function in the way you’d expect only a computer Digital Audio Workstation (DAW) to work. The track count is the first banner feature, but perhaps what will turn heads most is actually the support for conventional plug-ins.

Updated: You know, I’m writing about this thing based on their description, but it’s worth adding that the track counts (with these kinds of plug-ins), multi-track recording, and even plug-ins were previously believed to be impossible by many developers. That makes this an … interesting announcement. Happily, we’ve just gotten updates from the developer explaining those questions — see below.

Just a few of the bullets that might cause more than a little surprise:

• 48 mono/stereo, 24-bit/44.1kHz tracks, with recording for up to 24 tracks (you’ll obviously need a USB audio interface that can do that – see notes below)
• 64-bit, double precision mix architecture (something even Pro Tools only just acquired)
• Full delay compensation
• “Vintage-inspired” channel strips, with a desktop-like UI and VU/RMS switching
• Plug-in support (Out of the gate, PSPaudioware, Overloud, Fab Filter and Drumagog all work. You need to do custom wrapping of plug-ins for this host; standard plug-ins won’t work. The format is based on VST, but it’s not VST in the traditional sense in that they have to be custom-wrapped for sale through the app. See developer notes below.)
• Dropbox, SoundCloud, AAF, MP3 export
• Advanced channel strips, EQ, expansion/compression and dynamic controls ready to go
• Convolution reverb. (Really.)
• AAF import/export, making one definite application using this as a satellite for your desktop DAW (more on that notion below)

Update: I should say, and this is vitally important, the software isn’t shipping yet. No one has seen it in action. And that means all of this is hypothetical until we see whether this works at all. But see some notes from the developers that answers some skepticism. (This wasn’t just skepticism coming from me or end users – I heard from a number of puzzled developers who work on iOS apps!)

As impressive as all of this is technically, I’m not sure there’s a strong case for why you’d need such a thing on an iPad, other than “because you can.” But that raises the question of how you might actually use it. One obvious application for me is having a portable multitrack recording rig on which you can instantly add effects. It’s easy to imagine taking this to a concert gig, recording multiple tracks, then mastering a live show on the back of a tour bus. Then again, there’s nothing really stopping you from doing the same with a computer.

The main thing for me is to get hands on with this and see how this desktop-style UI adapts to an iPad – whether it feels newly mobile and touchable and usable on the go, or whether it feels like someone crammed your desktop DAW onto a different device. It’ll also be intriguing to see how plug-in counts work in practice on mobile hardware. And you do have to consider, cool as the plug-in support it, that you may miss some desktop plug-ins.

I’m eager to see someone review it, but that for me comes back to the question – how will you use it? And what is the real advantage of doing what you’ve done on a computer with an iPad?

My bet remains this: I still think the whole beauty of mobile devices is, for most, as a satellite, a complement to your desktop setup. And you have to consider how affordable something like a MacBook Air is – complete with Thunderbolt, something I don’t expect (as Intel tech) on an iPad any time soon. But that makes a touchable tablet as an inexpensive tool to orbit your studio really appealing, and I see some features here that could make this work in just this way.

(In fairness, I’d ask the same question of any new DAW entry – even on desktop.)

http://auriaapp.com/Products/auria

I believe Synthtopia gets the nod for this:
Auria Brings 48-Track Recording & VST Support To iPad – Are You Ready For The iPad To Replace Your Studio?

Wait, your whole studio? I think you still want monitors and mics and things, right? (Sorry, had to point that out…)

Not due until this spring, so we have some time to work out how to review it.

And yes, the most important question here is, is this actually possible or impossible?

Developer Responds

Rim from Wavemachine Labs answers questions I – and many developers – had about the app. I’m going to promote these from comments, as they’re important, and will add more as we hear it. (And yes, it’s actually quite good news to hear that they do have this working.)

CDM: How do you get 24-track audio recording on an iPad?
Rim: iOS5 supports USB Class 2 devices. We’ve got Auria recording with 18 input interfaces (the largest available right now). We’ve tested over 20 audio interfaces from various manufacturers and will be posting a list of compatible devices on or site when we released the app.

Although there are no 24-input USB interfaces out there, I’m ready for them in the code, and there’s enough resources to handle them.

Q.: How can you have “plug-ins” in an app on iOS, given Apple’s rules?
Apple won’t allow users to add anything to an app, like a plug-in for example. All add-ons to an iOS app must be statically linked into the app when it’s released. Auria supports real VST plug-ins which have been linked into the app. Users can then purchase these through the in-app store. If you’re a developer and would like info on how to port your plug-ins to iOS, drop me a line (rim at drumagog). Auria supports the official VST SDK (2.4), and we also have a custom JUCE library available for developers.

Q.: How much can you really do with an iPad versus a computer? Many of us would have imagined that doing this much was impossible.

I’ve spent the better part of a year of making 48 tracks and plug-ins happen It does work, even on the current hardware. If you’re going to be at NAMM. please stop by and see it work… You can have a 48-track project (with perhaps half of these tracks stereo), and have 24 tracks of channelstrips open, an instance of Drumagog on one track, and use about 70% of the CPU/ 50% of the disk resources. There’s also a track freeze function. We used assembler for lost of the heavy lifting and a lot of experience (I designed a very early touch screen based DAW in the late 80s).

The Melodyne editor, which promises to make working with audio as fluid as working with MIDI, has long had some impressive technology under the hood. But it’s as the tool gradually matures in terms of workflow and usability that I think it could win some additional converts.

Melodyne 2.0 is a major update to the editor all around, with additional timing and tuning options and better usability, and the addition of ReWire (atop plug-in compatibility) is a big plus for some. It’s easiest to just see the videos, but the overview of what’s new in this release:

• Attack Speed tool for editing transients. (That could make this a lot more interesting creatively.) New Time Handles for changing time in the notes. These tools have special applicability to percussion and vocal phrasing, respectively, but may have some other interesting alternative applications.
• Edit notes in other scales, temperaments, and tunings. (Re-tuning to alternative tuning systems, anyone?)
• Keyboard shortcuts work in plug-in mode, display and highlight is improved.
• Work via ReWire with hosts that lack plug-ins. Read: Reason. And that could make this an interesting companion to Reason’s record workflows.

Now, sure, all of this is often understood to be for people who just want to obsessively correct pitch and rhythm of recorded audio. But I remain interested in creative applications, just because the upshot of this is having audio you can modify after it’s been recorded.

There’s just one bottom line: will this stuff be compelling enough that you add an additional tool to your DAW just to get it? I still have yet to hear from die-hard Melodyne users, so if you’re out there reading, I’d love to learn how you use the tool, particularly if you go a bit beyond the way it was intended to be used. (That’s always interesting.)

US$/€399, $99/€99 upgrade, or free if you registered after October 1. More vids:

Let’s get straight to it: Ozone has already established itself as a do-everything mastering tool. It’s a suite of interconnected modules handling frequency and dynamics, designed to work together in an integrated interface. It does so much, in fact, that it’s hard for an upgrade to do more, but Ozone 5 promises new sound and visual feedback that could further entrench this popular tool.

And that could explain how Ozone 5 stole the Audio Engineering Society trade show in New York. AES is a flurry of knobs, dials, and faders, but some of the major buzz we heard was just this single upgrade to the software. (CDM’s Marsha Vdovin was out on the floor, and the word “Ozone” kept cropping up.)

Ozone is eminently visual software, so a lot of what’s new you can glean just by looking through the screenshots. But there are sound improvements, as well, both in the standard Ozone and the spendier “Advanced” edition.

What’s new:

• Updated modules. iZotope says they’ve “refined” their DSP algorithms. (Let’s see, carry the one…) The idea is, existing modules should sound better. There’s a detailed list on the iZotope site – aside from more subtle changes, you’ll find very specific adjustments to how parameters are controlled and how they impact the sound. To give one example, there’s a …
• New Limiter. The latest version of iZotope’s “psychoacoustics-based” limiter in the Advanced edition has a new stereo link control for handling left and right separately or together, and new intelligent transient handling algorithms, among other improvements.
• Enhanced EQ. Analog-matching EQ models analog shelf modes and frequency response, matching is easier than before, as with other modules, you can use left/right separately, and now zoom and display stereo info in your spectrum. There’s also new variable-phase functionality.
• New Reverb. Yes, sometimes you use reverb when mastering. (A little light reverb can do wonders.) A new modeled reverb algorithm adds new models and spaces and gives you unique early reflection control, as well as “cross-mix” for stereo imaging.
• New UI, workflow. I’ll let you just see what this looks like, but suffice to say parameters and labels are better-organized to be friendlier to advanced and beginning users alike. Past versions of Ozone were sometimes pretty-but-counterintuitive; this looks a bit clearer. Of course, you might not notice while dazzled by the…
• Slick visual feedback. In the standard version, metering has been enhanced. In the Advanced version, you get slick 2D and 3D plots of your sound spectrum for the Meter Bridge and Meter Taps modules. They look awesome, yes, but I also think these kind of “alien world mountainscape” views can help you better visualize what’s happening in a sound, so there is a practical use, too.

And, of course, all of this means you can easily wow clients when mastering by showing them visualizations that look like Geordi LaForge is studying abnormal quasar activity from the deck of the Enterprise. Just try to avoid opening up a cosmic string-related time wrinkle while mastering.

(And yes, when you’re all alone and no one is looking over your shoulder, you can do something useful with it.)

Pricing: US$249 (€195); US$999 (€799) Advanced.

Why is Advanced so expensive? Well, each module is also an independent plug-in you can use in your host. With that in mind, this starts to look like a better deal – some terrific reverb, EQ, and dynamics you can use anywhere. You also get the Meter Bridge and Meter Tap for analysis, fancier 2D and 3D spectrographs, and more advanced loudness meters. On the other hand, the basic version will also work with your host and gives you the sound-processing functionality minus all those more sophisticated meters you might need.

This month, there’s also steeply discounted intro pricing: US$599 for Advanced, US$199 for the standard edition. Expires December 1.

Ozone 5 was announced last month, but is now shipping. An OpenGL 2-capable video card is required for the 3D visualizations, but nearly all machines now provide that (including most integrated chipsets, too).

Ozone 5 Product Page @iZotope

For a look at what this tool can do, here’s our friend and experienced mastering and mix engineer Danny Wyatt, talking about how he works with limiting. The new UI and meters are actually a lot clearer than what you see in the video, and offer some nice, new functionality. I can tell you, Danny is a fully-converted Ozone lover, having worked with him in the studio as he mastered my own album. He’s got a big toolset of other stuff, but Ozone is very often what the real work comes down to, and — I think I can say this, Danny — he’ll be happy to evangelize the tool if you talk to him.

This isn’t a review, mind – in fact, my only significant reservation is that Ozone is so slick, it could distract from the reality that good mastering probably doesn’t need it. A great mastering engineer can do wonders with a fairly simple tool and their ear – no wild visualizations required. (“Great mastering engineer,” also known as, “not me.”) But that same person may well appreciate the level of precision iZotope, working with algorithms they’ve developed entirely in-house, can provide.

We want your feedback, as always. Ozone users – what do you think?

Users of rival products – what’s your all-in-one mastering tool of choice, and why?

Alongside its Pro Tools 10 and HDX unveiling, Avid turned some heads by recently announcing it was replacing its RTAS and TDM formats to a new format called AAX, “Avid Audio eXtension.” Now, your first reaction may not be unbridled enthusiasm, exactly: it seems the last thing users are likely saying is, “yes, please, I’d like a new plug-in format to worry about.” But I wanted to give the engineers at Avid a chance to tell us what they were thinking and why they made the move.

Avid’s product announcements have unfortunately coincided, presumably because of the financial calendar, with unpleasant restructuring and downsizing news, a topic NYC-based audio engineering site SonicScoop takes up. However, I prefer to focus here on the engineering side of what’s happening; we can look at Avid’s business and the changing business landscape another day. (For what it’s worth, I’m not as bleak as SonicScoop about the industry at large – least of all because I think the larger audio market remains healthy, even if Avid has been caught adapting to a new marketplace.)

The picture painted by Avid is one of a smooth transition to AAX. Now, of course, you’d expect them to say that, but I think they do have some specific technical reasons that, even with the change of name, the shift should be friendly to Avid developers. I’ll let them explain, though.

Bobby Lombardi, Senior Pro Tools Product Manager goes into the technical details of what AAX, and what it means for Pro Tools developers and users.

CDM: The main draw appears to be the ability to switch between native and DSP-based processing more easily, correct? From the end user perspective, can you get into specifics on what a user will see and how this will differ from RTAS/TDM?

Bobby: Visually, a user will see that the RTAS/TDM pop-up on the Pro Tools 10 Plug-in header has changed to Native/DSP. The exciting part is what they will hear. In the past, with HD Accel systems using a 24-bit fixed point processing environment, and host-based systems using 32-bit floating point processing, the gain staging could be quite different and produce significantly different results. With the introduction of AAX, sessions that migrate between host-based and DSP-accelerated HDX Pro Tools systems will sound identical.

How much work will it be for developers to migrate from RTAS/TDM to AAX?

Moving from an existing RTAS plug-in to AAX Native is relatively simple. Plus, once a developer has an AAX Native plug-in running, it will take a small amount of development effort to support AAX DSP. In comparison to TDM 56k used with the legacy HD hardware, AAX DSP is much easier to support and developers do not require specialized skills in writing 56k assembly code, so it opens up the opportunity for many developers to create DSP accelerated versions of their plug-ins.

We’ll still see parallel, separate versions of plug-ins for AAX Native and AAX DSP, correct? And some will, as with RTAS, presumably be native-only?

This is really up to the individual developer. Some developers may find it strategic to support one or the other, however Avid’s goal with this new format was to simplify plug-in development and reduce the complexity to support accelerated hardware.

RTAS and TDM are listed as “legacy” formats. Is Avid making any commitment to how long they’ll last?

The RTAS and TDM formats will continue to be supported in the 32-bit versions of Pro Tools but will not be supported once Pro Tools is released as a 64-bit application. The new AAX plug-in format is the bridge to 64-bit plug-ins for the Pro Tools and Media Composer platform.

Avid has expressed a desire to embrace open formats, but why is there still no common, industry-wide plug-in format? (Actually, there may be no good answer to that question, but I feel obligated to ask!)

We absolutely do embrace open platforms because they can open workflows that enhance the user experience. Part of the experience we need to ensure is that it’s stable, integrates well on our control surfaces, and provides a long-term commitment to the customer. For these reasons it’s important that we can design the plug-in architecture. For example, without designing AAX we could never give customers a plug-in environment that supports both DSP accelerated and native Pro Tools systems and ensure they delivered 100% sound parity. We hope that by providing a modernized AAX SDK for plug-in development, developers will find it easier not only to support Avid’s products, but also finding it easier to develop for non-Avid plug-in formats.

Any word on when we’ll see third-party plugs with AAX support?

More developers are coming online each week with their AAX offerings. We had over 25 developers showing over 60 individual AAX plug-ins at the AES tradeshow in NYC last month, and expect to see many more at the upcoming NAMM tradeshow. With the ability to provide all Avid third party developers a optimized development path to DSP-accelerated plug-ins, we do expect to see more DSP-accelerated plug-ins on the new AAX platform than the legacy TDM platform.

Thanks, Bobby. And for one other take, I happened to get to talk to Universal Audio about their transition. UA, given that they have their own DSP platform and support Avid’s rival packages, certainly aren’t dependent in their business on the Avid ecosystem (though you can be sure it makes a big part of their market). Anyway, here’s what they say; I’m guessing other third parties would say something similar, but if you’re a third party reading and wish to comment, please do so, and don’t let the fact that I only have UA here dissuade you.

Lev Perrey, Universal Audio Director of Product Development, responds to CDM:

Universal Audio intends to support AAX Native in conjunction with UAD-2 DSP accelerators ­ exactly like we have just completed with RTAS support in UAD Powered Plug-ins v6. There is no announcement as of yet as to when the transition to AAX will be complete but we are actively developing and committed to the Pro Tools platform. Pro Tools 10 does support RTAS and initial testing with UAD plug-ins shows it to work just like Pro Tools 9.

As for the significance question, for UA moving to AAX Native should be similar to our recent migration to RTAS ­ although it will be easier for us now moving to AAX since we have fully invested in direct Pro Tools development and better understand the Avid SDK.

We’ll continue to follow this story. Thanks to Avid for getting us more details; I know it’s appreciated.

More info:
AAX Audio Plug-ins @ Avid

“It must be a Thursday. I never could get the hang of Thursdays.” -Arthur Dent, in Douglas Adams’ The Hitchhikers’ Guide to the Galaxy

If you’re having any issue getting through your Thursday, it’s tough to beat some proper, good techno – the kind of techno anyone can love, even if they keep shouting about how they “hate” it.

Techno pioneer Carl Craig is still going strong, the kind of artist whose work seems to flow freely. He’s got the roots, having begun with Derrick May in Detroit, but he’s remained a font of new work and invention since, mixing his work with live and jazz music and even endeavoring to introduce young people to new music through a self-started not-for-profit. (Check the cat’s bio.) If you haven’t checked in with him lately, he’s touring … well, nearly everywhere, and is keeping the new sounds going through his Planet E label. Planet E turned ten earlier this year, accompanied by new a full-length and remix EPs, but here’s a quick test of what’s coming out of this label via SoundCloud.

Latest tracks by carlcraignet

I have Carl on the brain partly because I’ve learned King Britt (Saturn Never Sleeps) has new music with him. I owe King and SNS’ Rucyl Mills a good weekend hiding out during Tropical Storm Irene, where I got in to see King’s workflow – mixing MIDI with CV triggers, Mono/Poly with Maschine, analog sequencing with Ableton Live. (We maintained power through the storm. Can I please evacuate to a chilled-out studio session more often? I’m a very, very blessed person, and believe me, I’m grateful for those gifts, those moments.)

The resulting sound represents the best, most organic feel of the different generations we’ve seen of this music. Whereas once production was laborious, we now get to cherry-pick the most comfy tools, the looseness of live playing and analog gear twiddling and sequencing with the speed of a Maschine or Ableton setup on a laptop. And it comes out, with tracks that are improvisatory, relaxed, and naturally grooving. I think you can hear it in Carl’s new stuff, and I know I can hear it in King’s, having listened in and jammed as some things were made.

Remember handing burned CDs to DJs? In this case, Carl got hold of King’s tracks and King of Carl via email and Twitter.

For a glimpse, see the informal video. (I shot some video of King, too, but want to wait to get his and Rucyl’s word on their collaboration. Oh, and I need to, like, upload it. I’ll just ask my extensive video production department to– doh!)

Give King’s upcoming tracks on Planet E a listen.

King Britt presents Dynamic – Secret of the Stars b/w Things Take Time by planetedetroit

Here’s a look inside the session (and yes, that is a KORG vocoder):

King’s been doing this a long while, and his craft I feel is razor sharp, which lets him keep those tracks feel as loose as they do. He talks about how he tunes tracks in the mastering process on the Universal Audio blog. He definitely lets his UA fan side show, but he also gets loads of mileage out of some specific UA plugs – and the basic techniques here you can easily apply to any mastering plug-ins you like. (Readers recently brought up the excellent and underrated Samplitude, which is also a good choice with its integrated mastering tools.)

Give King talking UA and mastering workflow a read:

King Britt on Mixing “Bit by Bit,” by Saturn Never Sleeps [Universal Audio Producers' Corner]

More, mailing lists and blogs and whatnot:

King Britt.com
http://planet-e.net/blog/
http://www.carlcraig.net/

Integrated Melodyne pitch correction in PreSonus’ Studio One is made more interesting by the technology behind it. Celemony this week describes a new technology they call ARA, or “Audio Random Access.” The notion is this: rather than just receiving or generating audio signal, the plug-in gets access to audio data. That means you can actually write a plug-in that rewrites the audio content in a recorded DAW track, as Melodyne does in Studio One.

As developer Celemony describes it, “ARA opens an additional channel of communication through which the DAW and plug-in can exchange information about the audio file, tempo, pitch, rhythm and much more, which allows them to work together considerably more closely.”

It’s the ability to exchange audio data information that seems the most compelling. Previously, audio processing plug-ins simply took buffers of audio signal from the DAW. You could “look ahead” further into that signal by increasing the buffer (and thus latency with it), but generally speaking, you’re doing the processing in something that approximates real-time. ARA in the example of Melodyne gives you access to an entire recorded track without having to transfer the audio file to and from the plug-in.

Celemony says this is “an extension of the existing plug-in interfaces,” not a new plug-in format. (If it were the latter, I’d have to point to this xkcd cartoon.) I’m still obligated to express some skepticism about how widely this will be adopted, or if it can be considered a “standard” extension, though they do promise additional vendors soon. (Implementation would seem to be by necessity on a host by host basis – and then once you have the host, a plug-in creator might add support.) It’s a proprietary technology, but then, so are the plug-in formats currently in wide use (AU controlled by Apple for Mac OS, VST by Steinberg, and RTAS by Digidesign, unless we see more of LV2). For now, though, we’ll have to see if the idea itself can extend what a plug-in can do. Check out the videos for more.

celemony.com/ara (no documentation for developers, but there is an email address to use if you’re interested)

With soft synths a dime a dozen, how do you set yourself apart? Defying conventions is a pretty good start, and a team of developers who built the Mixxx open source DJ tool are doing just that.

SodaSynth from Oscillicious is a soft synth with a different approach. With no effects and, surprisingly, no filters, SodaSynth is all about the oscillators. But apart from its ready-to-layer sound, the developers are also making their software run in new places: aside from a VST, there’s a version for HP’s defunct TouchPad and, more interestingly, the first major soft synth we’ve seen yet for Google Chrome’s Native Client. We’ve got some details on the latter that will appeal to you hardcore Web browser / coder geeks out there.

First, the sound: with no filters and no effects, SodaSynth’s developers say they’ve made a synth that’s easy to layer. You get five waveforms, up to 32 oscillators per note, and full 8 note polyphony. (Per-note oscillators to me is where things get interesting.) The controls are pretty stunningly simple, but with five “classic” waveforms and some unique morphing settings.

Also, for those new to synthesis – and for some of those more unusual parameter names new to all of us – they’ve added extensive in-line online support, in a nice touch. (More in the gallery/sounds below.)

I’m in. Mac and Windows VST, and should run fine on Linux machines with Windows VST support. US$23.

SodaSynth VST

Here’s what it sounds like:

SodaSynth VST Demo 1 by Oscillicious

And there’s an HP Touchpad version, which you’ll find for $3 in the HP App Catalog. Notable in that it may soon join our Doomed Tablet Instruments Hall of Fame. (Our friend Francis Preve had an instrument out for the Newton. Really.) Seriously, if anyone has a TouchPad, send us video, ‘kay?

But more practically…

You can run SodaSynth right in Google’s Chrome Browser. We’ve seen plenty of synths and even full-blown workstations employing Adobe’s Flash. And there have been some projects built in JavaScript for Mozilla’s Audio Data API, previously called the Web Audio API (which I liked better as a moniker). Tons of examples via the Chromium site; Chrome and now an experimental Safari build have added support:

Web Audio API Samples

Soda Synth uses a third avenue, one which I’ve heard lots of people talk about but no one actually try. Google’s Native Client allows you to run native code right in the browser – not this JavaScript kids today love so much, but good, old fashioned, C/C++.

What does that mean for synths? Think low-latency live audio that out-performs other solutions, at least for now. SodaSynth isn’t just the first NC synth in the Chrome Web Store; according to the developers, it’s the first Native Client app, period. (Answer to the question “who cares whether you use native code ever again?” is, of course, “audio people.” I’m sure JavaScript advocates will be happy to chime in here, but even if JavaScript matches C/C++ performance, the ability to run C DSP code natively will continue to have advantages down the road.)

It’s free, so add it to Chrome now, and you get a synth you can jam with – there’s even a 4-bar live looper so you could produce actual sound snippets with the thing. I’m curious to hear your experience.

SodaSynth, free for Chrome Web Store

Developing in Native – Why it Matters, What it’s Like

I’m all about getting the nitty-gritty details – yes, including not only why this is exciting, but what the development process is like, warts and all.

Developer Albert writes:

Why is this news? It’s native compiled C++ code running our synthesizer in a browser at full speed, for the first time. While there’s some other pro-audio web apps like AudioTool, nothing can really get the latency low and run efficiently without native code. We think this might be a peek into a future where we there’s real pro-audio web apps.

I asked Albert specifically what challenges, if any, they’d encountered. Albert tells CDM that NaCl (get it?) still has some rough edges and needs further testing, and significantly isn’t enabled by default for some users. He did qualify that by noting NaCl’s developers have been generally helpful.

The Pepper Audio API that NaCl implements is pretty similar to SDL and performance seems to be good. The three big advantages of using NaCl over Adobe Flash for this sort of thing are raw performance, being able to directly set the audio latency, and that most audio apps are already written in C/C++, so they’re easier to port. Being able to just upload your binary to “deploy” it instead of building Windows/Mac/Linux versions is a huge time saver too.

Currently, I’m only hosting binaries for x86 and x86_64 because the Native Client doesn’t actually work on ChromeOS yet. One of the main
NaCl developers mentions this [2], though perhaps that’s been miscommunicated by Chrome’s marketing team, because I too thought it
was supposed to work.

The next milestone for the Native Client team is to implement “Portable Native Client”, or PNaCl [1], which will mean that NaCl apps will get distributed as “LLVM bitcode” instead of compiled architecture-dependent binaries. In other words, you will compile your application once, and it should run on x86, x86_64, and ARM. I think Google is waiting for this before pushing NaCl into ChromeOS.

“Early days” seems to be the key phrase here, but I’m eager to see Google put some resources behind this and turn this into a solid solution, especially on their nascent Chrome OS. (Too bad, as I was looking forward to seeing someone fire this up on a ChromeBook.)

For further reading, via Albert:

[1] The gory details about the proposed PNaCl plan
[2] Chrome/NaCl engineer at Google saying it doesn’t work in ChromeOS

More Images + Sounds

A song without and with effects, using Renoise:

SodaSynth VST Demo 2 (Dry – No Effects) by Oscillicious

SodaSynth VST Demo 2 (Wet – With Effects) by Oscillicious

The VST version:

Image of the ill-fated HP tablet version:

http://www.oscillicious.com/

MOTU’s MachFive sampler, while perhaps not getting the kind of attention rivals from NI and Steinberg have, has had in its history some compelling features. Those features were in a multi-window interface, though, that not all of us loved – while I can’t find the review, I know when I covered it for Keyboard, I praised powerful editing features like the slicer but lamented the UI.

MachFive’s new UI looks radically different. The tabbed layout and modules and preset browsing all recall NI’s products, but there are new twists, too, like slick, readable waveform views, gorgeous EQ visualizations borrowed from MOTU’s DP DAW, and plenty of shiny. The results look far more usable, which means easier access to new sonic capabilities. And that’s good news, because it’s those features where things get interesting. Just a few highlights:

• Granular stretching and re-pitch sounds, licensed from IRCAM. I’m fairly certain this is the first time I’ve seen the Paris research center as a specific bullet point in product promo, but there are samples that sound terrific.
• New scripting which MOTU touts for modeling things like strumming and fingering on guitars – and lots of other things, too. New sound content will take advantage of the scripting features. And, oh, yeah, if you’re thinking that scripting is available elsewhere, CDM’s nerdier readers will like this: the scripting engine is now in Lua.
• Hybrid synth engine covering wavetable, subtractive, and FM synthesis. Earlier today, readers were talking about disappointment that Omnisphere, the massive sample-based synth, lacked samples. Well, here you go – here’s one strong sample/synth hybrid contender. (Omnisphere’s another animal, but that doesn’t make this any less interesting.)
• Modular effects architecture, convolution reverb mean greater ability to apply effects, from buses to individual oscillators and keygroups.
• Oberheim-style Xpander filter.
• Tons of ready-to-use MIDI scripting.
• Powerful arpeggiator and micro-tuner.

You also get 45 GB of sound content (wowsa), full-screen mode, an updated slicer/looper, and expansion of MachFive’s already-extensive support for third party samples, even including obscure old formats.

I’m intrigued: the intelligent new layer rule interface, the overhauled UI and sound engine, and then extensive micro-tuning and Lua scripting start to make me interested, even with intense competition in this arena. For experimental sound design, there’s some real potential here. Stay tuned.

In the meantime, pictures:

More:
http://www.motu.com/products/software/machfive/

http://www.motu.com/products/software/machfive/technology.html

I took a look at Omnisphere 1.5, the synth so big it’ll make your head hurt, for Keyboard in a story out now (and readable now). As I begin the story:

Seeing its six DVDs of sound content, you might be tempted to duct-tape a key down and let Omnisphere finish your film scoring gig. While the director would probably love the results, you’d be missing out on the real fun.

In other words, what I discovered in that review was that Omnisphere, particularly with additions in the new 1.5 update, is a powerful creative sound design tool, not just a preset machine. The highlights:

• Granular section, pictured, made nicer with the ability to combine with glide and intelligent parameter control design
• Harmonia, which allows you to control each harmonic component of a sound independently using individual oscillator and synth controls
Waveshaper, which can not only add bit-crush-style effects, but work its magic on each element, polyphonically
• Individual independent arpeggiator, plus MIDI file drag-and-drop
• An Orb for exploring sonic capabilities – we’ve seen these sort of X/Y controllers before, but here you can even dynamically assign parameters in realtime, and add features like inertia and gesture recording
• iPad control via a really wonderful controller app

Being able to navigate multiple sonic parameters in real-time with touch, and combining sound-bending, far-reaching sonic tools like Harmonia and the granular features means you can really take sounds far from their original source – and sync them to tempo, if you like, with those MIDI and arp features. I need to pick up the whole tool again after the review and see what new sounds I can make; if there are any other users who wish to share, I’d love to hear what you’re making, as the possibility is really deep.

And yes, they now have done a dubstep bass tutorial, so everybody playing at home should take a shot.

Read the full, detailed review at Keyboard Magazine:

Spectrasonics Omnisphere 1.5 [Review by me for Keyboard]

How does it all work? Here are some relevant videos:

Universal Audio has a big set of updates to their DSP software out today. It seems worth sharing in part because I find the (faked) look of that Ampex reel-to-reel does give me a warm and fuzzy feeling, even if it mainly makes me want to get in a studio and hear the whir of the actual gear.

Here’s what’s in the update:

For Pro Tools users, there’s vastly-expanded support, including native RTAS plug-ins (instead of the VST-to-RTAS adapter), control surface support, proper automatable parameters, and correct naming and sorting, plus a quicker installation and workflow. I’m embarrassed to say, not having tried UA’s stuff in Pro Tools, I was unaware they’re missing – that sounds like the set of functionality that would make mixing UA and Pro Tools genuinely workable.

Full Mac OS X Lion compatibility is a big deal. We’ve seen a lot of Lion support arriving lately, and I saw readers specifically complain about the lack of support in the update. Seeing a hardware DSP platform with support seems to me a good sign, because it means both plug-in and I/O compatibility have to be in place. It’s getting to be about time to do a new compatibility update, and it may be an OS update that’s possible to recommend shortly (though Snow Leopard is working just fine for now).

Then, there are the plug-ins:

Brainworx bx_digital V2 EQ: This popular mastering EQ now comes to the UA platform, with M/S mastering, M/S recording, and L/R stereo modes. It’s kind of an EQ-plus, with M/S de-esser built in and mastering-specific EQ options, plus a mono plug for mixing.

SPL Vitalizer MK2-T is back in the emulation territory, modeled on the tube-based gear. Separate bass and mid-high modes give you frequency-specific loudness controls.

Ampex ATR-102 models the legendary two-channel tape, and has Ampex’s seal of approval. That means UA now models the two studio workhorses, the Studer A800 (see our previous coverage and shameless gear pr0n gallery) and the Ampex. ATR users and engineering titans Chuck Ainlay, Richard Dodd, Buddy Miller, and Mike Poole contributed presets, in a nice touch. US$349 buys you the plug … and yeah, that’s likely to make a few studios nervous on their rental fees. Then again, look at the names on the presets, and remember just how valuable engineers are, whether they’re behind an analog deck or a computer with a UA plug. (Take it from me – someone who’s not really an engineer.)

The SPL and Brainworx plugs were each developed outside UA. My guess is that Pro Tools support is a factor in seeing more third-party development. And while readers correctly noted the demise of other DSP platforms, UA’s is looking very healthy from a business perspective.

The only bad news: I’m confirming this, but there appears not to be support for 64-bit operation on Windows, which remains a significant omission in UA’s software.

Now, we need some double-blind A/B tests with both the Studer and Ampex (and maybe the real gear). Wonder if someone could help us set that up.

I really enjoyed some of the skepticism in comments on the last article. I think the questions “do I really need this?” and “will this give me the most value over time?” and “what alternatives should I consider?” are absolutely the questions you should ask about any music tech products. This is a news item, so I’m not anywhere near knowledgeable enough to comment in this case. I think the best thing to do is, beyond just reviews, continue to talk to producers and engineers about how they use software, and to developers about how it’s made. If you have specific questions, let us know.

And let’s have another look at the original. Simon Campbell on Flickr has this shot of one with the spools spinning:

We mastered onto this rascal at 30 ips using Dolby SR. Nice.

Recording the album ThirtySix at Gracieland Studios [UK], Rochdale

Photo is (CC-BY-ND) Simon Campbell, whose music you can go hear (linked via his name).

Universal Audio Downloads for the latest updates | Universal Audio Site