Running EchoMac 1.16.1 (1.16) under Mac OS X 10.6 Snow Leopard works - but after quitting the programme it leaves running a process named echomac that can easily consume 100% (on a dual processort MBP) CPU power - noticeable by your running fan.
I guess it is not too difficult to fix.
Thank you for another reason not to start Windows on my MBP - and the possibility to get onto Echolink.
Bug fix for the time being: Start Activity Monitor, enter echolinux in the search box, select the process echolinux and stop the process by clicking on the STOP button after running EchoMac.
I can confirm this bug. On quitting EchoMac 1.16.1 on Mac OS X 10.6.1 there is a process running called 'echolinux' consuming 100% of the CPU. Running a 'kill -9' on the process ID fixes this but not ideal.
I just compiled the latest trunk from SVN and I did not have an issue with the echolinux bug. Now, I did build with gcc 4.2 and sdk for 10.6 only. So there may be something new in the latest libs. I will try building under 10.5 sdk later. I do not have the default 10.4 installed at this time so that won't happen. I did and still do have issues with the compiled app from sourceforge so I have experienced the issue when running that build.
I intend to statically link the echolinux and echoaudio code into the Echomac application. This should resolve the problem.
This should be fixed thanks to Gary Propp in EchoMac 1.16.2 and later.