Let's face it: Pro Audio was approaching a turning point. After nine versions Pro Audio was saddled with a long feature list including many features that most people would consider esoteric (such as a programming language, CAL, and object-oriented studio controller builder, StudioWare) and some features which should be obsolete (such as destructive editing tools for lowering volume and normalizing) it was time to clean out the deadwood and make room for new growth. We will see, however, that more pruning could have been done.

But first, let's review the new stuff. There's a lot to cover.

Serious New Technology

To me the most impressive aspect of SONAR is that it is one of the first multitrack audio applications to truly capitalize on new technology from Microsoft: Windows 2000 and the WDM driver model. Besides offering increased OS stability, Windows 2000 supports symmetric multiprocessing, allowing a properly-written application to spread its resource requirements across multiple processors. SONAR takes full advantage of SMP, running strongly with two processors.

Some people will point out that having multiple processors does not actually double performance. Typically users will see, for example, about a 1.5X increase in CPU performance (meaning 50% more plug-ins) when running two processors. However, a side benefit is that even though certain application threads (like mixing) may bottleneck one CPU, the other CPU is usually not bottlenecked, providing, for example, fast user interface response even under heavy mixing loads. The bottom line is that with two or more processors, many functions in SONAR feel fast even when the app is loaded down.

WDM is Microsoft's new driver model which provides kernel-level streaming. WDM drivers differ from MME drivers by having fewer program layers between the application and the hardware. The net result is that a properly-written WDM driver can achieve latencies as low as 1.5 ms – low enough to support realtime processing like software synthesizers and live audio effects monitoring. Look out ASIO, here comes WDM.

Why didn't Cakewalk choose ASIO instead of WDM? Well, first there's the obvious answer: Steinberg controls the ASIO spec, and could change the driver model without notice, thus keeping Cakewalk on uneven footing. However, there's a more important answer for the consumer. WDM is an open driver model, and it's endorsed by Microsoft.

Ah, Microsoft. As much as we all like to hate Microsoft, the fact remains that operating system support is the most critical factor in determining the success of a software platform. And few are the cases in which Microsoft technology did not dominate its competitors. By choosing WDM instead of ASIO, Cakewalk and Microsoft have created a powerful alliance. Moreover, other software companies are getting on board Microsoft's WDM model, clearly paving the way for a truly professional audio driver standard for Windows. This is a Good Thing.

Note that you do not have to use Windows 2000 (or Windows XP) or WDM drivers in order to use SONAR. However, there are two aspects of SONAR that require low latency in order to be useful: live performance of software synthesizers and live audio effects monitoring. These features do not perform fast enough without WDM to be useful. You can make the move to SONAR when you're ready, but to take full advantage of everything SONAR has to offer, you'll want WDM, and to get the best performance, Windows 2000.

OK, enough of the under-the-hood stuff. Let's listen to the bells and whistles.

Software Synths

Probably the hottest aspect of SONAR is its support for DXi software synthesizers. DXi - which stands for DirectX instrument - is a new standard for creating a software synthesizer that functions like a DirectX plugin. Functionally, DXi plugins work like Cubase vSt plugins – you just insert them like a plugin into the application and play them with any MIDI controller. Although Cakewalk created the DXi standard, it is based on standard DirectX technology, and, most importantly, is endorsed by Microsoft.

If you've never used a DXi or vSt synth before, then you may be missing the most important part of the technology: since the synth is plugged into a project file, its settings are saved with the project whenever you save, and are instantly recalled when you open the project. So instead of having a rack of hardware synths, which all have to be set to their appropriate settings in order to re-create a MIDI song, the synths all instantly recall their settings whenever you load the song. Softsynth plugins are great. I love being able to create a sound in a plugin, and follow it with a DX audio effect - say, a Rhodes piano synth plugged into an FX2 amp simulator plugged into an FX3 room simulator. Great sound, and emminently playable.

Of course, the other thing is simply that software synths are cool and sound great. SONAR comes bundled with several DXi instruments to help you get started, including a software version of the Roland Sound Canvas called VSC, a software Soundfont player called LiveSynth, a modular synth called Tassman, and Audio Simulation's DreamStation. Tassman in particular is complex enough to justify its own article, and as a modular synth is exceeded in capability only by Native Instruments' Reaktor synthesizer (a DXi version of Reaktor is also in the works). Suffice to say, if you're a synth tweakhead, you'll love Tassman. Between VSC, LiveSynth, DreamStation and Tassman, there's more synthesis included in SONAR than you're likely to find in your local music store.

above - Dreamstation analog synth

below - Tassman modular synth

And if the included and upcoming DXi synths aren't enough for you, then check out Amulet's VST Adapter 3.0. VST Adapter 3.0 allows any VST plugin to be used inside a DX application like SONAR, instantly giving the SONAR user access to any VST instrument or audio plugin. With the immediate ability to use any VST or DXi synth or audio plugin, SONAR now sets a new standard for offering more plugin power than any application currently available.

The other benefit to DXi technology is that it allows an audio plugin to be MIDI controlled. This allows you to automate the parameters of your EQs, reverbs, flangers, and vocoders. DX plugins must be rewritten to support this new feature, but SONAR ships with several plugins from PowerFX which already support MIDI automation. VST plugins running in SONAR using VST Adapter 3.0 can also be automated, just like they can in Cubase. However, DirectX audio effect parameters can be envelope automated at a resolution and accuracy much higher than MIDI-controlled plugins like vSt plugins. DX plugins must be rewritten to support this new feature, but SONAR ships with several effects from Power Technologies which already support automation.

Audio Looping

The other SONAR feature that has users talking is its support for Acidized audio loop files. This allows you to construct and arrange songs using loops, just like in Acid. SONAR takes this one step further by supporting MIDI loops which work just like audio loops. And, whereas Acid forces the user to a one-track-per-loop model, SONAR allows the user to mix loops on a single audio track.

SONAR Loop Construction window

Article Continues >>

TrackbackPrint

Location: BlogsProRec ArticlesRip Rowan

Your name:
Your email:
	(Optional) Email used only to show Gravatar.
Your website:
Comment:
Security Code Enter the code shown above in the box below
Add Comment  Cancel