Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: XLD ripped/extracted cd nowhere to be found (Read 7303 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

XLD ripped/extracted cd nowhere to be found

Hi -  new here

have just started ripping cds using xld as i've just started ripping my entire collection (well that's the plan)

i have ripped approx 20 cds with only 2 dramas -  one was extremely slow (REM's out of time) as in 2 1/2 hours per track once i got to track 5 onwards. i gave up half way through track 7 - i'm putting this down to my cheap samsung burner (se208db). i might go back and rip it without accuraterip or just with itunes on that (cd appears in health condition) - fell free to shed any light on this one, on the side, if there is anything i should know

HOWEVER what has me stunned right now is that i am ripping Sting's "nothing like the sun".
NOTE: this is a remastered/rerelease that has an "enhanced cd video" as it's last track

i have ripped this cd twice. (just the audio tracks - to AIFF).

now - XLD/the log tells me:
all tracks have been completed in their extracting/ripping
"no errors occurred"; and
"all tracks accurately ripped"

i can't find the tracks on my destination folder or anywhere on my imac anywhere

can anyone shed any light on this one?

btw when ripping cds, my destination is an external drive which is currently connected


regards
peter t

XLD ripped/extracted cd nowhere to be found

Reply #1
1) AccurateRip has nothing to do with ripping speed - it is completely independent of the ripping process itself.  What ripping mode were you using: XLD Secure, Paranoia, or Burst?  I'm assuming it was either XLD Secure or Paranoia - try Burst instead.  In fact, that's kind of the point of AccurateRip - you can rip in burst mode, and if the rip is confirmed accurate, you're good.  You'll gain absolutely nothing from ripping in one of the secure modes if AccurateRip can confirm the rip.

2) No ideas on the missing files - can you post the log from that rip?
"Not sure what the question is, but the answer is probably no."

XLD ripped/extracted cd nowhere to be found

Reply #2
Go to the XLD preferences and under the GENERAL tab look for "Output directory" It will say the destination of where your files are being saved.

XLD ripped/extracted cd nowhere to be found

Reply #3
Go to the XLD preferences and under the GENERAL tab look for "Output directory" It will say the destination of where your files are being saved.



its not there at all - all other rips have gone there with no dramas

but my ripped (missing) cd can not be found anywhere (using spotlight search)

XLD ripped/extracted cd nowhere to be found

Reply #4
Please verify that you have (1) tried ripping any other CDs since encountering this problem, (2) verified that their files appear where you expect, (3) tried to rip the problematic CD again, and (4) again got no files from it. We really need to be sure (A) that it’s the only one that exhibits this behaviour and (B) that it always does so.

XLD ripped/extracted cd nowhere to be found

Reply #5
thecrow, have you looked for 'unknown'? (unknown artist, unknown album)
korth

XLD ripped/extracted cd nowhere to be found

Reply #6
1) AccurateRip has nothing to do with ripping speed - it is completely independent of the ripping process itself.  What ripping mode were you using: XLD Secure, Paranoia, or Burst?  I'm assuming it was either XLD Secure or Paranoia - try Burst instead.  In fact, that's kind of the point of AccurateRip - you can rip in burst mode, and if the rip is confirmed accurate, you're good.  You'll gain absolutely nothing from ripping in one of the secure modes if AccurateRip can confirm the rip.

2) No ideas on the missing files - can you post the log from that rip?
Hi Mixminus1

thanks for that tip

i used Burst and the rem cd was quickly ripped.

the log did come back without confirming that all tracks were ripped accurately but i'm not too concerned about that as i'm thinking it shoul dbe fine as the cd is in good condition and this has put this cd's ripping issue to bed

the log had this to say on some tracks (excuse me not knowing how to attach stuff here):
Code: [Select]
AccurateRip Summary (DiscID: 0012900d-009f6f42-860a590b)
    Track 01 : OK (v1+v2, confidence 400/1365)
    Track 02 : OK (v1+v2, confidence 400/1372)
    Track 03 : OK (v1+v2, confidence 400/1375)
    Track 04 : NG (total 1364 submissions)
    Track 05 : NG (total 1363 submissions)
    Track 06 : NG (total 1375 submissions)
    Track 07 : NG (total 1366 submissions)
    Track 08 : NG (total 1376 submissions)
    Track 09 : NG (total 1376 submissions)
    Track 10 : NG (total 1369 submissions)
    Track 11 : NG (total 1376 submissions)
        ->3 tracks accurately ripped, 8 tracks not



