Patrike,
Could you add something to profit profile for me? Could you add under Profit Profile, when you select an algo from the list on the display under gpu clocking profiles start and stop, could you add a line for "execute batch file before start mining" then a selection to allow us to link to it either local or remotely.
This simple addon would allow people to use third party OC and Settings without a major overhaul to Awesome Miner.
Example on a remote rig, i could then create a folder for all my OC batch files, then create a new one for each algo like Skein.bat, then link to it so we can use Nvidia Inspector without you having to implement it and get rights to use someone elses software....
+1 for batch file use
Patrike,
After thinking this over, it may be better to add the execute batch file function under profit profile GROUPS, reasoning is you could execute 1 single batch file for that entire rig group
Hi,
I may have to add a setting like this both to the Groups and to the Profit profile itself. Unless you have a mix of cards, most people don't use the Groups concept as it's mainly about adding up the numbers for mixed GPU systems.
For launching an external application, what I had in mind was the following to be configurable per algorithm in each Profit profile
- Launch before miner starts
- Launch before miner stops
- Launch after miner stops
In addition to this, I also plan to support adding a custom command line configuration to be passed to the mining software per algorithm in the Profit profile.
The same settings for launching external applications in these three scenarios could then be added to both a Managed Miner (that do have a batch file concept, but it's not a as flexible) and maybe to the Profit Groups as well as you suggested.
I get what your saying, adding it to both groups and individual profit profiles would cover the masses.
I would keep it simple like your gpu profile,
Execute batch files
*Launch before miner starts
*Launch after miner stops
In regards to managed miners, i would just add the same execute batch files options under managed templates, i would just add it as an *alternative to the gpu clocking profile option you already have built into the template options. so when they load a new template, the template could be specific to that rig and load those settings or batch files on launch.