Problems when playing and ripping CDs. No problems with DVDs.

topcat01 · 2026-08-20 18:22:24

BTW I also use whipper with great success to rip CDs to FLAC. I had to go through the "calibration" before things worked. Have you tried that?

seth · 2026-08-20 19:18:38

The Mint live system will likely boot (from usb) independent of the sata configuration.
From all the symptoms it's the only thing I could currently suggest

dsatta · 2026-08-21 13:48:05

topcat01 wrote:

BTW I also use whipper with great success to rip CDs to FLAC. I had to go through the "calibration" before things worked. Have you tried that?

Yep I tried using whipper, no dice.

seth wrote:

The Mint live system will likely boot (from usb) independent of the sata configuration.
From all the symptoms it's the only thing I could currently suggest

I tried using Mint with RAID Sata mode and nothing.
I also noticed that I was one BIOS update behind so I updated it but still nothing.

I'll try to upload some audio files today.

dsatta · 2026-08-21 14:21:59

I just checked through my CD collection and I noticed I have an Enhanced CD, which is more like a Data CD than a CDDA. But it still crackled.

Here's a sample of the first song from the CD, which crackles a lot and took quite a while to rip due to the failing error correcting.
https://voca.ro/1ggj4f2WbCkZ

And here's how it should sound like
https://www.youtube.com/watch?v=-ePTS2Y7OME

dimich · 2026-08-21 16:01:43

dsatta wrote:

Here's a sample of the first song from the CD, which crackles a lot and took quite a while to rip due to the failing error correcting.
And here's how it should sound like

Ripped sample has slightly higher pitch than original one. For me, it looks more like resampling or time synchronization issue rather than corrupted data.

dsatta · 2026-08-21 16:04:09

dimich wrote:

Ripped sample has slightly higher pitch than original one. For me, it looks more like resampling or time synchronization issue rather than corrupted data.

Do you think the motherboard Sata controller or the CPU could cause those issues?

dimich · 2026-08-21 17:20:06

dsatta wrote:

Do you think the motherboard Sata controller or the CPU could cause those issues?

The last time I used CD to play audio, it was playing analog audio signal directly to line-in of audio card. Sorry, I'm not very familiar with CD audio path in modern systems. However, speculating I'd rather suspect software, not SATA or CPU.

Last edited by dimich (2026-08-21 17:20:46)

dimich · 2026-08-21 18:19:24

dimich wrote:

Ripped sample has slightly higher pitch than original one.

Nope, the pitch is the same. Sorry, frequency axis auto-scaling in ffmpeg's spectrogram confused me. Now checked with fixed frequency axis, no discrepancy between ripped and original samples.

UPD: Interestingly, number of samples between clicks is ≈640. 588 samples per CD-DA sector / 640 = 44100 / 48000.

Last edited by dimich (2026-08-21 19:12:15)

seth · 2026-08-21 20:42:04

Is the shared file an analog recording of you playing the file back on that system and holding a mic against the speakers or a slice of the rip?
https://wiki.archlinux.org/title/PipeWi … le_rate(s) - or just forego the sound daemon.

dsatta · 2026-08-22 09:34:31

It's a slice of the rip cut using audacity to the same bitrate (i ripped and encoded in mp3 192 kbps)

seth · 2026-08-23 15:17:28

I agree w/ @dimich that this has analog vibes, bit-glitches tend to sound different (beeps and queeks) and the DAC might pick up EM smog - but the ripping itself does not include an analog output (I don't think I've seen an optical drive with such in ages) and the frequency settings of the sound daemon also won't matter (at least as long as you're just ripping the PCM w/ cdparanoia, random GUI encoders might do random sh…tuff)
Speaking of which: cdparanoia does not print any errors or problems w/ the rip?
And this *does* affect the pcm stream before any encoding/compression steps?

dsatta · 2026-08-23 15:45:47

output of

cdparanoia -A

cdparanoia III release 10.2 (September 11, 2008)