Track 03
    Filename : /Users/petert/Music/XLD/R.E.M./Out Of Time - 1991/03-Low.aiff
    Pre-gap length : 00:02:20

    Track gain              : -4.08 dB
    Peak                    : 1.000000
    CRC32 hash (test run)    : 91731C7C
    CRC32 hash              : 91731C7C
    CRC32 hash (skip zero)  : C95929B1
    AccurateRip v1 signature : EA3F2792
    AccurateRip v2 signature : 269FD2BF
        ->Accurately ripped (v1+v2, confidence 200+200/1375)

Track 04
    Filename : /Users/petert/Music/XLD/R.E.M./Out Of Time - 1991/04-Near Wild Heaven.aiff
    Pre-gap length : 00:01:42

    Track gain              : -4.44 dB
    Peak                    : 1.000000
    CRC32 hash (test run)    : B82976E1
    CRC32 hash              : 9ACBFC0E
        ->Rip may not be accurate.
    CRC32 hash (skip zero)  : 3F32D0C3
    AccurateRip v1 signature : AA6130AB
    AccurateRip v2 signature : 3B44B678
        ->Rip may not be accurate (total 1364 submissions).

Track 05
    Filename : /Users/petert/Music/XLD/R.E.M./Out Of Time - 1991/05-Endgame.aiff
    Pre-gap length : 00:02:57

    Track gain              : -0.18 dB
    Peak                    : 0.642731
    CRC32 hash (test run)    : A31C95F3
    CRC32 hash              : 1ADC577B
        ->Rip may not be accurate.
    CRC32 hash (skip zero)  : AAC88733
    AccurateRip v1 signature : B5DFD7C7
    AccurateRip v2 signature : D06160CB
        ->Rip may not be accurate (total 1363 submissions).

Track 06
    Filename : /Users/petert/Music/XLD/R.E.M./Out Of Time - 1991/06-Shiny Happy People.aiff
    Pre-gap length : 00:02:18

    Track gain              : -4.76 dB
    Peak                    : 1.000000
    CRC32 hash (test run)    : A2DF213F
    CRC32 hash              : 0A3F35DE
        ->Rip may not be accurate.
    CRC32 hash (skip zero)  : 31509B77
    AccurateRip v1 signature : AFC1AE14
    AccurateRip v2 signature : BD70C90A
        ->Rip may not be accurate (total 1375 submissions).

XLD ripped/extracted cd nowhere to be found

Reply #7
Please verify that you have (1) tried ripping any other CDs since encountering this problem, (2) verified that their files appear where you expect, (3) tried to rip the problematic CD again, and (4) again got no files from it. We really need to be sure (A) that it’s the only one that exhibits this behaviour and (B) that it always does so.
hi db1989

i have ripped a couple of cds since my sting cd issues with no problem. the sting cd is the only one with extra features (ie the video as track 13)

i double checked the destination i have set and it was what i thought and the tracks never got there - i also checked my entire internal and that external drive for some of the tracks and they were nowhere

i had tried to rip the cd 3 or 4 times and achieved the same result and only this one cd has had this issue

see below for a bit of the log that came through indicating the rip had gone fine (go figure)


**** HOWEVER.......

after all of the above, i noticed that the external drive's light would not be flashing to indicate that the drive was ripping/working whilst the ripping was supposed to be going on. only time this happened (have ripped 25 cds thus far). this is a western digital 750gb my passport drive - usb 3. what i then did was change the destination to my imac's internal hard drive and it all worked well with no issue. so all is now taken care of!! 

so i ask, could the issue have been the slowness of the connection? and maybe because of the amount of data on a cd like this is stored, or how it's stored? again only time i have had this issue so far?

i noticed that the cd had no pregaps showing (as opposed to all my others - same settings used). i use "include pre-gap except for HTOA" if that matters at all


