To anyone going down this route, there's a surprisingly deep rabbit hole when you look into "how copy the bits off the drive and into a .wav file". There are a lot of places where errors can be introduced: the quality of the CD drive, the condition of the disc itself, how fast the drive is spinning for the rip, etc. I didn't think this was a big issue until I got a load of cheap used discs, started ripping them with my laptop, and later discovered issues with some of the rips, even on discs which looked perfectly fine.
There's a tool called cdparanoia[1] whose goal is to babysit the CD drive and ensure that it gets a complete, perfect, uninterrupted stream of bits off the drive, and will use a lot of tricks to go back and re-read any data that didn't come back cleanly. I always used it with abcde[2], which was a wrapper around it with album lookup, tagging, and ffmpeg support. I highly recommend anyone amassing a CD rip collection take a look at it, both are still packaged in present-day Ubuntu.
There's a tool called cdparanoia[1] whose goal is to babysit the CD drive and ensure that it gets a complete, perfect, uninterrupted stream of bits off the drive, and will use a lot of tricks to go back and re-read any data that didn't come back cleanly. I always used it with abcde[2], which was a wrapper around it with album lookup, tagging, and ffmpeg support. I highly recommend anyone amassing a CD rip collection take a look at it, both are still packaged in present-day Ubuntu.
[1] https://www.xiph.org/paranoia/faq.html [2] https://abcde.einval.com/wiki/