Page 1 of 2

PI/PIF testing question

PostPosted: Mon Sep 05, 2005 12:07 pm
by grouch
I have 2 burners, BenQ DW1640 BSLB and NEC 3520 L&D 2.U2
Should I use the burner that I burnt the disc to do the scans or is it better to scan using the other drive, sort of like independent testing.
I only ask because the benq reports high spikes that the nec doesn't, and also vice versa.
so if i look at the two scans it doesn't make much sense

Re: PI/PIF testing question

PostPosted: Mon Sep 05, 2005 4:24 pm
by dolphinius_rex
grouch wrote:I have 2 burners, BenQ DW1640 BSLB and NEC 3520 L&D 2.U2
Should I use the burner that I burnt the disc to do the scans or is it better to scan using the other drive, sort of like independent testing.
I only ask because the benq reports high spikes that the nec doesn't, and also vice versa.
so if i look at the two scans it doesn't make much sense


Try doing transfer rate tests on the discs. Dips in the read speed will tell you how much attention you should pay to odd looking spikes :wink:

PostPosted: Mon Sep 05, 2005 7:12 pm
by Scour
Hello!

Maybe someone can help me:

Is PIF same like PO/POE?

PostPosted: Tue Sep 06, 2005 1:33 am
by dolphinius_rex
Scour wrote:Hello!

Maybe someone can help me:

Is PIF same like PO/POE?


POE is not the same as PIE or PIF. I don't think many people really know WHAT to make of POE actually. As for POF, there should never be ANY of them on a disc.

PostPosted: Tue Sep 06, 2005 5:10 am
by Scour
dolphinius_rex wrote:
POE is not the same as PIE or PIF. I don't think many people really know WHAT to make of POE actually. As for POF, there should never be ANY of them on a disc.


I don´t know that the "E" means.

PIF = Parity Inner Failure; is the next instance the PO- Parity Outer?

POF = Parity Outer Failure, it means that the correction can´t correct Errors (Hope I´m right)

PostPosted: Tue Sep 06, 2005 10:32 am
by dolphinius_rex
Scour wrote:
dolphinius_rex wrote:
POE is not the same as PIE or PIF. I don't think many people really know WHAT to make of POE actually. As for POF, there should never be ANY of them on a disc.


I don´t know that the "E" means.

PIF = Parity Inner Failure; is the next instance the PO- Parity Outer?

POF = Parity Outer Failure, it means that the correction can´t correct Errors (Hope I´m right)


PIE = Parity Inner Error
PIF = Parity Inner Failure
POE = Parity Outer Error
POF = Parity Outer Failure

PostPosted: Tue Sep 06, 2005 1:11 pm
by Scour
dolphinius_rex wrote:
PIE = Parity Inner Error
PIF = Parity Inner Failure
POE = Parity Outer Error
POF = Parity Outer Failure


When a error appear, it goes to the next instance of the error-correction?

PostPosted: Tue Sep 06, 2005 1:28 pm
by dolphinius_rex
Scour wrote:
dolphinius_rex wrote:
PIE = Parity Inner Error
PIF = Parity Inner Failure
POE = Parity Outer Error
POF = Parity Outer Failure


When a error appear, it goes to the next instance of the error-correction?


I'm not sure how POE works into it, but basically yes.

PostPosted: Sat Sep 10, 2005 3:08 am
by Muchin
Scour wrote:Hello!

Maybe someone can help me:

Is PIF same like PO/POE?

Most drives report PIF in number of rows. It is easier to see the relationship between PIF and POE if both use byte as the unit. Within a PIF row, those erroneous bytes not corrected in the first stage become POE bytes, up to 〜180 in number, to be corrected in the second stage.

PostPosted: Mon Sep 12, 2005 7:39 am
by Halc
PIE = erroneus byte in an ECC block inner parity row (implicitly considered correctable). Aka "PI error"

PIF = uncorrectable inner parity row in an ECC block (can contain multiple uncorrectable PIE or just a single one. Will lead to 1 or more POE). Aka "pi failure"

POE = erroneus byte in an ECC block outer parity column (implicitly considered correctable). Aka "po error"

POF = uncorrectable outer parity column in an ECC block (can contain multiple uncorrectable POE or just a single one) aka "po failure"

ECC block = a matrix of dvd payload data along with error correction data aligned into a 208 rows and 172 columns.

For more info:

http://www.cdrinfo.com/forum/tm.asp?m=7 ... PIF&#79249

and of course the ECMA specs in question.

best regards,
Halc

