Have you been perplexed by the jitter scans given by the Plextor drives and hoped the results to be reported in some reasonable unit? It has not been possible to make sense of the numbers returned by the drives as displayed in PxScan, perhaps that is why PlexTools does not even show any numbers for jitter. It has just occurred to me that there may be a solution. I came by it through reverse thinking prompted by a hint. In view that many earlier versions of PlexTools err in calculating PIE averages, it is not unthinkable that Plextor has also made some other mistakes. Have interest to see if you can find the kind of miscalculation that would give those weird numbers? It is surprisingly simple.
Hopefully we come to the same answer: By definition, jitter (%) = Ïƒ Ã· T Ã— 100. Now if computed as T Ã· Ïƒ Ã— 100, you will get 1250 (in %) when Ïƒ is 0.08 T, for example. Thus, Plextor drives appear to inadvertently report jitter as its inverse in %. To get jitter values correctly is then simple arithmetic. Please note that data-to-clock (D.C.) jitter is adopted by DVD specifications, whereas TA test measures data-to-data (D.D.) jitter, which is also employed in CD specs. D.D. jitter (the avg. given by PxScan in TA test) is generally somewhat higher (commonly 1.2 - 1.5 times) than (D.C.) jitter for DVD, though the differences vary from case to case.
Although I am confident that the mystery has been cleared up, helps from persons capable of deciphering the codes of Plextorâ€™s firmware are needed for final proof.