below is bits of the log of the unsuccessful rips to my external drive (excuse my inability to put these in as attachments):

** again, let me mention that all is good since i ripped this to my internal hard drive** , but if you can shed any light on this mystery (ie trap for young players , let me know)

cheers
peter t


Code: [Select]
X Lossless Decoder version 20130720 (144.0)

XLD extraction logfile from 2013-09-14 10:26:32 +1000

Sting / ...Nothing Like the Sun

Used drive : TSSTcorp CDDVDW SE-208DB (revision TS01)
Media type : Pressed CD

Ripper mode            : XLD Secure Ripper
Disable audio cache    : OK for the drive with a cache less than 1375KiB
Make use of C2 pointers : NO
Read offset correction  : 6
Max retry count        : 100
Gap status              : Analyzed, Appended (except HTOA)

TOC of the extracted CD
    Track |  Start  |  Length  | Start sector | End sector
    ---------------------------------------------------------
        1  | 00:00:00 | 04:36:07 |        0    |    20706 
        2  | 04:36:07 | 05:35:00 |    20707    |    45831 
        3  | 10:11:07 | 04:26:72 |    45832    |    65853 
        4  | 14:38:04 | 05:00:30 |    65854    |    88383 
        5  | 19:38:34 | 07:12:40 |    88384    |  120823 
        6  | 26:50:74 | 03:55:73 |    120824    |  138521 
        7  | 30:46:72 | 04:56:35 |    138522    |  160756 
        8  | 35:43:32 | 03:54:35 |    160757    |  178341 
        9  | 39:37:67 | 04:27:72 |    178342    |  198438 
      10  | 44:05:64 | 03:46:73 |    198439    |  215461 
      11  | 47:52:62 | 05:10:25 |    215462    |  238736 
      12  | 53:03:12 | 02:07:02 |    238737    |  248263 
      13  | 57:42:14 | 08:55:61 |    259664    |  299849 

List of alternate offset correction values
        #  | Absolute | Relative | Confidence
    ------------------------------------------
        1  |    670  |    664  |    107   
        2  |    675  |    669  |    94   
        3  |  -658  |  -664  |      6   
        4  |  -1968  |  -1974  |      6   
        5  |  -670  |  -676  |      5   

AccurateRip Summary (DiscID: 001b08be-00fd1a51-c10f9e0d)
    Track 01 : OK (v1+v2, confidence 21/248)
    Track 02 : OK (v1+v2, confidence 21/249)
    Track 03 : OK (v1+v2, confidence 22/250)
    Track 04 : OK (v1+v2, confidence 22/248)
    Track 05 : OK (v1+v2, confidence 21/246)
    Track 06 : OK (v1+v2, confidence 21/248)
    Track 07 : OK (v1+v2, confidence 21/248)
    Track 08 : OK (v1+v2, confidence 21/250)
    Track 09 : OK (v1+v2, confidence 21/248)
    Track 10 : OK (v1+v2, confidence 21/243)
    Track 11 : OK (v1+v2, confidence 21/246)
    Track 12 : OK (v1+v2, confidence 20/243)
        ->All tracks accurately ripped.

All Tracks
    Album gain              : -4.34 dB
    Peak                    : 1.000000
    Statistics
        Read error                          : 0
        Jitter error (maybe fixed)          : 0
        Retry sector count                  : 0
        Damaged sector count                : 0


Track 11
    Filename : /Volumes/AIFF/XLD/Sting/...Nothing Like the Sun - 1997/11-Little Wing.aiff

    Track gain              : -0.61 dB
    Peak                    : 0.998901
    CRC32 hash (test run)    : 3730B44B
    CRC32 hash              : 3730B44B
    CRC32 hash (skip zero)  : 5F5121D1
    AccurateRip v1 signature : BF7260F4
    AccurateRip v2 signature : 215A93DD
        ->Accurately ripped (v1+v2, confidence 13+8/246)
    Statistics
        Read error                          : 0
        Jitter error (maybe fixed)          : 0
        Retry sector count                  : 0
        Damaged sector count                : 0

