Ralph, This is a known problem. It's a message race condition between the action and the application or monitor window that's keeping an eye on that action. You've already checked the log, but I'll repeat this advice for anyone else reading. If you get a "lost communications" error it just means that the user interface lost it's communications link with the running action. It might mean something horrible has happened (like the action has crashed), or it might just mean the link between to two went dead. The first thing to do is to look at the log and find the action. It the log for that action says it finished (as in "Capture finished") there's nothing to worry about. This loss of communications between the UI and the running action has been popping up since Snow Leopard, and seems to be worse in Lion. (Apple has been getting agressive about conserving power when the computer is idle, but sometimes things are so quiet now the monitor thinks the action has died.) I've recently changed some code to address this issue and it seems to be helping. I haven't recorded a single "lost communication" error in the past week on any of my test machines. If the fix is stable, it will roll out with version 1.2.1, which should be released within a week.
|