Using cdda library version: 10.2
Using paranoia library version: 10.2
Checking /dev/cdrom for cdrom...
        Testing /dev/cdrom for SCSI/MMC interface
                SG_IO device: /dev/sr0

CDROM model sensed sensed: HL-DT-ST DVDRAM GHD0N 1.00 
 

Checking for SCSI emulation...
        Drive is ATAPI (using SG_IO host adaptor emulation)

Checking for MMC style command set...
        Drive is MMC style
        DMA scatter/gather table entries: 1
        table entry size: 131072 bytes
        maximum theoretical transfer: 55 sectors
        Setting default read size to 27 sectors (63504 bytes).

Verifying CDDA command set...
        Expected command set reads OK.

Attempting to set cdrom to full speed... 
        drive returned OK.

=================== Checking drive cache/timing behavior ===================

Seek/read timing:
        [57:16.48]:   31ms seek, 0.34ms/sec read [39.8x]                 
        [50:00.00]:   28ms seek, 0.37ms/sec read [36.1x]                 
        [40:00.00]:   33ms seek, 0.41ms/sec read [32.9x]                 
        [30:00.00]:   28ms seek, 0.44ms/sec read [30.0x]                 
        [20:00.00]:   29ms seek, 0.48ms/sec read [27.5x]                 
        [10:00.00]:   38ms seek, 0.59ms/sec read [22.6x]                 
        [00:00.00]:   43ms seek, 0.74ms/sec read [18.0x]                 

Analyzing cache behavior...
        Approximate random access cache size: 27 sector(s)               
        Drive cache tests as contiguous                           
        Drive readahead past read cursor: 128 sector(s)                
        Cache tail cursor tied to read cursor                      
        Cache tail granularity: 0 sector(s)                      
                Cache read speed: 0.07ms/sector [190x]
                Access speed after backseek: 0.72ms/sector [18x]
        Backseek flushes the cache as expected

Drive tests OK with Paranoia.

output of

cdparanoia -v -d /dev/sr0 1

cdparanoia III release 10.2 (September 11, 2008)

Using cdda library version: 10.2
Using paranoia library version: 10.2
Checking /dev/sr0 for cdrom...
        Testing /dev/sr0 for SCSI/MMC interface
                SG_IO device: /dev/sr0

CDROM model sensed sensed: HL-DT-ST DVDRAM GHD0N 1.00 

Checking for SCSI emulation...
        Drive is ATAPI (using SG_IO host adaptor emulation)

Checking for MMC style command set...
        Drive is MMC style
        DMA scatter/gather table entries: 1
        table entry size: 131072 bytes
        maximum theoretical transfer: 55 sectors
        Setting default read size to 27 sectors (63504 bytes).

Verifying CDDA command set...
        Expected command set reads OK.

Attempting to set cdrom to full speed... 
        drive returned OK.

Table of contents (audio tracks only):
track        length               begin        copy pre ch
===========================================================
  1.    19101 [04:14.51]        0 [00:00.00]    no   no  2
  2.    18727 [04:09.52]    19101 [04:14.51]    no   no  2
  3.    17257 [03:50.07]    37828 [08:24.28]    no   no  2
  4.    17026 [03:47.01]    55085 [12:14.35]    no   no  2
  5.    20825 [04:37.50]    72111 [16:01.36]    no   no  2
  6.    19101 [04:14.51]    92936 [20:39.11]    no   no  2
  7.    17825 [03:57.50]   112037 [24:53.62]    no   no  2
  8.    23270 [05:10.20]   129862 [28:51.37]    no   no  2
  9.    15656 [03:28.56]   153132 [34:01.57]    no   no  2
 10.    17465 [03:52.65]   168788 [37:30.38]    no   no  2
 11.    17417 [03:52.17]   186253 [41:23.28]    no   no  2
 12.    18941 [04:12.41]   203670 [45:15.45]    no   no  2
 13.    17351 [03:51.26]   222611 [49:28.11]    no   no  2
 14.    18803 [04:10.53]   239962 [53:19.37]    no   no  2
