Skip to main content

Topic: Where is the problem in this chain? (Read 2914 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.
  • fncll
  • [*]
Where is the problem in this chain?
A few CDs I've ripped with EAC using Burst mode, test and copy (which seems to yield the highest average that I can verify), with perfectly matching CRCs. I then encoded using Lame 3.96.1 -V1 -- but the resulting encoded files have obvious glitches and flaws (not noise artifacts).

I've never seen this before. But if the CRCs matched when ripped from EAC, then that means the problem must be something happening during the encoding process right? I don't have the original WAV files available to listen to them, but logically...
  • Last Edit: 13 July, 2005, 02:00:06 AM by fncll

  • Never_Again
  • [*][*][*][*][*]
  • Members (Donating)
Where is the problem in this chain?
Reply #1
LAME 3.96.1 -V1 is not going to introduce glitches into your encoding. The problem is most likely the CDs.

Where is the problem in this chain?
Reply #2
use secure mode, at least it will give you a list of possible errors after ripping the cd.
Who are you and how did you get in here ?
I'm a locksmith, I'm a locksmith.

  • fncll
  • [*]
Where is the problem in this chain?
Reply #3
I'll try it. It just seems strange to me that EAC could match CRCs while introducing errors-- but equally strange that the encoding would get glitched!

  • evereux
  • [*][*][*][*][*]
Where is the problem in this chain?
Reply #4
Do the CDs have any kind of copy protection?
daefeatures.co.uk

Where is the problem in this chain?
Reply #5
Or is it possible that you're hearing clipping?
"You can fight without ever winning, but never win without a fight."  Neil Peart  'Resist'