| depends on your priorities but here's my take :
i heard an AWS awhile back and was impressed by the sound. had just been on a G+ the day before so the memory was fresh. the AWS is very open sounding and has huge amounts of headroom, but i ended up buying a D-Control. these are the main reasons:
1) i'm on PT, and AWS only does HUI for PT, so no spreading plugs on faders, etc.
2) 2 different automation programs seemed impractical to me (Awsomation + PT automation). some AWS users end up doing alot of the automation ITB even with AWSomation on hand, so it kind of defeats the purpose - so workflow wouldn't be as smooth imho.
3) already have several pres so no need for onboard pres.
4) too few channels on the AWS to be a fully OTB solution, and control for PT isn't in the same league as Dcontrol (on other DAWs with Mackie control it's alot more comprehensive).
5) most importantly i'd achieved satisfactory results with a hybrid approach before deciding.
pros for AWS:
1) latency free monitoring when tracking.
2) small footprint.
3) the sound.
4) SSL name.
5) works on several platforms.
a large part of my decision had to do with the fact that i work with PT exclusively; even then it was a difficult decision as the AWS is a fine piece of equipment - really depends on individual needs and sense of aesthetic.
don't think Command 8 will control Logic but not 100% sure. M-Audio Project Mix does control other DAWs besides PT, but not sure if it'll work on HD.
my advice is spend enough time on an both AWS and Icon systems before spending your $. there are several AWS and Icon users on this forum, maybe they could comment. |