Kprobe Liteon Burn Quality Testing Tool

Ubergeek

Xecuter Groupie
Feb 24, 2003
6,272
0
California, USA
UPDATED XGD3 QUALITY GUIDELINES: http://team-xecuter.com/forums/showthread.php?t=73612

What is Kprobe?


Kprobe is a Liteon Burn Quality testing tool or a DVD Media Quality Testing Software that can be used by Liteon Burners on the PC - in our case we want to specifically test the iHas 124-B series drives (and also others in the iHas range that are compatible. The Burner Max was designed on the iHAS 124-04B so thats the drive we will make all tutorials and guides with. The program produces KProbe Scans that show the PI (Parity Inner) and the PIF / PO (Parity Outer) of the DVD Media, which in turn shows the quality of the dvd media. CI/CO errors that Kprobe reads are for CD Media so not required in your XGD3 burn tests. The latest Kprobe is Kprobe2 and you can download the FREE program here Kprobe2, which has a "Check Update" feature that you can be used to upgrade to the latest version of Kprobe

Why is Kprobe useful to you?

When you buy DVD Media you can quality test the stability of any DVD Media to determine if the media is any good after you burn them. The better the results (lower error rates) you have in Kprobe, means that your discs will last longer and have a smaller chance of decay over time (and will also prove to be a correct XGD3 burn that will be less likely to show any CIV errors and more likely to pass all checks). Once you find the DVD Media that is good, stick with them. As always we use Verbatim DVD+R DL - MKM-001 burns at 2.4x and MKM-003 burns at 4x (with OPC enabled) when using the Burner Max firmware.

If you are not sure what your discs Media Code is you can find out the media code ID of your DVD Media by using a program such as DVD Identifier

Recommended KProbe Settings To Use?:

This is by no means a KProbe manual to follow, just a general recommendation. Use the default ECC PI sum 8 and PO(PIF) sum of 1. The testing scan speed should be at 4X CLV (Constant Linear Velocity).



Welcome to the all new, redesigned KProbe2!

What follows is a brief tutorial on the use of Kprobe2. If you are familiar with KProbe then you will see a number of new features, apart from the re-design. KProbe2 is much more user-friendly, sleek and easy to use. We hope that everyone enjoys using it as much as we have.

KProbe2 is designed to work only with LiteOn DVD/CD burners.


As before, Kprobe full install will look for ASPI and install it if none exists. However, you now have the option of using the SPTI driver instead of ASPI, and this will be discussed more later.

KPRobe2 can co-exist with Kprobe1, you do not need to uninstall one in order to run the other. They will, by default, install to the same directory.

Download KProbe2:
Version 2.5.2


Change log 2.5.2:

1: Added support for BlueRay discs and also Smartburn, HyperTuning and OverSpeed functions.

Change log 2.5.1:

1: Fix DVD-R display bug with discs that have a mediaID longer than 10 Characters.

Chage log 2.5.0:

1. Fix bug: DVD-R DL ADER write error
2. Add AtapiCommander

Changelog version 2.4.6:

1. Fix bug DVD-R/RW disc ID
2. DiscInfo supports Lightscribe and DVD-RAM
3. Upgraded BitSetting function
4. Fix bug: ATIP/ADIP cannot stop when TE/FE occur on the last block.


Just run the .exe and follow the prompts. A reboot after install is strongly suggested. Kprobe will install an icon to your desktop, so just click it and here you go:



The first big change you will notice in KProbe2 is the toolbar. This is fairly self-explanatory, and here you will find many of KProbe2's new features. So let's look at the "tools";



Surprise! A couple of the favorite LiteOn tools have now been included in Kprobe2. These are the bitsetting and region-freeing tools. For discussion and use of the bit-setting (book-type) and region-free tools, please look HERE . You will also find additional relevant material in the LiteOn tools collection

Before we go any farther, let's not forget to look at one of KProbe2's nifty tricks, just click on the disc icon in the upper left corner.



There you see the option to minimize KProbe to the task tray. A very nice feature if you're using the book-type tool and don't need the program taking up space in the taskbar.



Now let's move over to the Info menu.



These options will give you a wealth of information about your media and drive.



As you can see, you have the option to copy disc info to your clipboard. This makes it very simple to post an error scan in the forum, you just paste this into your post and everyone will know what media you have scanned.

The drive info screen looks like this:



Next on the menu is the "Supported Media" info. At present this only works with CDRW drives, so you will get a warning if you try to use it on a DVD writer. What it will show you is the list of supported media from your firmware. We hope that future firmware releases on the DVD writers will allow this feature to work.



Next on the toolbar is the driver selection menu. You can now select whether to run KProbe2 on the ASPI driver or SPTI driver. KProbe2 will remember your setting and run on that driver every time you use the program. If your system is having problems with the ASPI drivers, you now have the option to remove them completely.
Some people report problems with SPTI drivers as well, so use what works the best for you.



Depending on which driver you select, you may notice that your drop-down list of drives will be displayed differently. Here, in Windows2000, the SPTI driver shows the drive letter, and also designates the 0-0 positions of the drives differently. (note: the top drive on my list is the SATA CDRW drive). Here's a comparison of the displays in the 2 drivers, first is ASPI;



Next is SPTI;




On the right side of the toolbar you will see the start-stop-save buttons.



Use these to start or stop any test, or to save the results. Note that ".png" is now the default image format for saved tests. Unless you have a specific reason to do so, this should not be changed,


At the bottom of KProbe2 you now have a status bar that will display the status of your test, the media inserted in the drive, and the driver in use.




Let's move on to the specific tests and their settings

We start with the "Bler" test, which is where you will run PI/PO scans. This is the default screen that opens when you run KProbe2. The settings are very similar to the old KProbe settings, with a few differences;



Realtime Chart: Disabled by default, do not use this unless you have a specific reason for doing so.

Maximum Sampling Rate: This option should be used to increase accuracy when your CPU power is limited. It is intended to minimize the program's demand on the CPU so more sampling is done. For most systems with P4 or better CPU, this should never be required. Of course Athlon based systems of any kind would be considered "better" than P4.


Remove The Singular Point: This will clean up some of the high single spikes that some drives produce when scanning PI/PO. As I understand the fix, it removes any spikes where PI=PO and equals the max error count. It should reduce those spikes but not affect the over-all results.

Test Range: These settings allow you to set whether to scan the entire disc or only a portion of it. Auto-detect is the default, and will scan the entire burned area of the disc. If you wish to know the actual size of the burned area, just click the "Check Size" button.

Speed: This drop-down speed selection replaces the type-in speed command from the old KProbe. Your selected speed will become your default speed every time you run KProbe2, until you change drives or driver.

ECC Sum settings: Note, this has changed! You now set PI and PO ECC counts separately. The default is 8 and 1, which conforms to the DVD standards for 1x scanning. There is no reason to change these settings. However, when comparing scans from KPRobe2 to scans from KProbe1, you must be aware that the PO count is different, and PO levels in KPRobe2 will be different, when compared to ECC-8 counting. Another way to express this difference is that we now are looking for PO counts under 4 max, instead of 32-max. My experience has been that actual differences will vary from disc to disc, and scan to scan. But the DVD standard at 1x scanning is 4 max PO.

Dual Layer Scanning: Kprobe2 is designed to perform scanning of both layers of dual-layer media.

At the bottom right you will see the status display for the test as it is running:



This provides real-time counts of errors, drive speed and test progress. Always remember to check the actual scan speed here during your scan, rather than relying on the selcted speed.



In case you haven't seen the tool tip in the program already, you now make your graph settings by right-clicking on the graph. (only while the test is not running).




The settings are pretty self-explanatory.

Set Title: Allows you to create a custom title for your graph, which will be saved in your image file output as well.
Set line color: Allows you to select the color for the graph you clicked on.
Show Marks Click and you'll see what it does.
Auto Y axis This will auto-graph the chart to fit the error rate of the actual test results. Recommended to leave this checked and not use a fixed-sized graph.
Set error color and value These set how a "read error" is displayed when scanning CDR/RW for C1/C2. Please note that these erors are not the same as C2, and are not "unreadable sectors", but simply indicate that the PUH has skipped over that sector. This occurs either as a result of unreadable data (high C2), or as a result of PUH slipping. A few of these errors are normal on most drives.

You may also have noticed that KProbe is now re-sizable! You can drag the window to any size that pleases you. Note that the size of your graph, when saved to an image file, will change proportionally when you change the window size. To stretch your graph and get a better look at it, just drag the window wider.

Now let's move on to the second tab, ATER/ADER



Works only with LiteOn burners
This set of tests is not new, but has also not been used to date. It's my hope that further discussions of these tests will follow, and we will learn to use this to further identify problems with hardware or media.

To put it simply, this test helps identify problems with laser focus and servo accuracy. It tells us what percentage of bits are written to their correct address.

In terms of results, lower is better. My source tells me that 8% ADER/ATER is considered too high. What this means is that 8% of your bits are not where they are supposed to be. The media is very much a part of this accuracy test, as is the burner.

"Cont.ADER/ATER" is a more generalized running count of these errors. It tells you how many continuous errors have ocurred per block. Again, lower is better.

The setting for these tests are as follows:




Real-time Chart As before, unchecked by default, do not use this unless you have a specific reason to do so.
Write:This will require a blank disc, and will write data to the entire disc then read it back and give you the results. This is the true measure of your burner's performace in the ADER/ATER tests. Un-checking this will alow you to read any disc and see how well it performs in the same test. The value of a read-only test is questionable.

Again, this is a very simplified explanation of a fairly complex test which warrants a great deal more discussion. Feel free to ad your 2 cents.

WE ENCOURAGE YOU TO POST YOUR OWN CHARTS/SCANS OF YOUR BURNED XGD3 BACKUPS - YOU SHOULD ALSO TRY DIFFERENT TYPES OF MEDIA TO SEE IF THERE ARE OTHERS THAT WILL WORK AND NOT JUST THE VERBATIMS


Now we're off to the last pane, the Performance tests:



Here you have a nice collection of [COLOR=green !important][FONT=inherit !important][COLOR=green !important][FONT=inherit !important]performance [/FONT][/FONT][FONT=inherit !important][COLOR=green !important][FONT=inherit !important]tests[/FONT][/COLOR][/FONT][/COLOR][/COLOR] similar to what you have seen in other programs.




You have the oprion to run a transfer rate test on your burned media. This test will be similar to what you see in CDSpeed, and the drive will slow down if there is trouble reading a disc.

You also can choose to burn a data disc to test the burn rate, or simply simulate the burning by checking the appropriate boxes.


If you click the start button at the top of the window, KProbe2 will run all the tests. If you click one of the start arrows in the settings box, you will only run that test. Note that we now have a layer-to-layer seek test for dual-layer media.


That about sums up the new testing program. I hope I have managed to make a good introduction for those who are familiar with the old Kprobe, but also for those who are new to Kprobe.

This thread is for discussions of any aspect of using Kprobe2, bug reports and feature requests are also welcome.


Full credits goto rdgrimes

WE ENCOURAGE YOU TO POST YOUR OWN CHARTS/SCANS OF YOUR BURNED XGD3 BACKUPS - YOU SHOULD ALSO TRY DIFFERENT TYPES OF MEDIA TO SEE IF THERE ARE OTHERS THAT WILL WORK AND NOT JUST THE VERBATIMS
 

Ubergeek

Xecuter Groupie
Feb 24, 2003
6,272
0
California, USA
Max PI should not be higher than 100 and max PIF should not be higher than 4 according to the spec (ECMA-364) - Of course this is a guide and will obviously fluctuate between different types of media

Here are some scans of XGD3 burns by various members of the team

These are Verbatim MKM003. As you can see the burns are perfect and very clean. You won't be seeing any CIV errors from these.





---------- Post added at 20:41 ---------- Previous post was at 20:37 ----------

This is an AONE disc. As you can see it is dogshit quality for XGD3 Burns.

It may say burned successful but this is the quality you get when you to a full read error test. This one would have thrown CIV errors all over the place and would probably eventually flag for a ban or stop working altogether.



FYI

PI = Parity Inner
PIF = Parity Inner Failures

Basically PI errors can be as high as 200, and still have a readable disc, but to achieve a good XGD3 burn you need to be around 100, whereas PIF errors over 8 are not good at all. In actuality, you look at the average, but you still don't want any spikes in PI that run high, or in PIF that are above say 8 or 9. A good PIF is 4 or below.

If you use NERO CDSPEED as a disc quality test, all you have to worry about is the disc quality score which is shown in a box. As long as your disk quality score is over 90 it should be fine.

WE ENCOURAGE YOU TO POST YOUR OWN CHARTS/SCANS OF YOUR BURNED XGD3 BACKUPS - YOU SHOULD ALSO TRY DIFFERENT TYPES OF MEDIA TO SEE IF THERE ARE OTHERS THAT WILL WORK AND NOT JUST THE VERBATIMS
 

bigO73

VIP Member
Sep 23, 2010
392
0
Tampa Bay, Florida
This looks nice! I personally like the TDK brand so it will be interesting to see how they read out with this program. Ordered my drive from xconsole on Monday, but just got email saying it won't be shipped until tomorrow. Will post my results with the TDk when I get it, that's if nobody beats me to it.;)
 

