Which Drive Do I Trust?
| Disc Testing Methods and Software Discuss, Which Drive Do I Trust? at Blank Media forum; Quote: |
- #201
| Quote:
(Actually i know nothing and that's all i know..... or something)
__________________ Writers - LiteOn SHM-165P6SX (MS0P) (USB) - Pioneer DVR-216BK- Pioneer 215D - 3x Pioneer DVR 112 (1.22) - 3x Pioneer 111D (1.29) - Plextor PX-810SA (1.00) - LG GSA-E50N (WE01) Scanner/ripper/reader - LiteOn 1653SX (CS0T) (USB) - LiteOn SHM-165P6SX (MS0P) (USB) - LiteOn SOHC 5235K Shelved LG 5163 (A104) - LiteOn SOHR-5239V (2$0E) - 1x Samsung 203B (SB01) - NEC/Optiarc 7170S (1.82) - Benq 1640 (BSRB) - NEC 3500 & NEC 3520 - Pioneer 106D & 107D - LiteOn 411 & 811 and some.. The King is on vacation after 2 years - LG 4163 (A106) Fatally broken - 1x Samsung 203B (SB01) |
- Today (MyCE Staff)
- Posts: 15,596
| |
- #202
| Quote:
|
- #203
| Quote:
Actually that errors would actually be reported "before" or "after" correction makes no difference whatsoever, what is reported in all cases are the errors before correction (even if they are reported after the correction stage... see my point? - think of PIF...), or all this would make no sense at all: unless they reach their absolute limits (for the drive's ability) leading to a POF, all PIE/PIF errors can be corrected, so there would be nothing in the scans (at least most of the time..) if the errors reported were errors after correction! ![]() And once more to be sure that the point is noticed: PIE/PIF errors reported are a result of the reading process.
__________________ The artist formerly known as Francksoy I won't reply to technical help requests by PM, but ask you question in the forum and notify me, I'll be glad to help if I can! Last edited by Wizzu; 06-05-2006 at 03:30. |
- #204
| Quote:
You can put 1000s of questions to any theory and it's fine but just bc you have qualified doubt it doesn't mean the theory is bad (or good). Experience will let you know. If you don't learn and improve through experience you get pretty much nowhere
__________________ Writers - LiteOn SHM-165P6SX (MS0P) (USB) - Pioneer DVR-216BK- Pioneer 215D - 3x Pioneer DVR 112 (1.22) - 3x Pioneer 111D (1.29) - Plextor PX-810SA (1.00) - LG GSA-E50N (WE01) Scanner/ripper/reader - LiteOn 1653SX (CS0T) (USB) - LiteOn SHM-165P6SX (MS0P) (USB) - LiteOn SOHC 5235K Shelved LG 5163 (A104) - LiteOn SOHR-5239V (2$0E) - 1x Samsung 203B (SB01) - NEC/Optiarc 7170S (1.82) - Benq 1640 (BSRB) - NEC 3500 & NEC 3520 - Pioneer 106D & 107D - LiteOn 411 & 811 and some.. The King is on vacation after 2 years - LG 4163 (A106) Fatally broken - 1x Samsung 203B (SB01) |
- #205
| Discussion continued from this thread over in the LiteOn forum, with the most relevant posts starting here. The discussion is about comparing jitter scans performed on LiteOn drives (using new beta software) with jitter scans performed on BenQ drives. My post is in answer to this post by scoobiedoobie: Quote:
I still think that BenQ drives sometimes reports PIE/PIF values "unfairly" for burns made in some other drives, independently of the jitter level, but I'll return to that when I have made some more scans to confirm what I have seen recently. Quote:
That's why you can have a disc with high jitter that still scans with low PIE/PIF levels at low speed. But if you scan the same high-jitter disc at high speed (12x or faster), you will very often see much higher PIE/PIF levels - especially near the outer edge of the disc. I have seen this behaviour many times on my Plextor drive, and to a lesser degree on my LiteOn, BenQ and NEC drives. So performing a disc quality scan at 12x or 16x is an indirect way of detecting high jitter; if the PIE/PIF levels don't rise near the end, the jitter is not extremely high, but if the PIE/PIF levels do rise near the end, the explanation could be high jitter (or something else).
__________________ Do not meddle in the affairs of dragons, for you are crunchy and taste good with ketchup. |
- #206
| Quote:
|
- #207
| I do have a hypothetical question. if you have a physically good disc (balanced, no physical scratches), I'm going out on a limb and saying then higher errors are probably due to asymmetry, land/pit length and width. However, if data-clock jitter is the standard deviation from the "expected", shouldn't asymmetry affect jitter values? Also shouldn't beta and TA test (not sure what liteon calls it) be related then? I'm hoping that DVDScan's major drive ejecting bugs are fixed soon so I can do some of my own tests. I would like to compare some benq vs plextor vs liteon in beta/jitter scans. it's getting late and my mind is slow. |
- #208
| Has anyone here tried scanning on the Aopen 1648 AAP? this drive reports Jitter aswell (even though it's only a DVD-ROM drive). |
- #209
| Quote:
My main point being that you can use it to detect the absense of high jitter, if you scan the disc at high speed and there is no rise in PIE/PIF levels near the outer edge!
__________________ Do not meddle in the affairs of dragons, for you are crunchy and taste good with ketchup. |
- #210
| My first input in this "gurus" thread (woaw, that was a long and enthralling reading! )... please bear with me.. Quote:
So now DrageMester's input had me starting to test a handful of discs at higher speeds, to see if I also find this correlation with jitter... I will report my findings. |
- #211
| Quote:
I no longer judge burning quality solely on PIE/PIF scans at low/medium speed, but also on how they scan at high speed (12x) and of course Read Transfer tests. Quote:
__________________ Do not meddle in the affairs of dragons, for you are crunchy and taste good with ketchup. |
- #212
| Quote:
|
There's more to MyCE.com
Listen up, we've got more. Product information on 107,830 products. Our experts have written 523 articles. We've gathered 16,131 news items for you to always keep updated.

- think of PIF...), or all this would make no sense at all: unless they reach their absolute limits (for the drive's ability) leading to a POF, all PIE/PIF errors can be corrected, so there would be nothing in the scans (at least most of the time..) if the errors reported were errors after correction! 
)... please bear with me..