KCK wrote:I find it hard to believe that KProbe's running at about half of the desired speed has gone unnoticed so far.
That's because it hasn't.

Well, at least it hasn't gone unnoticed for very long. This is a new bug that was introduced in 1.1.13 (which wasn't available for very long before it was replaced with 1.1.14).
I was a little surprised to read the comments about KProbe testing at half speed (i.e. 4x instead of 8x), because although I normally only test with the MAX box checked, I have tested in the past at 8x and it seemed to take the right amount of time. However, I never sat down with a stopwatch and timed it, so I thought I would give it a go. Sure enough, as you reported, KProbe 1.1.14 is testing at speeds slower than the speed set in the configuration box. On my LTR-48246S, KProbe 1.1.14 tests using the correct speed when the MAX box is checked, but takes 19:51 to test a 79:27 disc (an average rate of 4x) at the 8x setting.
This didn't square with what I remembered in previous tests at 8x, and until today I hadn't done any tests at anything other than MAX using 1.1.14, so I reverted to 1.1.13 and 1.1.12 to see how they do at other than MAX. Version 1.1.13 also has the bug, but with 1.1.12 everything tests out fine:
- Code: Select all
KProbe 1.1.12 on LTR-48246S SS0E
set speed elapsed time actual speed C1 avg
----------------------------------------------------
4x 19:51 4x CLV 0.157
8x 9:56 8x CLV 0.165
12x 6:37 12x CLV 0.195
16x 4:57 16x CLV 0.144
24x 4:38 24x CAV 0.403
32x 3:20 32x CAV 0.684
40x 2:37 40x CAV 0.767
48x 2:14 48x CAV 0.262
MAX 2:14 48x CAV 0.264
In this rare case my memory was correct.

Older versions did test at the proper speed as set, and the problem is a new one introduced in 1.1.13.
Alexnoe over at CDFreaks offers an explanation of how it may be possible to set the speeds mistakenly because the speeds are set in units of bytes/sec rather than units of "x":
http://club.cdfreaks.com/showthread.php ... post437828
Until Karr corrects this, you can either go back to an older version, or set your speed to the next level up.
cfitz
<edit>
I got a copy of 1.1.13 and was able to test it also and confirm that it too has the bug. I have updated this post accordingly.
</edit>