Sorry...

The 'Lost in translation' I was referring to was Reaper's Local Hash Rate vs CGminer's Local Hash Rates being different, yet VERY similar Submission Rates.

*(if it is simply a math problem, or share difficulty issue and reporting)*

What hashrate does your pool report you submitting?

The pool reports me accurately with slight peaks and valleys for luck, ~ 9.5 MH/s total

That is:

- 15x 7970 (approx 500+ kh/each)

- 3x 5830 (820 kh/3....single rig)

- 2x 5770 (400 kh/2....same rig)

- 1x 6950 (395 kh/s)

=======================================

**MINER1 (2.15 MH/s)**----------------------

4x 7970 @ 925/925, 1040mV

worksize 256

aggression 13

threads_per_gpu 5

sharethreads 18

lookup_gap 2

gpu_thread_concurrency 10240

=======================================

**MINER2 (2.15 MH/s)**---------------------

4x 7970 @ 925/925, 1040mV

worksize 256

aggression 13

threads_per_gpu 5

sharethreads 18

lookup_gap 2

gpu_thread_concurrency 10240

=======================================

**MINER3 (2.61 MH/s)**----------------------

5x 7970 @ 925/925, 1040mV

worksize 256

aggression 13

threads_per_gpu 5

sharethreads 18

lookup_gap 2

gpu_thread_concurrency 10240

=======================================

**MINER4 (820 KH/s)**--------------------

3x 5830 @ 840/800, 1055mV

worksize 128

aggression 17

threads_per_gpu 2

sharethreads 18

lookup_gap 2

gpu_thread_concurrency 6144

=======================================

**MINER5 (395 MH/s + 980 MH/s + 400 MH/s)**---------------------------------------

1x 6950 @ 800/800, 1000mV

2x 7970 @ 900/900, 1000mV

2x 5770 @ 850/1200, 1050mV

worksize 256 (

**6950**)

aggression 18

threads_per_gpu 2

sharethreads 18

lookup_gap 2

gpu_thread_concurrency 8192

----------------------------

worksize 256 (

**7970**)

aggression 13

threads_per_gpu 5

sharethreads 18

lookup_gap 2

gpu_thread_concurrency 10240

----------------------------

worksize 128 (

**5770**)

aggression 17

threads_per_gpu 1

sharethreads 18

lookup_gap 2

gpu_thread_concurrency 6144