Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[tij]

I still rip my music with 3rd party tools EAC (exact audio copy) and CUEtools/CUERipper (when rip has errors and needs to be repaired)

Reason for using above is AccuRip and CUETools Database … both are databases of checksums of CDs ripped by other ppl

I know that online databese can be manipulated … but imho:

(1) this is only concern for people who rip pirated copies of CDs  ... when you rip pirated copy and database gives you confidence of 500 people had ripped same CD with same result ... you never sure if those other 500 people were ripping same inferior quality pirated CD

(2) on the other hand when you ripped legitimate copy of CD and database gives you confidence of only 1 person that ripped same CD with same result … it gives you comfort (as its highly unlikely that 2 damaged CDs will give you same checksum)

(3) i had CDs that i know have bad scratches … and ripping those sometimes had several tracks mismatching database (EAC struggled with them … but in the end reported it was able to rip ... reripping those track several times gave different checksum everytime) … sometimes I able just to rerip problematic tracks till result matched database … and that gave peace knowing that I had a perfect rip (I don't rerip problematic tracks anymore since I discovered that CUETools can repair rips depending on CD damage)

(4) CUETools can repair rips from damaged CD!!! ... i just used CUERipper (uses older version of EAC) and then CUETool to rip CD i put in the bin of "cannot rip ... need to buy on ebay" (read some advised on net) ... wow

I think in the age where CD sales are dropping ... and some CDs can only be have used … it is great asset to be able to verify your rip integrity and most importantly have chance to repair rips from scratched CDs before going to ebay again to try buy that CD in "better condition"

so ... AccuRip, CUETools Database to verify current ripping process … verify older rips that were not verified before … and ability to restore/repare bad rips

[tij]

Just repaired rip from badly scratched CD using (EAC to rip and CUETools to repair the rip) … you can see from attached picture the extend of scratches ... there are several scratches with black color around edges - those scratches are actually on top of CD that removed data layer off

Since i know my CD is genuine and not pirated (2002 Nirvana compilation album) … comparing restored rip to other people rip with same CD (there were 4 tracks that managed to be accurately ripped … so I know CDs I was comparing to in database are from non-pirated CDs) gave me confidence that restored rip is accurate

Why all this fuss? ... i've been ripping CD for awhile now and only found out I can repair bad rips very recently … hopefully someone will benefit from this … and hopefully JRiver can incorporate this feature into MC

Some details on my repair below

Extract from original rip report
AccurateRip summary
 
Track  1  accurately ripped (confidence 200)  [8EC994AB]  (AR v2)
Track  2  accurately ripped (confidence 200)  [CB347121]  (AR v2)
Track  3  cannot be verified as accurate (confidence 200)  [0DF4D22D], AccurateRip returned [244BBEBB]  (AR v2)
Track  4  accurately ripped (confidence 200)  [EB21D5E9]  (AR v2)
Track  5  cannot be verified as accurate (confidence 200)  [5E3CBBFD], AccurateRip returned [97394777]  (AR v2)
Track  6  accurately ripped (confidence 200)  [12E0D3F9]  (AR v2)
Track  7  cannot be verified as accurate (confidence 200)  [24128F93], AccurateRip returned [EA3032D4]  (AR v2)
Track  8  cannot be verified as accurate (confidence 200)  [9F010BA1], AccurateRip returned [99BB126E]  (AR v2)
Track  9  cannot be verified as accurate (confidence 200)  [5C47A6D7], AccurateRip returned [DECEC4F3]  (AR v2)
Track 10  cannot be verified as accurate (confidence 200)  [09CEBC96], AccurateRip returned [0EB95AD8]  (AR v2)
Track 11  cannot be verified as accurate (confidence 200)  [F729C2A3], AccurateRip returned [F6C7EDB2]  (AR v2)
Track 12  cannot be verified as accurate (confidence 200)  [79D09801], AccurateRip returned [0D2B12AA]  (AR v2)
Track 13  cannot be verified as accurate (confidence 200)  [984F5D16], AccurateRip returned [85CB0417]  (AR v2)
Track 14  cannot be verified as accurate (confidence 200)  [82B859E1], AccurateRip returned [F3867D49]  (AR v2)
Track 15  cannot be verified as accurate (confidence 200)  [F839A36B], AccurateRip returned [5B8B212D]  (AR v2)
 
 4 track(s) accurately ripped
11 track(s) could not be verified as accurate

Extract from repair report
[CUETools log; Date: 9/19/2019 12:08:46 AM; Version: 2.1.5]
CUETools DB: corrected 17044 errors.
[AccurateRip ID: 001cd2e4-014aca7a-f20cd60f] found.
Track   [  CRC   |   V2   ] Status
 01     [f862b54b|8ec994ab] (200+200/932) Accurately ripped
 02     [f806b2a5|cb347121] (200+200/930) Accurately ripped
 03     [60078755|c8dbbee1] (200+200/929) Accurately ripped
 04     [2aaa5775|eb21d5e9] (200+200/930) Accurately ripped
 05     [704a04cd|4c3ff43a] (200+200/929) Accurately ripped
 06     [1328d4fa|12e0d3f9] (200+200/933) Accurately ripped
 07     [c1370f5f|9fb44d72] (200+200/927) Accurately ripped
 08     [0b2f214d|6f836951] (200+200/924) Accurately ripped
 09     [4cf133af|45b91c54] (200+200/925) Accurately ripped
 10     [132b465c|7d66077a] (200+200/926) Accurately ripped
 11     [bded1fe4|c84b235b] (200+200/928) Accurately ripped
 12     [64ecc486|27abf83d] (200+200/926) Accurately ripped
 13     [e8d58950|e156fbbb] (200+200/923) Accurately ripped
 14     [bd11c72c|eb3f5f43] (200+200/925) Accurately ripped
 15     [6570f6ed|7aac1c74] (200+200/923) Accurately ripped

[Awesome Donkey]

You might try doing a search of the forums, AccurateRip support has been discussed multiple times before.

https://yabb.jriver.com/interact/index.php/topic,58595.0.html
https://yabb.jriver.com/interact/index.php/topic,58494.0.html
https://yabb.jriver.com/interact/index.php/topic,91781.0.html

From the looks of it, I wouldn't hold my breath for this as I don't imagine their stance has changed.

[tij]

Actually … repair/correction of rip comes from CUETools database … AccurateRip database can only be used to verify rip

Its harder to manipulate AccurRip database as rip is put in DB per CD-Drive (so if I rip several times same CD from same PC using same CD-Drive … its seems to put only one result in DB) … CUETools database updates database just from checking your existing rip (checking multiple times from same PC seems to put one record in DB)

This post was originally posted in "Who do we love?" as a suggestion to play with CUETools or AccuRip (CUETools is more useful as can use it to repair bad rips)

Previous discussion seemed not to mention ability to actually correct bad rips from badly scratched CDs (enough data have to be accurately ripped to be able to repair bad portion of rip … so not all bad rips can be repaired) … so I thought to mention it

Personally … I am happy to do my rips and their correction (if needed) outside of MC … so once this was separated from "Who do we love?", I thought to use it as a pointer to people who are not aware that bad rips can be repaired (so far I was able to accurately repair all my CDs I previously deemed "too damaged for ripping - need to get another copy form ebay"

[tij]

Here is what I do to repair the rip in CUETools (only lossless 44.1/16):

[CUE Paths]
1. select [Input] … can select CUE Sheets or files
2. select [Output] where repaired files are to be placed

[Action]
1. select [Encode] to indicate that I want to generate files ([Verify] will only check your rip against database)
2. select [repair] in drop box

[Mode]
1. select [Tracks] if want one track per song … or [Image + CUE] if want CD image with CUE sheet

[Audio Output]
1. select codec to encode audio

Once hit [Go] … a popup will ask you to select CD that best matches your rip

Then it will verify your current rip against database … if CD cannot be repaired, it will generate report where your tracks will be listed as "no match found"

if CD can be repaired … you will be presented with choice to repair against previous rips done by other ppl .. in screen shot attached you can see I was offered 2 choices to repair my 2002 Nirvana disc

choose one with most "confidence" as it indicates how many people had rip that CD with same result

you can see there is choice there with confidence 1 … that's my original attempt at ripping the CD which failed to be repaired (I actually ripped this CD multiples times till one of the rip was reparable … it seems only one attempt at the rip was put in the database as I mentioned before)