Au vue du post sur cdrinfo, je pense que je vais garder mon plextor 712A
avec plextool XXL 3 pour mes tests de taux de transfert ainsi que les tests de PI/PO
Au vue du post sur cdrinfo, je pense que je vais garder mon plextor 712A
avec plextool XXL 3 pour mes tests de taux de transfert ainsi que les tests de PI/PO
NEC and Pioneer drives: These drives are discouraged from being used as testing units.
I can't think of any software that should be avoided.
For LiteON's, K-Probe, DVDInfoPro, and Nero CD/DVD Speed are good
For BenQ's DVDInfoPro, and Nero CD/DVD Speed are good
For Plextor's PXScan is good, and DVDInfoPro also works, but it doesn't report Beta scores yet.
LiteON's: 4x CLV is recommended, 8x CAV would be "ok" but discouraged
4x is pretty much the standard most of the time, so I recommend 4x to keep it more uniform. 8x is pretty much the other option.
BenQ's: 8x CAV is recommended, 4x CAV is "ok", CLV and P-CAV testing is discouraged.
8x CAV is pretty much the most common speed used, and could be argued as the BenQ standard.
Again, I'd like to keep it as uniform as possible. I tend to be against the use of P-CAV and CLV because BenQ drives were designed to be CAV testing units.
Only CD/DVD Speed offers these odd testing options, and I don't think we want to see everything get confused by having to see which of 6 or 7 different speeds/testing methods has been used. Also, I've seen some odd results on CDFreaks that concern me.
Plextor: 2x is encouraged, 5x is "ok", 8x and 12x is discouraged
2x and 5x tend to give fairly similar results, but once you move to 8x and 12x the results tend to get a little wild. Also, most people who bother to use Plextors for scanning, usually use 2x or 5x anyways.
Summary
After having compared three test disc results measured with CATS and with PX-712A, we are happy that finally end users can do accurate measurements, and close to what proffesionals are using.
From the first place we didn't expect any miracles, remember PX-712A costs only few hundred Euros when CATS costs thousands.
For sure, we would like to have other reading speeds options than the default 2X CLV, since if you decide to do PISum8/Sum1 and Beta/Jitter scans, for one disc you must spend around 1:15hours.
If only PlexTools could report PISum8/Sum1 and Beta/Jitter with one pass would be great
« Résumé :
Après avoir comparé les résultats obtenus avec 3 DVD de test mesurés avec la machine AudioDev CATS puis le graveur Plextor PX-712, nous sommes heureux de constater que les utilisateurs finaux ont enfin la possibilité d’effectuer des mesures précises et proches de celles données par les machines utilisées par les professionnels.
Au début nous n’attendions aucun miracle considérant qu’un PX-712 coûte une centaine d’€ et la machine CATS SA300 quelques milliers.
Bien sûr nous voudrions pouvoir disposer d’autres options que la vitesse de lecture par défaut de 2x en mode CLV (vitesse linéaire constante) vu que si vous décidez d’effectuer un scan PISum8/Sum1 et un test Beta/Jitter pour un DVD cela vous prendra environ 1 heure et quart.
Si Plextools pouvait reporter le PISum8/Sum1 et le Beta/Jitter en une seule passe ce serait déjà bien »
DrageMester a écrit:CDRinfo also compared the Pioneer DVR-111DBK with an Audiodev SA-300 CATS scanner in this review, and that 111D drive didn't fare nearly as well - only one disc out of four had similar scans to the CATS.
This suggests that there is significant variance between the scanning "accuracy" of Pioneer 111 drives.
The same is also true for many other consumer grade drives; e.g. NEC drives are known to vary a lot in how they scan.
DrageMester a écrit:CDRinfo a aussi comparé le Pioneer DVR-111DBK avec une Audiodev SA-300 CATS dans cette review, et ce graveur 111D ne s'est pas comporté auusi bien - seul 1 DVD parmi les 4 avait des scans similaires à la CATS
Ceci suggère qu'il existe une variabilité significative entre des graveurs Pioneer 111 concernant leur "scanning accuracy"
JC: Data to Clock Jitter
Jitter measurements are used to indicate the occurrence of deviations from an ideal duration. The data on an optical disc is carried by the length of the pits and the distance between them. This data is extracted with a clock signal that is synchronized with the pit edges. Jitter measurements are done by monitoring the length of the pits and the distance between them (Data to Data Jitter), and by monitoring the length between the edges of the pits and the edge of the clock (Data to Clock Jitter).
Its value is given by the standard deviation of the length of the recorded marks.
It mustn't exceed
8% for DVD-R
and 9% for DVD+R
of the 1T reference clock signal (38.2 ns)
Francksoy a écrit:Personally I think along the same lines as SantaKlaus: discs/burns showing good scans at higher speeds are most certainly better discs/burns.
So I'd say that if you need to lower the speed to have a good scan, you're doing things backwards so to speak, i.e. changing the testing method to get the result you want.
What you should want is good results without changing the testing method.
So my opinion is: change the burning speed, the firmware, the discs, whatever, but don't scan at slower speeds just to see a good scan! :disagree:
G@M3FR3@K a écrit:As said before in this forum, the error measurement tests are to be taken with a grain of salt
since it will only show you how that particular drive can read that particular disc.
It's a good indication though as PI/PO scanning can reveal problem areas on the disc but comparing two different drives (using two different scanning software tools) can show a very different result.
Neither will be more accurate, it all depends on the drive you're using to read the disc with.
alexnoe a écrit: Sounds like one is doing avg per ECC block, and the other is doing avg per 16 ECC blocks
Retourner vers Expertise de médias
Utilisateurs parcourant ce forum : Aucun utilisateur enregistré et 0 invités