We discovered AC about a year ago. There were some initial problems, but the author has been responsive to requests, supporting multiple streams on the 002, adding specially requested features, and fixing bugs. (This is one of the reasons I prefer independant developers; they actually answer email.)

We are now using AC for all of the recordings at the University of Utah Gardner Hall. We use it because it is simpler and easier to script than ProTools or Logic. (Both of which we own and use in other labs.) We also use it for automated recordings.

We have it set up with five instances (copies) of one AC running on one machine, each routed to a different input stream from a 002 (and one routed to the line input). We have the automation set so it will record each hall or recital room (five total) whenever there is any signal. This means we basically record everything all the time in five spaces. So we have been running AC constantly, an average of 10 hours a day, 7 days a week, five concurrent copies for about six months. It has been extremely robust and reliable, with rare failures, yet simple and staightfoward for our application.