Drive Read Cache (none)

[Helvetia]

Hello
Is the automatic drive read cache reliable? I have a Plextor PX-B950SA. The detection gives the result "Drive does not appear to cache, no cache clearing will be used test time without re-read. 5,803 ms test time with re-read: 11684 ms" Detected cache size 0 KB (0 frames) Is the possible?

[Test FUA Support] gives the result "CD drive rejected FUA clear command, FUA will not be uses."

I wonder Exact Audio Copy the message "drive caches audio data". Which statement is true? dBpoweramp CD Ripper or Exact Audio Copy?

Looking forward to answers, Thanks

[Spoon]

Re: Drive Read Cache (none)

It is not 100% reliable, getting cache is notoriously difficult on some drives.

Those numbers are consistent with a drive which does not cache.

[Helvetia]

Re: Drive Read Cache (none)

what setting would you choose in my case?

[Spoon]

Re: Drive Read Cache (none)

The safe option is to set the drive caches 1024KB

[Helvetia]

Re: Drive Read Cache (none)

many thanks for the solution. I would like to know why 1024 is the safest solution. there is a report on this?

[Spoon]

Re: Drive Read Cache (none)

1024KB is larger than any cache (audio) on any CD drive.

[Helvetia]

Re: Drive Read Cache (none)

OK. Is it true that all the settings are actually irrelevant when the CD was read accurate?

So long as no read errors happen and the CDs were read accurate are those settings as cache for example or read speed etc, it is really necessary to change settings?


I have to safety the max. Reading speed to 16x limited. Do you find this unnecessary as long as accurate read?

[Spoon]

Re: Drive Read Cache (none)

If accurateRip verifies yes.

Reading speed should not be limited, many drives rips better at higher speeds.

[Porcus]

Re: Drive Read Cache (none)

Is 4 kB too low to be a reliable number?

What about this: I took a doubtful CD, that needed individual frames reripped, and they seemed to clock in at 10/12 matching. Then cache cannot be as big as ten frames?
(If so, how many bytes it 10 frames? I.e. is one frame only the audio size, is it the total data transmitted for a frame of audio, or what?)


(There are many threads about drive cache, I picked a recent one. Could be others more relevant.)

[Spoon]

Re: Drive Read Cache (none)

the 10/12 is the times matched and re-read. Audio cache can be as small as 4KB

[Porcus]

Re: Drive Read Cache (none)

If cache were big enough to fit 10 frames, then wouldn't I have 10/10?

[Spoon]

Re: Drive Read Cache (none)

These are frame re-reads, they are the same if cache is 0 or 1024KB

[Porcus]

Re: Drive Read Cache (none)

I'm maybe a bit slow: wouldn't a caching drive re-read from cache when you ask it to re-read frame X?
If cache is as large as 10 times the frame, wouldn't it then automatically feed you ten identical frames?

Isn't this what the kilobytes number in the config is used to defeat?