Yeah, templates make that much easier. Since templates seem to be a combination of everything, if I can blanket apply it to all the rigs that would work.
Weird bug I've noticed, when I start AM and go to miners tab and use Ctrl+A to select all the miners it crashes AM. Also you can't globally stop all miners. Say selecting them all and selecting stop IF one of the miners is already stopped. Small thing, but you have to use ctrl to unselect some of them so you can stop the others.
Affinity is another needed option. Although understanding affinity and how it selects CPUs is a bit of a chore. There is a mathematical equation for it.
bensam1231, Thanks for all feedback above. Everything is noted, and I will comment on some topics below.
Going back to the discrepancies between Afterburner reported GPU, System reported GPU, and miner reported GPU stats (which should be noted clearly somewhere), why does AM wait till the miner is running before reporting GPU stats? Is this because some of the information is pulled from the miner? It would be nice if it was reported all the time even if you can't report things like hashrate till the system is fully mining. Sometimes you'll be using a miner that isn't supported by AM as well (which is why being independent from mining software is a good thing).
It's true that the GPU tab doesn't show any information when not mining, but the System tab always show the information for all GPU's.
The purpose of the GPU tab is to show mining related information, including only those GPU's used by a specific miner. This can be fewer than all the GPU's you have in the system. The GPU tab is also focused on providing hashrate statistics per GPU, which is also very related to the mining operation.
The System tab always shows all GPU's, and also some basic CPU/RAM/HDD information. This information is always available even when not mining. As I pointed out earlier, some informaiton, especially for CPU, is not available unless you run in Administrator mode.
As you know, the feature "Map to system monitoring" is really about bringing in the information from the System tab to the GPU tab, to make it more complete for a specific mining operation point of view.
I haven't take time to play around with this yet, but when running a completely foreign miner (IE nothing AM is built for), I assume AM will monitor the process and while it can't see what's happening inside of it as it doesn't have a API (black box), it should be able to tell when the process hangs according to the system and restart it. Additionally adding the ability for the miner to be restarted every X number of minutes would be useful. Currently a miner unsupported by AM I'm mining with requires me to change the priority on it and since I can't do that, I can't use AM with it.
If you use unsupported mining software (Generic Miner), Awesome Miner can still provide you with GPU information on the System tab. But Awesome Miner can of course not show hashrate or even have an idea of which GPU's that are actually being used.
For a Generic Miner, where an API isn't available, you are correct that Awesome Miner can still start and stop the mining process, and also restarting the mining if the process crashed. If you need to restart it on a regular interval, you can define a rule for that. In Options dialog, Rules section, you can add a new rule with a "Time" trigger and for example a "Miner command" action to perform a restart.
Would it be fine if I simply implement the "Process priority" setting in the properties for a Managed Miner, so you manually need to set it per miner? It will of course be supported in the Managed Templates as well.