PostPosted: Mon Sep 12, 2005 11:11 am
by grouch
ok, i've taken a Fujifilm DVD+R, made in Japan, media code YUDEN000 T02 and burned it with my NEC 3520, firmware 2.U2 @ 16x.

I've done transfer test and quality scans @ 8x using the NEC 3520 and BenQ 1640 BSLB.

As you can see, the quality scans vary and I don't know which one to rely on.

PostPosted: Mon Sep 12, 2005 11:12 am
by grouch
Continued...

PostPosted: Mon Sep 12, 2005 12:43 pm
by dolphinius_rex
Grouch,

I would say that all the scans point to the disc having a problem.... The NEC says the end of the disc is suspect, and the BenQ says the middle of the disc has a problem.

Why not just re-burn the disc?

PostPosted: Mon Sep 12, 2005 1:37 pm
by Scour
Grouch,

Scan with the NEC @5x

PostPosted: Mon Sep 12, 2005 3:47 pm
by RJW
dolphinius_rex wrote:Grouch,

I would say that all the scans point to the disc having a problem.... The NEC says the end of the disc is suspect, and the BenQ says the middle of the disc has a problem.

Why not just re-burn the disc?


Not so sure about the NEC that dips could very well be possible because of stuff running in the background So if there's a change that you had stuff running in the background then I suggest a retest with the NEC befor completely saying it's complete garbage.
Also strange the NEC is the less good reader of these 2 based on the information I have however it doesn't seem to have the problem in the middle were the benq had problems. I wonder what problem there is at that specific spot.

PostPosted: Mon Sep 12, 2005 4:29 pm
by rahzel
also could be because of heat.
when it was hot outside, every burnt DVDR had single PIF spikes like that with my NEC 3520A.

PostPosted: Mon Sep 12, 2005 4:29 pm
by dolphinius_rex
RJW wrote:Also strange the NEC is the less good reader of these 2 based on the information I have however it doesn't seem to have the problem in the middle were the benq had problems. I wonder what problem there is at that specific spot.


Yeah, I'm curious as to that myself!

PostPosted: Mon Sep 12, 2005 4:57 pm
by grouch
Alright, new test.
Minimal background programs, no taskbar programs, internet usage 0, AFK when test in progress.
Asus probe temps, 35 CPU and 33 motherboard.
Room temp 25 celsius

PostPosted: Mon Sep 12, 2005 4:58 pm
by grouch
Continued...does this mean my BenQ is defective??

PostPosted: Mon Sep 12, 2005 5:09 pm
by rahzel
do you have an nforce motherboard? if so, do you have the nforce IDE sw drivers installed? if so, uninstall them.

PostPosted: Mon Sep 12, 2005 7:07 pm
by grouch
I have an Asus P4P800-E Dlx which uses the Intel 865 northbridge, with the ICH5R southbridge, with onboard Promise controller. No nForce for me. And I use the default windows drivers.

PostPosted: Tue Sep 13, 2005 3:25 am
by rahzel
i guess i should have read your sig #-o .

PostPosted: Tue Sep 13, 2005 10:41 am
by dolphinius_rex
grouch wrote:I have an Asus P4P800-E Dlx which uses the Intel 865 northbridge, with the ICH5R southbridge, with onboard Promise controller. No nForce for me. And I use the default windows drivers.


Do you have a friend's computer you can try it on?

I've yet to figure out what caused it, but my BenQ DW1640 had major issues when installed on one of my PC's, but not on the other. Both machines ran DFI motherboards with NVidia chipsets too :o

PostPosted: Wed Sep 14, 2005 1:19 am
by grouch
nah...i've spent enough time with these that's my stock is running low that i'm leaving these for less important back ups...back to the MIT sony08d1's from wal-mart...

aside from bitsetting and MIJ, the fujifilm's perform worse than the sony's...relatively same price, and sony's burn adequately well in both my burners at 16x

thanks to all for the suggestions and comments

PostPosted: Wed Sep 14, 2005 2:10 pm
by Muchin
Halc wrote:PIE = erroneus byte in an ECC block inner parity row (implicitly considered correctable). Aka "PI error"

PIF = uncorrectable inner parity row in an ECC block (can contain multiple uncorrectable PIE or just a single one. Will lead to 1 or more POE). Aka "pi failure"

POE = erroneus byte in an ECC block outer parity column (implicitly considered correctable). Aka "po error"

POF = uncorrectable outer parity column in an ECC block (can contain multiple uncorrectable POE or just a single one) aka "po failure"

Most probably you were too busy to check what you wrote above. Undoubtedly you are aware that only very few drives use byte instead of row as the unit of measurement for PIE. Another point is that PIE numbers given by some drives include PIF. I am not sure whether POE does not include POF by all drives.