As a workaround, you could run several instances of cgminer, each managing 8 or whatever # devices works. You can define which devices each instance manages by using --device.
In the long run, I think its clear the GUI has to be separated from the miner, so ckolivas can concentrate doing what he does best, and any half competent dev can make a gui using the API. Of course then the API should work and not crash, its something I havent heard before, I hope someone looks in to that.
In that context, Id also like to bump my earlier feature request:
Got another feature request for the API. 2 in fact:
1) be able to read the worker name of a pool over the API
When using multiple workers for things like GPUmax, its currently impossible to distinguish between them. I can understand password being hidden, but the username is even visible on the screen, so why not expose at least the worker name over the API when calling the "pools" command ?
Pull request is up for this.
https://github.com/ckolivas/cgminer/pulls2) ability to delete pools over the API.
This has been discussed before, but its possible to do it in the CLI, it would be great if this were enabled over the API too; its one of the last things an alternate GUI using the API cant do.
Ill pledge 2.5 BTC for each feature if they make it into the mainline.[/i]
I don't like the idea of throwing away information ... when you delete a pool you lose all it's info.
Convince me otherwise why you think this is good or needed.
No I'm not asking for more BTC - I don't want more BTC - just a reason why it's not bad to throw away the pool stats for the pool you delete - and thus why you ever use more than 32 pools