Track 12
    Filename : /Volumes/AIFF/XLD/Sting/...Nothing Like the Sun - 1997/12-The Secret Marriage.aiff

    Track gain              : -2.43 dB
    Peak                    : 0.827545
    CRC32 hash (test run)    : EFFF4CA2
    CRC32 hash              : EFFF4CA2
    CRC32 hash (skip zero)  : AB20FA1F
    AccurateRip v1 signature : F164071D
    AccurateRip v2 signature : 4DA11BB4
        ->Accurately ripped (v1+v2, confidence 12+8/243)
    Statistics
        Read error                          : 0
        Jitter error (maybe fixed)          : 0
        Retry sector count                  : 0
        Damaged sector count                : 0

No errors occurred

End of status report

XLD ripped/extracted cd nowhere to be found

Reply #8
i used Burst and the rem cd was quickly ripped.

the log did come back without confirming that all tracks were ripped accurately but i'm not too concerned about that as i'm thinking it shoul dbe fine as the cd is in good condition and this has put this cd's ripping issue to bed

The snippet of log you attached explains why it was painfully slow in secure mode:  the disc is hosed.  For whatever reason, the disc can not be read well after track 3.  Note the CRC's for the test pass and final pass do not match after track 3.  Though you said the disc looks good, that is not necessarily a guarantee the data can be read correctly.

All that being said, have you listened to the rip?  It may have audible defects or it may sound fine.  If it sounds fine, you'll need to decide if that's good enough for you.  For some it is, but other people want a perfect copy for archiving. 

after all of the above, i noticed that the external drive's light would not be flashing to indicate that the drive was ripping/working whilst the ripping was supposed to be going on. only time this happened (have ripped 25 cds thus far). this is a western digital 750gb my passport drive - usb 3. what i then did was change the destination to my imac's internal hard drive and it all worked well with no issue. so all is now taken care of!!

so i ask, could the issue have been the slowness of the connection? and maybe because of the amount of data on a cd like this is stored, or how it's stored? again only time i have had this issue so far?

A USB 2 connection is much faster than you can rip a CD, so it's not that.  My first thought is that the leading "..." in the folder name is causing issues (files and folders that begin with a dot are hidden by the operating system, so I'd expect the rips to be there, just hidden).  But that wouldn't explain why it worked on your internal drive or how you saw no activity to the external drive.  Odd.

XLD ripped/extracted cd nowhere to be found

Reply #9
interesting re the"..." because i just ripped Phil Collins's (please forgive me) "...But seriously" cd to my internal hard drive. when i went back to check that i noticed there was no tracks at all to be seen in my folder structure.

the artist folder was there BUT no Album folder or tracks. again i did a spotlight serach for tracks and i found nothing

AND THEN

i looked further in the Sting album ("...nothing like the sun") and it was the same story - a sting folder but nothing under that.


i shall rerip these with a new album name (without "...") and i shall report back


(i'll also listen to a few tracks of the rem album

cheers
peter t

XLD ripped/extracted cd nowhere to be found

Reply #10
My first thought is that the leading "..." in the folder name is causing issues (files and folders that begin with a dot are hidden by the operating system, so I'd expect the rips to be there, just hidden).  But that wouldn't explain why it worked on your internal drive or how you saw no activity to the external drive.  Odd.

Hi gib

all is SOLVED

just ripped both of the "..." cds onto my external drive and all went well. all tracks visible

i noticed that the "sting" folder with the missing/hidden tracks that i ripped earlier is the same size as the "sting" folder of the visible/successful rip of the album

Thanks heaps for you spot on answer gib - you have saved me many many hours on this i reckon (before i would have probably noticed that both albums started with "..." and then in turn suss that out myself - it would have given me the absolute willies!!!)

and thanks to all others that have contributed to my question/dilemna

all solved in 24 hours
much appreciated
peter t

XLD ripped/extracted cd nowhere to be found

Reply #11
A bit off topic, but I just got a Samsung SE 208DB drive myself, just like the OP is using. Perhaps it can save others some time (and coasters) by giving the drive offsets I found: read: (+)6 , write: -6 samples.

Kees