stefanounick

VIP Member
Jun 9, 2010
1,178
118
Orbiting Sun
First, do you know how to read? WE ENCOURAGE YOU TO POST YOUR OWN CHARTS/SCANS OF YOUR BURNED XGD3 BACKUPS and NOT some chit chat talking
 

jayfig

VIP Member
Oct 29, 2010
314
0
North Carolina
Well excuse me drill sergeant I was just asking if anybody can decipher the graph data and tell me if it was good, bad, descent, etc... That is what forums are for correct? My online college forum wasn't that strict.
 

montana909sb

Full Member
Nov 26, 2010
60
0
Well excuse me drill sergeant I was just asking if anybody can decipher the graph data and tell me if it was good, bad, descent, etc... That is what forums are for correct? My online college forum wasn't that strict.
ya same here my graph looks way different then those first ones
 

Ubergeek

Xecuter Groupie
Feb 24, 2003
6,272
0
California, USA
Link To Image

Now somebody tell me how to read this. :rolleyes2:
*sigh* :facepalm: Reading is AWESOME !

Max PI should not be higher than 100 and max PIF should not be higher than 4

Well excuse me drill sergeant I was just asking if anybody can decipher the graph data and tell me if it was good, bad, descent, etc... That is what forums are for correct? My online college forum wasn't that strict.
So its ok for you to come here - completely ignore the rules on posting (i.e. READ BEFORE POSTING) and then act like a bitch when you get called out on the fact ?