TOTAL  258765 [57:30.15]    (audio only)
 
Ripping from sector       0 (track  1 [0:00.00])
          to sector   19100 (track  1 [4:14.50])

outputting to cdda.wav

 (== PROGRESS == [!!V!V!V!V!!!!!V!V!V!!!V!V!!!V!| 019100 00 ] == :^D * ==)   

Done.

The progress bar is full of errors

!  Errors found after stage 1 correction; the drive is making the same error through multiple re-reads, and cdparanoia is having trouble detecting them.

V Uncorrected error/skip

Smiley faces were often these:

:-P Unreported loss of streaming in atomic read operation

8-| Finding read problems at same point during reread; hard to correct

seth · 2026-08-23 16:10:43

So there's your problem… BUT WHY? <insert meme here>

For recap, you tried different sata ports(?) and power adapters (!) - resp. the power adapter can be ruled out for cross system usage.
Also ruled out the sata cable by either replacing it or carrying between systems?
The sata mode (raid/ahci) has no impact?
Are there (many) other sata devices? Can you reduce those to the minimum resp. remove all of them when booting the live system?

dsatta · 2026-08-23 16:15:23

Yep tried different Sata ports, cables and modes to no avail. Also power cables.
There are 4 Sata devices connected to the motherboard: 1 Sata SSD, 2 HDDs, and the CD-ROM Drive. I can definitely try removing all of those except the Drive when I don't have to use the computer as I am studying for an exam right now. Will keep you updated for when I try it.

topcat01 · 2026-08-23 18:09:44

Does this machine pass a long memtest? I forget if this was tried already, sorry.

sharow · 2026-08-24 09:12:18

dsatta wrote:

output of

cdparanoia -A

The progress bar is full of errors

!  Errors found after stage 1 correction; the drive is making the same error through multiple re-reads, and cdparanoia is having trouble detecting them.

V Uncorrected error/skip

Smiley faces were often these:

:-P Unreported loss of streaming in atomic read operation

8-| Finding read problems at same point during reread; hard to correct

https://www.xiph.org/paranoia/bugs.html

Some drives that cause the 8-| smilie and '!' mark in the status bar (dropped/duplicated bytes found after first stage \
verification) will likely also click. The 8-| smilie indicates that the drive is making errors that are difficult to de\
tect.

I suspect it may not be handling the partially-read state correctly.
https://github.com/jwilk-mirrors/cdpara … ace.c#L294

