Probably 20 years ago I implemented "auto rip" in the Grip audio CD ripper. You could optionally enable two settings: "Select all tracks and start ripping when

Probably 20 years ago I implemented "auto rip" in the Grip audio CD ripper. You could optionally enable two settings: "Select all tracks and start ripping when a disk is inserted" and "eject the disk when ripping is done". Worked like a charm. https://www.mankier.com/1/grip https://www.mankier.com/1/grip Years later when I was burning hundreds of CDs a month for our Linux distribution (I think peak was 700 CDs a month), I implemented an "autoburn" system: - Detect insertion of a disc. - Burn the image to the disc. - Verify the burned disc. - If it succeeded verification, eject it. So we could just go around to the CD drives, put in the blanks, and then come back a bit later and put the ejected discs into envelopes. Any drives not flashing their activity LEDs but with the drive bay closed were bad burns. I eventually implemented a custom verification process based largely on time required to read each block, as well as the checksum. We found that any disc with any sectors that took more than some number of ms to read, would likely fail in some customer drives. We had some discs that would verify, but would take a little, or in some cases a long time to read. Instead of 3 minutes, we had some discs that would take 30 minutes to read, but would return the correct checksum. We tracked this down by paying our users to send us back discs that they couldn't read, to identify the failure. Not all blank CDs were created equal. We had some media that would produce up to 50% failures using this testing. Taiyo Yuden media was consistently inexpensive but produced few if any failures.