IPB

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
DAE quality report on samsung SH-S203N, Apparent perfect C2, how certain is that result?
Jan S.
post Jan 3 2008, 21:29
Post #1





Group: Admin
Posts: 2551
Joined: 26-September 01
From: Denmark
Member No.: 21



I decided to make that DAE quality test cd and ran it on my Samsung SH-S203N.

Firmware Version: SB00
Serial Number: SH-S203NFirmware
HTOA: Yes
Read offset correction: +6
Write offset: -6
Combined offset correcting: +0
Overreading: No!



Errors total Num: 87326
Errors (Loudness) Num: 3555 - Avg : -72.7 dB(A) - Max : -44.1 dB(A)
Error Muting Num: 180 - Avg : 1.0 Samples - Max : 2 Samples
Skips Num: 0 - Avg : 0.0 Samples - Max : 0 Samples



Total Test Result : 82.3 points (of 100.0 maximum)
C2 Accuracy: 100.0 %


The results show a perfect C2 flagging. but are there enough errors to make that a pretty safe conclusion? It shows significantly less errors than the example in the DAE Quality guide. I ran the test on 2 different test cd and different speeds... There are slight differences but the conclusion is pretty much the same.
For comparison my HP drive gave 9000k errors which indicates that this samsung is indeed impressive.

I still need to determine caching (it doesn't cache. I just haven't researched how to determine it safely) but since there seem to be some interest in this drive I decided to post results now. Are there any other test that could be interesting?
Attached thumbnail(s)
Attached Image
Attached Image
 
Go to the top of the page
+Quote Post
Jan S.
post Jan 5 2008, 21:12
Post #2





Group: Admin
Posts: 2551
Joined: 26-September 01
From: Denmark
Member No.: 21



Just to report a funny thing.
While trying to determain overread I found that the samsung cuts ~10k samples if you try to make it read with a -1000 offset.

The upper graph shows the rip with offset 0. The lower one with offset -1000. The data is offsetted correct but it mutes ~10k samples when it actually should get more data at the start of the track.
Now the question was if it does this too when using the correct offset of +6.

It shows that it doesn't cut at the beginning so all well here.


The upper track is ripped with offset 0. The lower one with offset +6. Now it appears it cuts 4k samples in the non-offsetted version!

This drive is seriously funky... Use with caution!!!
Attached thumbnail(s)
Attached Image
Attached Image
Attached Image
 
Go to the top of the page
+Quote Post
greynol
post Jan 5 2008, 21:15
Post #3





Group: Super Moderator
Posts: 10339
Joined: 1-April 04
From: San Francisco
Member No.: 13167



QUOTE (Jan S. @ Jan 5 2008, 12:12) *
The upper track is ripped with offset 0. The lower one with offset +6. Now it appears it cuts 4k samples in the non-offsetted version!

This drive is seriously funky... Use with caution!!!

Actually, this is quite normal...
http://www.hydrogenaudio.org/forums/index....st&p=535072

This post has been edited by greynol: Jan 5 2008, 21:16
Go to the top of the page
+Quote Post
Jan S.
post Jan 5 2008, 21:23
Post #4





Group: Admin
Posts: 2551
Joined: 26-September 01
From: Denmark
Member No.: 21



It cuts the end when offset is not used... So lead-in is not involved at all, right?
Go to the top of the page
+Quote Post
greynol
post Jan 5 2008, 21:31
Post #5





Group: Super Moderator
Posts: 10339
Joined: 1-April 04
From: San Francisco
Member No.: 13167



QUOTE (Jan S. @ Jan 5 2008, 12:23) *
It cuts the end when offset is not used... So lead-in is not involved at all, right?

I'm not totally sure, but I don't think the lead-in is involved.

There have been posts to Digital-Inn saying that samples are lost when the offset correction is set to zero and overreading is enabled with drives that cannot overread. This wasn't addressed in the link I gave (sorry about that), but I think it's an issue that could be fixed in EAC.

This post has been edited by greynol: Jan 5 2008, 22:13


--------------------
Your eyes cannot hear.
Go to the top of the page
+Quote Post
Jan S.
post Jan 5 2008, 21:34
Post #6





Group: Admin
Posts: 2551
Joined: 26-September 01
From: Denmark
Member No.: 21



I checked this. It indeed does not cut when overreading is disabled.
btw.: I could also see that the one with offset +6 was cut at the end when overreading was on. With overreading turned off everything works correctly. The conclusion is that if you keep overreading off the drive is fine...
Go to the top of the page
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 25th December 2014 - 11:52