Rip CD相關知識教學/交流

jaffeinism

EAC 比較少用了, 因為準確性無DBPOWERAMP 高, 係有時DBPOWERAMP RIP吾到既TRACK, 先至用EAC補完...

jaffeinism

audio cache 好多參考文章都吾建議ON ... EAC & DBPOWERAMP 都係甘設定....

jaffeinism

CUETOOLS 可以CHECK到CRC, PEAK ...

[CUETools log; Date: 17/11/2016 1:08:52; Version: 2.1.5]
[CTDB TOCID: LWZNveehnYHVQC2JiUwbrZ6Q9yE-] found.
Track | CTDB Status
  1   | (4/4) Accurately ripped
  2   | (4/4) Accurately ripped
  3   | (4/4) Accurately ripped
  4   | (4/4) Accurately ripped
  5   | (4/4) Accurately ripped
  6   | (4/4) Accurately ripped
  7   | (4/4) Accurately ripped
  8   | (4/4) Accurately ripped
[AccurateRip ID: 0011202d-00732b0d-810c4b08] found.
Track   [  CRC   |   V2   ] Status
01     [c4a42927|afe79056] (0+1/1) Accurately ripped
02     [b82a6c1d|77a92405] (0+1/1) Accurately ripped
03     [d1b72d1d|1a6508bc] (0+1/1) Accurately ripped
04     [915901fd|05bf63f9] (0+1/1) Accurately ripped
05     [f7240330|28fcb13d] (0+1/1) Accurately ripped
06     [44b3690c|c5a263c4] (0+1/1) Accurately ripped
07     [37c75b66|39852fc7] (0+1/1) Accurately ripped
08     [322b90c9|8dadab0f] (0+1/1) Accurately ripped

Track Peak [ CRC32  ] [W/O NULL]
--   99.9 [76E1D32C] [5B23CB11]           
01   42.7 [B42785A4] [102EA4BD]           
02   86.7 [9112EC48] [85F7A04C]           
03   66.0 [90605414] [D367DEC1]           
04   63.5 [6A480835] [DFBB4920]           
05   63.3 [61D70E4C] [21B28AF8]           
06   78.0 [2F03DD03] [68650B51]           
07   48.1 [26095C37] [25B09ADD]           
08   99.9 [FBDB092F] [D2B9B4A1]           

fishfishfish

jaffeinism 發表於 2016-11-17 00:18
audio cache 好多參考文章都吾建議ON ... EAC & DBPOWERAMP 都係甘設定....

even 隻drive 唔cache audio, on左都100%唔影響質素
不過會rip耐左

jaffeinism

fishfishfish 發表於 2016-11-17 06:30
even 隻drive 唔cache audio, on左都100%唔影響質素
不過會rip耐左

cache  on會影響資料真確性, 所以無on好耐

fishfishfish

jaffeinism 發表於 2016-11-17 07:43
cache  on會影響資料真確性, 所以無on好耐

基本上係強烈建議你on
如果你隻drive唔cache audio, 係可以off, on左亦冇壞, 但會rip耐左
如果你隻drive cache audio, 但你off左, 就會有問題

所以我既guide都會建議on

Reference:
http://wiki.hydrogenaud.io/index.php?title=EAC_Drive_Options

Drive caches audio data
In order for secure mode to work properly, every read request made by EAC must cause the drive to seek data from the CD. If your drive caches audio, subsequent requests for the same data may result in the drive only fetching this data from its buffer, rather than from the physical disc. To prevent this from happening, EAC has a routine to ensure previously requested data gets flushed from drive's cache. This is done by having the drive read extra data from the disc—more data than the cache can store.

If the "Detect Read Features..." function reports "Caching : Yes", it is important that you enable the cache flushing routine by checking the "Drive caches audio data" box.

If the "Detect Read Features..." function reports "Caching : No", it is not necessary to enable the flushing routine. Checking the "Drive caches audio data" box with drives that are reported by EAC as not caching will not improve EAC's accuracy. It won't improve EAC's ability to detect errors nor EAC's ability to correct them. What it will do however, is reduce your ripping speed and shorten the life of your drive.

Tip #1: If you're concerned that your drive caches audio data even though EAC is saying otherwise, try ripping a scratched disc (one known to produce errors easily). Make sure you uncheck the "Drive caches audio data" setting AND uncheck the "Drive is capable of retrieving C2 error information" setting. Make sure you also set the error recovery quality to "Low" (this setting can be found under the Extraction tab in the EAC Options dialog). If EAC is capable of displaying a read error then cache flushing isn't necessary. Ignore any sync errors that may be displayed; they are irrelevant to this test.

Tip #2: Tip #1 is all you need to know, but if you're still paranoid that your drive caches audio, feel free to try Feurio's audio caching test (Ctrl+Alt+P\Test device\Cache test) or spath's cache explorer. If either determine that your drive doesn't cache or caches less than 64 KB of data, then cache flushing isn't necessary (ignore the reported buffer size when using cache explorer). The reason for the 64 KB barrier is that EAC will never request less than this amount while ripping (link).
Note: If "Drive has 'Accurate Stream' feature" is deselected, then "Drive caches audio data" is automatically checked, regardless of whether the drive actually caches audio data.

fishfishfish

jaffeinism 發表於 2016-11-16 22:15
Encoder: FLAC -compression-level-5 -verify
DSP Effects / Actions: -dspeffect1="CPU Throttle= -speed= ...

喱個係咩log?

fishfishfish

jaffeinism 發表於 2016-11-17 01:10
CUETOOLS 可以CHECK到CRC, PEAK ...

[CUETools log; Date: 17/11/2016 1:08:52; Version: 2.1.5]

照睇又冇問題bor...
冇聲係split左先冇聲定 原本已經冇聲?

Filling88

寫得好清楚。係disable cache. 如果唔disable cache，只會重覆從buffer讀取有問題嘅data，唔係重新由cd取data。
'enable cache flushing'。 flushing點解呢？查吓字典先！
(Post76 Android 手機版送出)

fishfishfish

Filling88 發表於 2016-11-17 10:20
寫得好清楚。係disable cache. 如果唔disable cache，只會重覆從buffer讀取有問題嘅data，唔係重新由cd取da ...

個drive有audio cache你係冇得"Disable"佢的, 最少EAC冇