http://club.cdfreaks.com/showthread...5&page=10&pp=25
Quote:
Originally Posted by KillMe
Wow. Thanx ErikDeppe! That really sounds cool!
Thanx for the screenshot as well.
What was the point behind the low scanningspeed until now: Firmwarelimitation? Lack of speedup-command? Qualityproblems while highspeedscanning? Or is it a hack (meaning that you do not scan all sectors but only a few)?
Didn't You state earlier in this thread that Benq told you PO-Scanning is not implemented in firmware? Now it looks a little bit like it was implemented.
Don't get me wrong, I don't want to blame anyone. It's a great burner. And yours is a great program and it was the first to support pipo-scanning with the Benq at all.
I'm just curious....??
BTW: The scan shown in the screenshot looks not so perfect. High Jitter and PI of 60 at some places. Are You sure drive and disc are ok? Burned 8x right?!
There are several reasons why the current method is slow:
- scan is done at 4x CAV, although this seems to be fixed in the latest firmware version. But it doesn't make much difference.
- PI errors and Jitter cannot be measured in a single pass so everything has to be scanned twice
- the performance when testing with small scanning intervals is low
But these issues are all fixed with the new method.
The results from the screenshot I posted are pretty good. The jitter display is something I'll have to look at because it's much higher than with the old method.
With the old method PI failures were not reported but with the new method all kinds of errors can be reported (including PO errors and PO failures).
__________________
報價︰
最初透過KillMe公佈
哇。 Thanx ErikDeppe﹗ 那真的聽起來涼爽﹗
screenshot的Thanx也。
直到現下的在低的scanningspeed后面是要點的︰ Firmwarelimitation嗎？ 缺乏加快命令嗎？ Qualityproblems當時highspeedscanning？ 還是(意味著你不掃描全部部門而是只一些)是一輛出租？
你沒在這根線裡更早說明Benq告訴你郵電亭掃描沒被在固件裡實現嗎？ 現下它看起來一點象它被實現。
不要誤解我，我不想要責備任何人。 它是一個大的燃燒器。 並且你的是一個大的程式，它最先確實用Benq 支持pipo 掃描。
我只不過好奇 ....? ?
BTW︰ 在screenshot裡顯示的掃描看起來不如此完美。 在一些地方60的高的緊張和PI。 你是肯定的運動，光碟是ok嗎？ 正確地燒毀8x嗎？ !
有這種當今的方法是慢的的幾個原因︰
-雖然這好像被在最新的固件版本裡修理，但是掃描被在4x CAV 做。 但是它沒有很大影響。
-錯誤PI 和感到緊張在單遍內不能被測量因此一切事情必須被兩次掃描
-當隨著小的掃描間隔測試時，性能是低的
但是這些問題用這種新方法全部固定。
來自我公佈的screenshot的結果是很不錯的。 緊張展示是我必須看的東西因為比由於這種舊的方法高得多。
由於老的方法PI錯誤， 沒被報告但是用這種新方法各種錯誤可能被報告(包括郵電亭錯誤和郵電亭失敗)。
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Quote:
Originally Posted by Halcyon
I read from the support page that CD-DVD Speed supports Toshiba SD-M1902.
Is this the same as support for Toshiba SD-M1912?
http://tinyurl.com/5v76b
I can't find Toshiba SD-M1902 from Toshiba's site.
Just want to be sure, before I order SD-M1912
Sorry, that was a typo. It's the SD-M1912. The SD-M1902 doesn't exist
It's supported because it uses the Mediatek chipset.
__________________
--------------------------------------------------------------------------------
報價︰
最初透過平靜公佈
我從支持頁讀CD -DVD速度支持東芝南達科他M1902。
這與對東芝南達科他M1912的支持相同嗎？
http://tinyurl.com/5v76b
我不能從東芝的場所發現東芝為南達科他M1902。
只想確信，在我預訂南達科他M1912之前
抱歉， 那是一名印刷工人。 它是南達科他M1912。 南達科他M1902不存在
它被支持，因為它使用Mediatek晶片組。
Quote:
Originally Posted by Jamos
@Erik can you add to your sig. a link to your cdspeed site?
Done
__________________
報價︰
最初透過Jamos公佈
@艾利克罐裝你增加你的sig。 與你的cdspeed 場所的聯繫嗎？
做
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Quote:
Originally Posted by muchin
Out of curiosity, most recently I used Plextor Premium to scan C1/C2 errors with CD Speed 3.30 as well as PlexTools and got some surprising results. Although CD Speed supports C2 scanning (but not C1), the numbers obtained for three discs are 5-20 times those of CU (E32) errors using PlexTools. Furthermore, the total CU errors returned after performing digital audio extraction with error reporting by PlexTools are identical, or nearly so, to the C2 totals given by CD Speed. Presumably the results are due to different ways in handling the same raw data, and the C2 in CD Speed for Plextor drive represents E32 , thus corresponds to CU in C1/C2 test of PlexTools , though in different unit of measurement. In its C1/C2 test PlexTools transforms the raw data so as to be compatible with BLER, i. e. in unit of frame/second. CD Speed plots the error rates returned by the chipset as they are, so the unit is byte/second. Am I right? It would be nice to count C1 error rates also in two different ways by the same drive, provided that ErikDeppe will enable support for C1 scanning by Plextor Premium in the near future.
If a drive is not listed here then Nero CD-DVD Speed uses a standard command to get C2 error information. This command returns the errors in bytes/second.
For Plextor drives (not listed) the C2 errors reported by Nero CD-DVD Speed are indeed the same as the CU errors from PlexTools. Both are reported in bytes/second.
Nero CD-DVD Speed shows the errors as they are returned by the drive.
C1/C2 errors are usually returned in frames/second.
__________________
報價︰
最初透過muchin公佈
出于好奇， 最近我使用Plextor 保險費掃描C1/C有CD 速度3.30和PlexTools的2個錯誤，得到一些驚人的結果。 雖然CD 速度支持C2 掃描(但不是C1)， 為3 個光碟獲得的數目是使用PlexTools的5-20 倍CU(E32)錯誤的。 而且， 在執行用透過PlexTools 報告的錯誤的數字化的音頻的血統相同之后，總CU 錯誤回來， 或者差不多如此，對以CD 速度給的C2 總數。 大概結果在處理相同的原始數據過程中由於不同的模式， 並且Plextor 運動的在CD 速度方面的C2 描述E32， 如此符合CU 在PlexTools的C1/C 2 試驗，雖然在不同的測量單位裡。 在它的C1/C裡2 試驗PlexTools 改變原始數據以便與BLER，用框架/秒的單位的i. e.相容。 CD 速度密謀晶片組返回的出錯率，象他們是那樣，單位是位元組/秒。 我正確嗎？ 透過相同的運動用兩種不同的模式也算C1為出錯率將是很高興的， 假若ErikDeppe 不久將使Plextor 保險費的對C1 掃描的支持成為可能。
如果運動在這裡沒被列舉，那么尼羅CD -DVD速度使用標準命令得到C2 錯誤訊息。 這命令在位元組/秒返回錯誤。
對于Plextor來說開車，(不列舉)C2 錯誤被尼羅報告CD -DVD速度從PlexTools 的確與CU 錯誤相同。 兩個被在位元組/秒報告。
當他們因為運動被返回時，尼羅CD -DVD速度顯示錯誤。
C1/C 2 錯誤通常被在框架/秒返回。
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
http://club.cdfreaks.com/showthread...5&page=11&pp=25
Quote:
Originally Posted by Halcyon
Another thing to notice is that the Toshiba SD-M1802 does not report PIF at all for dvd scans (that is, it cannot report them, even if they exist).
For CD scans it does report C2, but I'm not sure the results are useful (maximum 220 c2 on a disc that is readable).
Also, it reports jitter for and speed for cd scans that are totally whacked (see attachment): speed jumps from 1x to 99x and jitter is reportedly at 0,3%.
I don't think this drive can report PIFs but I will check these issues asap.
報價︰
最初透過平靜公佈
注意到的另一事情是東芝南達科他M1802不確實報告PIF dvd掃描(即，它不能報告他們， 即使他們存在)。
CD 掃描它報告C2，我不能確信結果有用(最大220 c2在可讀的一光碟上)。
此外，它報告感到緊張和速度給cd掃描全部用力打(看見附件)︰ 速度從1x猛增到99x，在0，3% 據報道，緊張是。
我認為這運動不能報告PIFs，但是我將檢查這些問題asap。
Quote:
Originally Posted by Halcyon
Erik,
can you quickly summarize which chipsets are currently supported?
- Mediatek (LiteOn, Toshiba, etc)
- ALI (AOpen
- Philips (Philips, BenQ, NuTech)
Are there others?
- VIA (Toshiba SD-M1802)
- Ricoh (AOpen, Ricoh)
__________________
報價︰
最初透過平靜公佈
艾利克，
哪個晶片組目前被支持，你能迅速作總結嗎？
-Mediatek(LiteOn，東芝，等等)
-阿裡(AOpen
-菲利浦•(菲利浦，BenQ，NuTech)
有其它人嗎？
-透過(東芝南達科他M1802)
-理光(AOpen，理光)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Quote:
Originally Posted by muchin
Would you comment on some related questions? Does the error test under advanced DAE quality test also use MMC command? Is it possible to choose different speeds for this test? When I got very different profiles by this test and the disc quality test for the test CD disc created by Nero CD-DVD Speed using the same drive, what does it mean?
This wonderful unique program allows many drives to perform many tests. Bravo
The Advanced DAE Error test indeed uses the standard MMC command.
The speed is not changed for this test so you can use Nero DriveSpeed to set the speed first.
Normally the results from the Advanced DAE Error test should compare well with the Disc Quality test. Do you have some screenshots which can show the difference?
__________________
報價︰
最初透過muchin公佈
請你對一些有關的問題作評論，好嗎？ 錯誤在先進DAE質量檢驗下測試此外使用MMC 命令？ 這次試驗選擇不同的速度是可能的嗎？ 我透過這次試驗得到非常不同的外形和試驗CD 光碟的光碟質量檢驗使用相同的運動尼羅建立CD -DVD速度， 它是什麼意思？
這個令人驚嘆的獨特的計畫允許很多運動進行很多試驗。 太棒了
錯誤測試的先進DAE 的確使用標準MMC命令。
速度不被換成這次考試因此你能使用尼羅DriveSpeed首先確定速度。
通常來自先進的DAE 錯誤試驗的結果應該由於光碟質量檢驗比較得好。 你有能顯示差別的一些screenshots嗎？
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _