Help - Search - Members - Calendar
Full Version: Someone please analyse my FEURIO Cache Test result
Hydrogenaudio Forums > Lossless Audio Compression > Lossless / Other Codecs
Badass01
CODE
Informations from INQUIRY command:
Manufacturer: HL-DT-ST,   Product:  DVDRAM GSA-4167B,  Version: DL12
Synchronous data transfer: Not supported
Explanation:
The INQUIRY command will give fundamental information on a device.
First it determines the names of the manufacturer and the product and the product version number (in most cases the version of the
firmware).
It also determines some infomation on the abilities of the device; the most interesting being whether the device
supports"synchronous data transfer". This transfer mode allows a faster transfer of the data through the SCSI-bus. This is also
necessary when using "slow" CD-Roms, because the bus will be burdened less.


Reading device capabilities:  OK
Maximum speed: 7056 kByte / second (40.0 times)
Cache size: 2048 kByte
Read CD-RW:   Yes
Read Bar code:  No
Read UPC code:  Yes
Read ISRC code:  Yes
Return C2 error pointers:  Yes
Read R-W subcodes:  No
R-W subcode de-interleaved:  No
Read CD-DA:  Yes
Read CD-DA correctly:  Yes

Explanation:
All "modern" CD-Roms support a additional command, which can be used by the computer, to determine the capabilities of the CD-Rom.
The device supports the command. Feurio! has decoded the most interesting details and output them.
It should be pointed out that these are statements by  the manufacturer! If a CD-Rom reports that it supports some functions, this
doesn't mean that these functions are implemented correctly.

Maximum speed:
   This is the maximum speed, with which the CD-Rom can read audio data.
   (This has nothing to do with the transfer rate on the SCSI- or IDE-bus.)

Cache size:
   The size of the cache memory of the device.
   (Feurio! determines the real cache size that can be used by audio data later; in fact there are devices that cannot cache audio
   data!)

Read CD-RW:
   Here it tells you whether your device can read rewritable media.

Read Bar-code:
   Reports whether your device can read the bar-code which is printed on most CDs/CDRs.

Read UPC-code:
   Report whether the device can read the UPC-code (Universal Product Code) of the CD.

Read ISRC-code:
   Reports whether the device can read the ISRC-code (International Standard Recording Code) of the tracks.

Return C2 error pointers:
   A CD has several methods for error detection and correction.
   In general, a CD-Rom corrects errors automatically (if possible).
   There is also a mode, in which the CD-Rom returns, if (and where) there were correctable errors. So it is possible for example
   to determine, how "good" a CD still is. Unfortunately this mode works only with data CDs!

Read R-W-subcodes:
   Besides the normal audio data, on an audio CD there is some additional data in so-called "Subchannels" on the CD. The
   individual channels are named with letters.
   The P- and Q-channels contain e.g. the time-code and the index data.
   The channels R and W are still not normed, they can be used e.g. for writing the artist and the title of the track to the CD.
   This parameter reports, if your device can read the R- and W-channels.

R-W-subcode de-interleaved:
   Reports, if the device can read the R-W-channels just in raw format ("No") or in a processed format ("Yes").
Read CD-DA:
   "Yes" -> The device claims that it can read audio data.

Read CD-DA correctly:
   "Yes" -> The device claims that it can read audio data correctly (i.e. without jitter errors).

====================================================================================================
=

+++++++++++++++++++++++++
++ Cache test
+++++++++++++++++++++++++

Feurio! will now try to determine the size of the cache memory usable for audio data and the max. transfer rate.
To do so, Feurio! will read a certain number of sectors repeatedly and measure the transfer rate.

First 1 sector will be read repeatedly, then 2 sectors, and so on.
Normally the transfer rate will increase, because the more sectors are read, the fewer search operations will be needed.

Number of sectors: 1 (=2 kByte) -> 1.010 MBytes / second
Number of sectors: 2 (=4 kByte) -> 2.439 MBytes / second
Number of sectors: 3 (=7 kByte) -> 3.520 MBytes / second
Number of sectors: 4 (=9 kByte) -> 4.424 MBytes / second
Number of sectors: 5 (=11 kByte) -> 5.797 MBytes / second
Number of sectors: 6 (=14 kByte) -> 6.540 MBytes / second
Number of sectors: 7 (=16 kByte) -> 7.244 MBytes / second
Number of sectors: 8 (=18 kByte) -> 8.006 MBytes / second
Number of sectors: 9 (=21 kByte) -> 8.615 MBytes / second
Number of sectors: 10 (=23 kByte) -> 9.155 MBytes / second
Number of sectors: 15 (=35 kByte) -> 10.187 MBytes / second
Number of sectors: 22 (=51 kByte) -> 0.624 MBytes / second
Number of sectors: 15 (=35 kByte) -> 7.964 MBytes / second
Number of sectors: 16 (=37 kByte) -> 10.565 MBytes / second
Number of sectors: 17 (=39 kByte) -> 0.495 MBytes / second
Number of sectors: 18 (=42 kByte) -> 0.516 MBytes / second
Number of sectors: 19 (=44 kByte) -> 0.545 MBytes / second
Number of sectors: 20 (=47 kByte) -> 0.581 MBytes / second
Number of sectors: 21 (=49 kByte) -> 0.612 MBytes / second
Number of sectors: 31 (=72 kByte) -> 0.897 MBytes / second
Number of sectors: 46 (=108 kByte) -> 1.042 MBytes / second
Number of sectors: 69 (=162 kByte) -> 1.228 MBytes / second
Number of sectors: 103 (=242 kByte) -> 1.508 MBytes / second
Number of sectors: 154 (=362 kByte) -> 2.066 MBytes / second
Number of sectors: 231 (=543 kByte) -> 2.107 MBytes / second
Number of sectors: 346 (=813 kByte) -> 2.452 MBytes / second
Number of sectors: 519 (=1220 kByte) -> 2.575 MBytes / second
Number of sectors: 778 (=1829 kByte) -> 2.712 MBytes / second
Number of sectors: 1167 (=2744 kByte) -> 2.860 MBytes / second
Number of sectors: 1750 (=4116 kByte) -> 2.949 MBytes / second
Number of sectors: 2625 (=6174 kByte) -> 2.993 MBytes / second
Number of sectors: 3937 (=9259 kByte) -> 3.031 MBytes / second
Number of sectors: 5905 (=13888 kByte) -> 3.086 MBytes / second
Number of sectors: 8857 (=20831 kByte) -> 3.144 MBytes / second
Number of sectors: 13285 (=31246 kByte) -> 3.199 MBytes / second
Number of sectors: 19927 (=46868 kByte) -> 3.274 MBytes / second

-------------------------------
Result:
Maximum transfer rate: 10565 kBytes/Second
Cache size for audio data: 37 kByte

############################################
####           FINISHED
############################################


I don't know what this means. I detedcted the read features in EAC and it told me that caching wasn't supported so then I tried the Feurio Cache test and the above result came up. At the start it tells me the cache size is 2048 kByte and then at the end it says 37kByte? Does this mean it is supported or not (seeing that its only 37kByte)?

Thanks smile.gif
jimhaddon
i think no-one will help you, as you are making a nusance of yourself posting 2 topics
rutra80
It means that your drive has 2048KB of cache, and 37KB of it are used for audio caching, so unfortunatelly your drive probably does cache audio.
Sebastian Mares
How large is the data read by EAC again? Maybe the cache is smaller and therefore EAC reports that the device does not cache.
Cartman_Sr
Stop spamming. Do some research on your own instead. Try reading some help files for software you're using. gun2.gif
rutra80
QUOTE (Sebastian Mares @ May 7 2006, 23:08) *
How large is the data read by EAC again? Maybe the cache is smaller and therefore EAC reports that the device does not cache.

IIRC it's either 64KB, or 32KB...
Badass01
yo yo yo

hold up. I first posted it on here as I referred to the guide from here. Then i noticed the CD Hardware forum so I thought Id post in there as it may get more replies, I just thought about hitting more people as I thought people may just go to specific forums.

I then did do my own littel research based on what is in the CD Hardware forums and went to this site:
http://www.daefeatures.co.uk/

There, I searched for my model and found that caching is not supported so why is it coming up as 37kBytes?
Maybe as rutra80 says its 64 and 37 may be too less? Anyway shoud I just assume it doesn't support caching then?
rutra80
Wouldn't cached data to be completly overwritten, need to be at least 2 times smaller than amount of data read? I have some problems with logic here ATM wacko.gif
kritip
I read a topic just today on the eac forum, and andre responded, saying the samllest eac reads is 64k so it should be ok. He then mentioned it would cause no harm to tick the box anyway. Sorry i can't find the thread, it wasn't a new one on there, but i was researching it earlier on my laptop.

if the drive caches 37K though (like my LG 6167B) and eac reads chunks of 64k, if the error was in the first 37 k of that 64k chunk, surely it would go undetected, as it would use the same 32k cache topped off by a nother subsequent read, or would it re-read the whole chunk again?!

TO be on the safe side, i just tick the box anyway, you get the speed hit, but you know for sure you have nothing to worry about biggrin.gif

Kristian
Badass01
I am now even more confused. If there's no point to the tick box why is it there and why is it mentioned right at the start of the EAC + FLAC image guide blink.gif
rutra80
The box is there to tick if your drive caches audio (so extraction is secure but slower), or to untick if your drive doesn't cache audio (so extraction is faster on drives which don't cache, but if you untick it on a drive which caches you may get unsecure extraction).
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2009 Invision Power Services, Inc.