Typically one checks for return value and EAGAIN||EWOULDBLOCK(it's O_NONBLOCK), and call another read() for remaining data if needed. Since this function does not returns how many bytes were partilly read, I suspect it may be seeking back(SEEK_SET) and trying again(and fail again). It’s just speculation. I don’t want to pursue it any further.

BTW my observation is that glitch rate is 75 glitches per second.
That matches this rate.
https://en.wikipedia.org/wiki/Track_(op … dio_tracks

Last edited by sharow (2026-08-24 09:16:59)

seth · 2026-08-24 14:09:45

Yes… we know.
The question is *why* does it struggle with reading disks only in that system (if this was an old drive doing that everywhere I'd tell you to get a new drive and if it was a bunch of old discs I'd tell you to try to clean and then quickly back them up)

Though at this point it has to be some weirdness w/ the SATA bus, let's see what #39 resolves to…

euromatlox · 2026-08-24 18:46:41

Could this be related to sound cards (including motherboard's audio) ?

I recently had both Asus Xonar DGX (PCIe) and M-Audio Audiophile 24/96 (PCI) installed, and got sound errors while M-Audio was recording using Audacity.
Also M-audio did disappear now and then (lspci).

I think the reason to my problems was that there are no real PCI sockets anymore...both motherboard and Asus Xonar have ASM1083 PCIe to PCI Bridge installed.
Did this cause IRQ conflict or something else...don't know.

I just removed Asus Xonar soundcard, kept M-Audio (added a mixer with headphone socket for listening). So only 1 soundcard in my PC.
Motherboard is Server board without any audio (Asus P8B-M).

Last edited by euromatlox (2026-08-24 18:52:56)

dsatta · 2026-08-25 15:23:55

Important update:

I managed to get my hands on an USB Drive and lo and behold, it works without any problems, so the problem is definitely the SATA controller. For now I will be using that drive to listen to and rip CDs.
I wonder if anyone else with my motherboard has this same problem.
Thanks everyone for their inputs on this, I think at this point unfixable, problem

V1del · 2026-08-25 17:09:31

Random thought, potentially the drive not liking SATA power management? https://wiki.archlinux.org/title/Power_ … Management -- can you try setting that to max_performance resp. verify what it is set to? I don't think anyone mentioned checking that explicitly yet, though it "shouldn't" be active on a desktop, but depending on how the UEFI announces itself, who knows.

Last edited by V1del (2026-08-25 17:11:52)

mwillems · 2026-08-25 19:43:05

I read this thread with great interest because I have a very similar problem: I have an internal DVD drive that will read DVDs perfectly, but struggles to read CDs. It produces staticky, error-filled CD rips regardless of which software I use, but all DVD rips are perfect in every respect. I also have an internal blu-ray drive in the same system that can read all discs correctly with no problems.

I initially assumed that my DVD drive was failing in an idiosyncratic way, but it worked fine when plugged into another computer, just like yours. I eventually gave up troubleshooting because the blu ray drive worked for CD ripping just fine, but this thread caught my attention for obvious reasons.

FWIW my motherboard in the affected system is not the same exact model as yours, but it is also a relatively recent Gigabyte Ryzen board (mine is a Gigabyte B650 AORUS Elite AX Wifi). I've had the problem ever since I switched the drive over to this motherboard two years back. I wonder if there's something up with Gigabyte's SATA controllers?

EDIT: I can confirm that all my SATA link power policies are set to max_performance and have been consistently. That setting, at least for my version of the issue, doesn't fix it.

Last edited by mwillems (2026-08-25 19:50:35)

seth · 2026-08-25 19:57:34

dsatta wrote:

There are 4 Sata devices connected to the motherboard: 1 Sata SSD, 2 HDDs, and the CD-ROM Drive. I can definitely try removing all of those except the Drive

Do you also have more noise on the bus (given there's also a BD drive…)?
Do you know whether the board uses multipliers?
https://en.wikipedia.org/wiki/SATA#Topology

topcat01 · 2026-08-25 20:08:24

This is indeed a most mysterious problem. There was some speculation about analog signals earlier, but if we are not directly playing and using cdparanoia to rip, it's a fully digital data flow, just like reading a data CD. This leads me to wonder if the drive can read a data CD properly.

This is very interesting to me since I recently helped a friend rip their entire CD collection to FLAC using whipper (with full metadata, and accuraterip verification), and the only problems were with discs with visible damage. Most of those worked after a good cleaning, however there were a couple with bad scratches which we could not recover.

Note also that CD and DVD uses different laser wavelengths and usually the player has a different laser for each medium. However, since the drives work on other computers it's unlikely the (infrared) CD laser is malfunctioning. DVD uses a red laser rather than infrared.

Last edited by topcat01 (2026-08-25 20:17:50)

mwillems · 2026-08-25 20:14:22

If you mean audible noise, no the drive doesn't make any unusual noises and exhibits the issue regardless of whether the BR drive is spinning. If you mean electrical noise, the only conventional SATA devices are the DVD and Bluray drive, one plugged into SATA port 1, the other into SATA port 3. The system harddrive is an NVME drive which I think coming in through the PCI controller directly rather than through the SATA controller (it doesn't have an "ata" location under /dev/disk/by-path/).

I don't know a definitive way to figure out if multipliers are in use, but lspci shows a single SATA controller, but I have six SCSI ports under /sys/class/scsi_host/, which suggests maybe so?

Happy to run diagnostics if you can more specifically describe where to look or what commands to run!

To TopCat01, Accurate rip is what tipped me off to the problem in my case as I not only never got a successful AccurateRip on the first try, the re-reads would frequently fail to resolve the issues even on perfect discs (i.e. discs that read perfectly on other drives and appeared in perfect shape). And the same drive can produce a bit-perfect copy of a DVD verified by checksums! The drive also fails to burn CDs, but that's a whole other kettle of fish. I don't have any Data CDs on hand to test, but I agree that would be an interesting test. For completeness the software I used to try and rip CDs with the affected drive are soundjuicer, cdparanoia, JRiver Media Center, and an old version of dBPoweramp (through wine). None worked with the affected drive, all worked with the Blu Ray drive.

Last edited by mwillems (2026-08-25 20:20:32)

topcat01 · 2026-08-25 20:19:35

Yes, I always use accuraterip. Note also my comment about different lasers, although I don't know how that might be relevant given the facts.

Arch Linux

#26 2026-08-20 18:22:24

Re: Problems when playing and ripping CDs. No problems with DVDs.

#27 2026-08-20 19:18:38

Re: Problems when playing and ripping CDs. No problems with DVDs.

#28 2026-08-21 13:48:05

Re: Problems when playing and ripping CDs. No problems with DVDs.

#29 2026-08-21 14:21:59

Re: Problems when playing and ripping CDs. No problems with DVDs.

#30 2026-08-21 16:01:43

Re: Problems when playing and ripping CDs. No problems with DVDs.

#31 2026-08-21 16:04:09

Re: Problems when playing and ripping CDs. No problems with DVDs.

#32 2026-08-21 17:20:06

Re: Problems when playing and ripping CDs. No problems with DVDs.

#33 2026-08-21 18:19:24

Re: Problems when playing and ripping CDs. No problems with DVDs.

#34 2026-08-21 20:42:04

Re: Problems when playing and ripping CDs. No problems with DVDs.

#35 2026-08-22 09:34:31

Re: Problems when playing and ripping CDs. No problems with DVDs.

#36 2026-08-23 15:17:28

Re: Problems when playing and ripping CDs. No problems with DVDs.

#37 2026-08-23 15:45:47

Re: Problems when playing and ripping CDs. No problems with DVDs.

#38 2026-08-23 16:10:43

Re: Problems when playing and ripping CDs. No problems with DVDs.

#39 2026-08-23 16:15:23

Re: Problems when playing and ripping CDs. No problems with DVDs.

#40 2026-08-23 18:09:44

Re: Problems when playing and ripping CDs. No problems with DVDs.

#41 2026-08-24 09:12:18

Re: Problems when playing and ripping CDs. No problems with DVDs.

#42 2026-08-24 14:09:45

Re: Problems when playing and ripping CDs. No problems with DVDs.

#43 2026-08-24 18:46:41

Re: Problems when playing and ripping CDs. No problems with DVDs.

#44 2026-08-25 15:23:55

Re: Problems when playing and ripping CDs. No problems with DVDs.

#45 2026-08-25 17:09:31

Re: Problems when playing and ripping CDs. No problems with DVDs.

#46 2026-08-25 19:43:05

Re: Problems when playing and ripping CDs. No problems with DVDs.

#47 2026-08-25 19:57:34

Re: Problems when playing and ripping CDs. No problems with DVDs.

#48 2026-08-25 20:08:24

Re: Problems when playing and ripping CDs. No problems with DVDs.

#49 2026-08-25 20:14:22

Re: Problems when playing and ripping CDs. No problems with DVDs.

#50 2026-08-25 20:19:35

Re: Problems when playing and ripping CDs. No problems with DVDs.

Board footer