HA - are there plans to add in the ability for the user to select more than one version of cc-miner? For example, there are a few different x16r ones out there (e.g. enemyminer 1.03) that work. Some also algorithms see improvemnts with KlausT or Alexis, for example. Having just 3 miner choices (tpruvot, dstm, and ethhash or whatever) seems a bit limiting. Would it create more problems than it solves to allow for different miner software?
I went with Klaust's variant of CCMiner as it is still being actively maintained and it is a bit faster with some algorithms such as Skein and Neoscrypt. Also, I decided upon Nevermore miner instead of EnemyMiner because there is no longer an official repository for EnermyMiner. That makes me wonder about that software's future and the integrity of some of the copies of EnemyMiner floating around. The developer of Nevermore is pretty active when it comes to improving his product and that miner is a bit faster at mining RavenCoin than CCMiner 2.2.5. I also added an Xevan miner even though it has not been updated in a while since some coins that use that algorithm are still profitable and the miner seems pretty stable despite its age. I'm hoping that the upcoming Monero fork will help make Cryptonight mining profitable again, which is why I added XMRig.
Stability issues are still my primary concern when it comes to evaluating which miners to add. For instance, I looked into HSRMiner for Neoscrypt, but a lot of users say that after a few hours it is no faster than Klaust and there are quite a few stability complaints. Similarly, I have held off on including the latest release of Ethminer because its release candidates have broken a lot of basic things at one time or another according to the Github issues list. Of course, I'll continue to watch the development of all these miners and update Hash Auger accordingly.
There is still a bit of tweaking potential in the current versions of these miners to improve both their performance and stability. Obviously over-clocking is part of that, but the CCminer-variants also support adjustable intensity levels for each algorithm. The miner developer assigns a default intensity to each one based on their own testing. Yet the default intensity level is not hardware-dependent; too high of an intensity level can cause stability issues and too low of a level can reduce performance. Version 1.6 of Hash Auger allows users to define custom intensity levels to help address both issues, but I am looking at ways to automate to process of selecting the best intensity level per device for a future release.