Maybe if your college forum was a little stricter you wouldn't be posting questions that had already been clearly answered and you would've ended up with better grades ? :rolleyes2:

ya same here my graph looks way different then those first ones
same goes to you - actually READ before wasting your time posting. We are here to educate you not to spoon feed you so that you learn absolutely nothing in the process.

Come on guys - I just gave you ALL the info you need. Do me the respect of actually reading it first before posting anything. Back on topic.......
 
  • Like
Reactions: J3rk My Turk3y

cRaZyLeGz

Full Member
Aug 10, 2010
72
6
S. Wales
If you aint bald m8 your gonna be by the end of the week pulling your hair out.

Guys if it was clear as mud before it aint now, it aint easy starting off I understand that but information is the key, take it in just use your brains if you cant do that then read again and again till you do.

Sorry off topic I know.
 

GhostFace606

VIP Member
Jan 31, 2011
803
0
TanonymousX
here is mine :eek2: rather its the media or the drive good or bad I don't know?this was a turncated back up of gow3.
 
Last edited:

Fisticuffs

VIP Member
Mar 14, 2011
1,326
68
Arizona, US
To put it simply, this test helps identify problems with laser focus and servo accuracy. It tells us what percentage of bits are written to their correct address.

In terms of results, lower is better. My source tells me that 8% ADER/ATER is considered too high. What this means is that 8% of your bits are not where they are supposed to be. The media is very much a part of this accuracy test, as is the burner.

"Cont.ADER/ATER" is a more generalized running count of these errors. It tells you how many continuous errors have ocurred per block. Again, lower is better.
Everything is in the OP, Look at uber's graphs and compare :rolleyes2:

I'll post mine when my burner arrives

Where's bandit123 with his spoon when you need him
 
Last edited:

Ubergeek

Xecuter Groupie
Feb 24, 2003
6,272
0
California, USA
here is mine :eek2: rather its good bad I don't know?this was a turncated back up of gow3.
I just spent 3 posts telling people to read before posting after asking the same sh*t ;)

Max PI should not be higher than 100 and max PIF should not be higher than 4
You posted your results so come to your own conclusion. Everything in the OP tells you how to read these graphs.