CDRLabs.com

Has anybody tried setting v1.1.14 to 9x to see if it defaults to a correct 8x?

I had to bump 1.1.14 up to 10x before it would shift gears to a true 8x on my LTR-48246S.

cfitz

I got a copy of 1.1.13, and it also is testing slower than the configured speed (i.e. it tests at 4x when you configure it to test at 8x). Thus, it appears that the bug was introduced in version 1.1.13 (which was a rather short-lived version anyway).

I will edit my previous post to reflect this update.

cfitz

how come it won't allow for 1x reading? I know that Alcohol 120% has been known to slow down to 1x for reading really bad discs, why can't this be done for K-Probe?

The only time I've seen read speeds below 4x on a LiteOn is when it was re-reading errors, so it was (I presume), re-reading at 4x with a output speed if 1-2x. The drives do not slow or re-read in KProbe, they skip ahead.

Version 1.1.16 now available:

Release notes
KProbe :
1.Support save read buffer data
2.Update media manufacturer information
3.Fix bug : Speed error when running PI/PO
4.Fix bug : Disc size error where running C1/C2 on formatted disc

Install version:
http://upload.cdfreaks.com/Kprobe/kpsetup.exe

Update version:
http://upload.cdfreaks.com/Kprobe/kprobe.zip

New version of MInfo released today:

Version 1.5
Release notes:
MInfo:
1.Add DVD+R/+RW manufacturer
2.Update media manufacturer information

Get it here:
http://upload.cdfreaks.com/Kprobe/MInfo.zip

Woohoo! thanks for updates!

Now, who's going to go back and re-time the reading scans to see if it's fixed?

I'm busy writing a new review, so I'm out of the game for a little while. I can do some timing later maybe, but this review is a little time sensitive.

I've got it running now, will edit with full results later, but 8x was about 11 min, so it looks to be fixed.

rdgrimes: Thank you for the notification. Have you been in touch with Karr Wang on other topics too? Any information on what is saved from the "Raw CMD" panel?

The new KProbe seems to be buggy. The length isn't being recognized correctly and the program hangs once the LBA exceeds the written portion. An (imprecise) comparison with V1.1.12 @40x indicates that the read speed is being set correctly, however (ca. same scan time up to data end).

G

1.1.16 is working well here:

KProbe scanning times:
Version 1.1.16, 700MB CDR, LTR-52327S
Starting when "testing" appears in the status bar.
8X - 11min
12x - 6:40 min
24x - 4:50 min
32x - 3:30 min
40x - 2:45 min
48x - 2:15 min
Max - 2:05 min

Based on the times, it appears to be switching to P-CAV at 23x and CAV at 48x, so all is well.

KProbe 1.1.16 scanning a full 700Mb disc on LiteOn 48246s at 24x took: 4:50 (out of which 10 seconds was taken for starting up the scan)

The same disc scanned at 10-24x CAV on Plextor Premium was: 4:39 (out of which 10 secs was for setting up the scan)

The same disc scanned with Kprobe 1.1.14 at 32x setting (best estimate for real 24x scanning) took 4:48 (10 secs for set up).

Disc size was 79:49:43 (MSF).

Looks about ok.

regards,
Halcy

Have you tried scanning an audio disk that wasn't quite full? I ran into the length recognition problem I mentioned above for both audio disks I've tried with 1.1.16.

G

Just tried to scan a 62 min audio CDR, with Kprobe set for "disc size". It continued scanning to 63:30 and then froze.

I've Emailed the author about this.

Check out these two scans done on the same disc. The disc is a E3 Works "Digital Vinyl" CD-R, which I am using in a review that I'm writing. The scans are both done at 40x. The first scan is with K-Probe 1.1.14 and the second is with K-Probe 1.1.16 I did them one after the other with all the same setting, and I double checked Nero Drive Speed and it is set to allow up to maximum (48x) read speeds.

K-Probe Version 1.1.14:


K-Probe Version 1.1.16:


Now the interesting thing, is that all the other CD-Rs of the same media type that I scanned with 1.1.14 produced similar results to the scan above by 1.1.16... so what is different about the disc that causes 1.1.14 to read it differently, how was it fixed???

by the way, I scanned the disc several times with 1.1.14 and it always produces similar results to the above 1.1.14 pic. I'M CONFUSED!

Hehe, you are experiencing what I'm experiencing (although I've yet to see that phenomenon across Kprobe versions).

Makes you wonder about readability test accuracy, doesn't it? :)

I'll put more tests later myself.

regards,
Halcyon

I also saw a couple odd-looking C2's on a disc that was previously free of C2. They were near the same general area, but only with scanning at 40x+.

dolphinius_rex wrote:I'm busy writing a new review ...

congrats on the new site name

OK, "bug" found...
the link Welcome to KProbe still points to the old website, which is now empty...maybe it should point at something at cdfreaks?

regarding the scans I just put up, don't worry, the C2 spike is SUPPOSED to be there! The media is unbalanced (I believe) since it is covered in grooves on the top. Remember, this is the "digital Vinyl" stuff, that looks like the old vinyl records.

dodecahedron: Thanks! I'm very proud of my new domain name!

Anybody still got 1.1.14 stashed somewhere? I accidentally overwrote my copy with 1.1.16.

cheers,
halcy

I'm still experiencing some oddities with 1.1.16, I can't figure them out though. It's as if the speed testing isn't consistant anymore. Sometimes when I test at 40x I get one result which I would expect for 40x, and sometimes I get another result, which I would expect from 32x or maybe 24x... This has only occured for me on 1.1.16 so far, and it's driving me nuts!

has anyone else experienced similar problems?

rdgrimes wrote:Just tried to scan a 62 min audio CDR, with Kprobe set for "disc size". It continued scanning to 63:30 and then froze.

I've Emailed the author about this.

Confirmed! it attempts to keep scanning even after there is no more data to scan, it just gave me unreadable blocks after it ran out of data, it scared the heck out of me until I realised what was happening!

ARGH! I swear, I'm NEVER going to finish this review!