With relatively little fanfare, Cakewalk released Sonar 7 this month. It looks like it has some really nice features. I've got the Studio edition, and I'm going to review it for Ars. There's just one problem:
Where to start?
It's possible, with Pro Tools, to feel like it's a very simple program. That's mostly due to the window layout, which is incredibly friendly and simple. Pro Tools rarely (if ever) has more than 3 windows onscreen at any time--Edit, Mix, and Plugin. There are menus and subsections for those windows, but when they added right-click support in 7.3 it meant that you could basically ignore 90% of those. So even though the software is actually fantastically powerful, you don't really notice most of it.
Sonar follows a different kind of metaphor. It's more like Cubase. There are lots and lots of windows and palettes and menus. It doesn't make it hard to use, necessarily. In fact, because almost everything in Sonar can be customized, including the menus, you could probably make it look a lot like Pro Tools. But out of the box, Sonar looks like something complicated, and a little overwhelming. It doesn't let you forget just how much there is.
Because let's face it, these packages--any of them, from Live to Logic--are really unbelievably full-featured. Any tool at this level is. That's one reason why people complain about Word: it is stuffed full of functionality for working with text--so much so that you sometimes can't find the feature you need. Final Cut Pro has the same kind of in-your-face complexity. Don't ever press a button on the keyboard unless you absolutely know what it does in Final Cut. They're all mapped to something. I accidentally hit the keys with my elbow the last time I did an editing project, and it took me five minutes to put everything back.
So how do you review something that big? Where do you start? Surely, I can't review everything in the package. It would take me months. And that's assuming I even know what to do with those features--like Word, each of them is probably used, but perhaps only for certain kinds of projects.
My plan is to use Sonar like I would do my work projects--meaning that I'll do a little radio recording, a little instrument recording, and some midi composition. I'm also going to download some of the NIN multitrack files and load them in as a way to test the mix engine in 32- and 64-bit modes--I doubt any of the material I have lying around is high-fidelity enough to make a difference.
There's also some standard bullet-points that are different from the other DAWs, and I think it's important to test those. So I'll be putting AudioSnap, ACT mapping, sidechaining, and the various VST instruments under as much scrutiny as I can apply. I'm open to other suggestions, but I think those are the main points.
The bad news is that no matter what I do, I'll feel like I haven't done it justice. But the good news is that DAWs have reached the point where the basic functionality is the same from system to system, so I hope most users will be able to fill in the gaps.