tsuzu / xld

Automatically exported from code.google.com/p/xld
0 stars 0 forks source link

XLD reports "AccurateRip: YES" in main window, but tracks not found in DB during rip/verify #147

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Rip this particular CD, or Verify a previous rip of it.
2.
3.

How about the reproducibility (always, sometimes, rarely, ...)?

100%.

What is the expected output? What do you see instead?

I see:

AccurateRip Summary (DiscID: 0010e56f-00924f8f-7c099e0b)
    Track 01 : Not Found
    Track 02 : Not Found
    Track 03 : Not Found
    Track 04 : Not Found
    Track 05 : Not Found
    Track 06 : Not Found
    Track 07 : Not Found
    Track 08 : Not Found
    Track 09 : Not Found
    Track 10 : Not Found
    Track 11 : Not Found
        ->0 track accurately ripped, 11 tracks not found

What version of the product are you using? On what operating system?

Version 20121222 (142.2)

Please provide any additional information below.

This is the first time I've seen this, in hundreds of rips.

Both CDs of a 2-CD set I've just bought (Everything but the Girl, Idlewild), 
show this behaviour:

- After disc pre-gap detection, XLD shows the tracks, and says "AccurateRip: 
YES" in the bottom status bar. I've always taken this to mean that the disc was 
found in the AR DB...?

- After rip, the log file shows that the tracks were not found in the DB; see 
attached.

- This also occurs on Verify of a previous rip, for these CDs.

Other CDs I have continue to rip and verify correctly.

If the tracks are really not in the AR DB, then why does XLD say "AccurateRip: 
YES" in the bottom status bar?

thanks much indeed.

Original issue reported on code.google.com by cdmac...@gmail.com on 1 Jan 2013 at 11:16

Attachments:

GoogleCodeExporter commented 9 years ago
I should add: I've often seen CDs not in the AR DB, but in those cases XLD has 
always said "AccurateRip: NO".

Original comment by cdmac...@gmail.com on 1 Jan 2013 at 11:17

GoogleCodeExporter commented 9 years ago
It could happen when the database has an entry for the disc but it doesn't 
contain any valid data.

Not a bug.

Original comment by tmkkmac on 1 Jan 2013 at 11:20

GoogleCodeExporter commented 9 years ago
Thanks!

Original comment by cdmac...@gmail.com on 1 Jan 2013 at 1:14

GoogleCodeExporter commented 9 years ago
I'll change a behavior not to say YES for those kind of disks.

Original comment by tmkkmac on 1 Jan 2013 at 1:28

GoogleCodeExporter commented 9 years ago
Thanks again, much appreciated...

Original comment by cdmac...@gmail.com on 1 Jan 2013 at 5:40