I've been using Sonar since 2000. They came a long way for sure since then. I do pro work with it and it is indeed a solid DAW when run on a good system. The one perpetual issue - and I mean, significant issue - is the high cpu (sonar's cpu) hit when trying to create a networked system (and I've read a handful of folks having trouble with a few VSti's here and there). Apparently, it's how Sonar handles buffering data. This was confirmed by first checking windows resource manager which does not reflect the high usage. Secondly, the networked system was tested with other daw's and they did not exhibit this behavior and those few people with the VSTi issue tested those VSTi in other daw's successfully. Cakewalk needs to buckle down on this problem before having fancy new releases. Other than these specific scenarios, cpu usage within Sonar is totally fine as well as overall performance and usability.