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 found problems and bug list (Read 76966 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

XLD found problems and bug list

Please post your found problems and bug issues at this thread.

After reading this thread please check the XLD Master Thread List for other important XLD threads.

Guide lines for reporting problems or bugs in XLD on this thread.
  • Incude the version of XLD you used when the problem occured.
  • Include the system configuration:
    • (Computer used Power Mac, iMac, MacBook, etc.)
    • OS version (10.5.2, 10.5.4, and so on)
    • Specific architecture (PPC G4, PPC G5, Intel, etc.)
    • Drive model and firmware (if log is not posted)
    • Amount of system memory
  • An accurate description of how XLD's settings are fixed before the problem occurs.
  • A detail report of the undesired or incorrect result that is occurring when using XLD. 
  • Post any XLD logs that were produced during the problem situation when using XLD.

XLD found problems and bug list

Reply #1
Okay, I have a *slight* problem with XLD. I tried to encode a CD to AAC (settings True VBR, Max quality, no accurate bitrate information, no add gapless information for iTunes 7). The CD is ripped properly and encoded to m4a-files but when I try to play them in iTunes there's a problem: First track(track1) is played properly but the next one starts with the beginning of the track1, plays it for 10-15s and then starts another track(track2). If I try to play these songs separately (by clicking them), they all include a piece of track1 and after that the actual track that it's supposed to play...

I used version 20080921a (I think), the problem still persists with the newest version (which is at the moment 20080925).

Here's the logfile (if it helps or anything). I only ripped first two tracks this time:

Code: [Select]
X Lossless Decoder version 20080925 (93.2)

XLD extraction logfile from 2008-09-25 00:01:53 +0300

Conception / In Your Multitude

Used drive : MATSHITA DVD-R  UJ-835E (revision GAND)

Use cdparanoia mode : YES (CDParanoia III 10.2 engine)
Disable audio cache : OK for the drive with cache less than 2750KB
Make use of C2 pointers : NO
Read offset correction  : 0
Max retry count : 100

TOC of the extracted CD
Track |  Start  |  Length  | Start sector | End sector
---------------------------------------------------------
1  | 00:00:32 | 05:09:70 | 32 | 23276 
2  | 05:10:27 | 03:39:68 | 23277 | 39769 
3  | 08:50:20 | 03:12:00 | 39770 | 54169 
4  | 12:02:20 | 03:46:62 | 54170 | 71181 
5  | 15:49:07 | 02:57:15 | 71182 | 84471 
6  | 18:46:22 | 07:44:60 | 84472 |  119331 
7  | 26:31:07 | 04:35:08 | 119332 |  139964 
8  | 31:06:15 | 04:21:72 | 139965 |  159611 
9  | 35:28:12 | 03:56:40 | 159612 |  177351 
  10  | 39:24:52 | 06:39:18 | 177352 |  207294 

Track 01
Filename : /Users/Trikimees/Music/01 Conception - Under A Mourning Star.m4a

CRC32 hash : 4EDBD281
CRC32 hash (skip zero) : BF189EC7
Statistics
Read error   : 0
Skipped (treated as error)   : 0
Edge jitter error (maybe fixed)   : 0
Atom jitter error (maybe fixed)   : 0
Drift error (maybe fixed) : 0
Dropped bytes error (maybe fixed) : 0
Duplicated bytes error (maybe fixed) : 0

Track 02
Filename : /Users/Trikimees/Music/02 Conception - Missionary Man.m4a

CRC32 hash : 6D60D46C
CRC32 hash (skip zero) : 16E45CD0
Statistics
Read error   : 0
Skipped (treated as error)   : 0
Edge jitter error (maybe fixed)   : 0
Atom jitter error (maybe fixed)   : 0
Drift error (maybe fixed) : 0
Dropped bytes error (maybe fixed) : 0
Duplicated bytes error (maybe fixed) : 0

No errors occurred

End of status report
[!--sizeo:1--][span style=\"font-size:8pt;line-height:100%\"][!--/sizeo--]Moderation: Code changed to codebox.[/size]

XLD found problems and bug list

Reply #2
Did you rip the tracks individually or save as one file?  I just ripped 2 tracks as separate as files with  include pregrap.  I had accurate bitrate information, add gapless information for iTunes 7 both checked. Sorry misread your post I did the opposite of your settings. I  did not have any issues with the outputted files playing correctly in iTunes 8.0.


Code: [Select]
X Lossless Decoder version 20080925 (93.2)

XLD extraction logfile from 2008-09-24 17:44:27 -0400

Blues Traveler / Four

Used drive : SONY DVD RW DW-D150A (revision 1.MD)

Use cdparanoia mode    : YES (CDParanoia III 10.2 engine)
Disable audio cache    : OK for the drive with cache less than 2750KB
Make use of C2 pointers : YES
Read offset correction  : 48
Max retry count        : 100

TOC of the extracted CD
    Track |  Start  |  Length  | Start sector | End sector
    ---------------------------------------------------------
        1  | 00:00:32 | 04:40:03 |        32    |    21034 
        2  | 04:40:35 | 05:19:15 |    21035    |    44974 
        3  | 09:59:50 | 05:41:57 |    44975    |    70606 
        4  | 15:41:32 | 04:46:63 |    70607    |    92119 
        5  | 20:28:20 | 05:05:47 |    92120    |  115041 
        6  | 25:33:67 | 04:01:18 |    115042    |  133134 
        7  | 29:35:10 | 02:59:27 |    133135    |  146586 
        8  | 32:34:37 | 05:16:63 |    146587    |  170349 
        9  | 37:51:25 | 04:50:15 |    170350    |  192114 
      10  | 42:41:40 | 01:55:60 |    192115    |  200799 
      11  | 44:37:25 | 05:34:35 |    200800    |  225884 
      12  | 50:11:60 | 06:38:07 |    225885    |  255741 

List of alternate offset correction values
        #  | Absolute | Relative | Confidence
    ------------------------------------------
        1  |    89  |    41  |    50   
        2  |  2362  |  2314  |    48   
        3  |    85  |    37  |    36   
        4  |    59  |    11  |    18   
        5  |  -143  |  -191  |    16   
        6  |  1220  |  1172  |    10   
        7  |  2381  |  2333  |      9   
        8  |  1915  |  1867  |      8   
        9  |  1027  |    979  |      8   
        10  |  1313  |  1265  |      6   
        11  |    75  |    27  |      3   

Track 07
    Filename : /Users/macman4hire/Music/Blues Traveler/Four/MPEG-4 AAC/07 Crash & Burn.m4a

    CRC32 hash            : 3846F82B
    CRC32 hash (skip zero) : 2215C4FA
    AccurateRip signature  : E89CD3F9
        ->Accurately ripped! (confidence 110)
    Statistics
        Read error                          : 0
        Skipped (treated as error)          : 0
        Edge jitter error (maybe fixed)      : 0
        Atom jitter error (maybe fixed)      : 0
        Drift error (maybe fixed)            : 0
        Dropped bytes error (maybe fixed)    : 0
        Duplicated bytes error (maybe fixed) : 0
        Inconsistency in error sectors      : 0

Track 10
    Filename : /Users/macman4hire/Music/Blues Traveler/Four/MPEG-4 AAC/10 The Good, The Bad, And The Ugly.m4a

    CRC32 hash            : E6B0BE50
    CRC32 hash (skip zero) : FA738070
    AccurateRip signature  : 1434A565
        ->Accurately ripped! (confidence 111)
    Statistics
        Read error                          : 0
        Skipped (treated as error)          : 0
        Edge jitter error (maybe fixed)      : 0
        Atom jitter error (maybe fixed)      : 0
        Drift error (maybe fixed)            : 0
        Dropped bytes error (maybe fixed)    : 0
        Duplicated bytes error (maybe fixed) : 0
        Inconsistency in error sectors      : 0

No errors occurred

End of status report
Edit: Just ripped to the same two tracks with no accurate bitrate information, no add gapless information for iTunes 7 and both play fine in iTunes 8.0.  Sorry don't know whats going with your rips.  Try a different CD and see what happens!

XLD found problems and bug list

Reply #3
I believe it would really help if those posting in this thread provided some information about  the system they are using. I have found (and tmkk has fixed) a couple of PPC-specific bugs in XLD.

With that in mind, I think it would be beneficial to mention:

1. Computer used (Power Mac, iMac, MacBook, etc.)

2. OS version (10.5.2, 10.5.4, and so on)

3. Specific architecture (PPC G4, PPC G5, Intel, etc.)

4. Drive model and firmware (if log is not posted)

This will help zero in on any problems. Thanks.

XLD found problems and bug list

Reply #4
Did you rip the tracks individually or save as one file?  I just ripped 2 tracks as separate as files with  include pregrap.  I had accurate bitrate information, add gapless information for iTunes 7 both checked. Sorry misread your post I did the opposite of your settings. I  did not have any issues with the outputted files playing correctly in iTunes 8.0.

I ripped them individually with pregap and without pregap. I had accurate bitrate information and gapless information for iTunes 7 both checked. I also ripped the same CD (individually) with and without pregap and both accurate bitrate information and gapless information for iTunes 7 *unchecked*.

So in total I made four different rips and the problem persisted. I had no problems whatsoever when I ripped the cd with iTunes 8.

As requested, here's my system:

Mac PowerPC G4, Mac OS 10.4.11 (Tiger); MATSHITA DVD-R  UJ-835E (revision GAND).

***Edit: I tested another cd: no change.***

Code: [Select]
X Lossless Decoder version 20080925 (93.2)

XLD extraction logfile from 2008-09-25 10:01:11 +0300

Yann Tiersen / Tabarly

Used drive : MATSHITA DVD-R  UJ-835E (revision GAND)

Use cdparanoia mode    : YES (CDParanoia III 10.2 engine)
Disable audio cache    : OK for the drive with cache less than 2750KB
Make use of C2 pointers : NO
Read offset correction  : 0
Max retry count        : 100

TOC of the extracted CD
    Track |  Start  |  Length  | Start sector | End sector
    ---------------------------------------------------------
        1  | 00:00:00 | 03:05:05 |        0    |    13879 
        2  | 03:05:05 | 03:38:08 |    13880    |    30237 
        3  | 06:43:13 | 01:14:65 |    30238    |    35852 
        4  | 07:58:03 | 03:33:72 |    35853    |    51899 
        5  | 11:32:00 | 00:55:63 |    51900    |    56087 
        6  | 12:27:63 | 02:14:35 |    56088    |    66172 
        7  | 14:42:23 | 01:12:50 |    66173    |    71622 
        8  | 15:54:73 | 02:19:45 |    71623    |    82092 
        9  | 18:14:43 | 02:38:20 |    82093    |    93962 
      10  | 20:52:63 | 01:18:37 |    93963    |    99849 
      11  | 22:11:25 | 02:45:30 |    99850    |  112254 
      12  | 24:56:55 | 03:37:53 |    112255    |  128582 
      13  | 28:34:33 | 01:32:07 |    128583    |  135489 
      14  | 30:06:40 | 02:38:03 |    135490    |  147342 
      15  | 32:44:43 | 01:07:10 |    147343    |  152377 

Track 01
    Filename : /Users/Trikimees/Music/01 Yann Tiersen - Tabarly.m4a

    CRC32 hash            : 6BD0FA61
    CRC32 hash (skip zero) : 7D58BD1B
    AccurateRip signature  : 09B2245C
        ->Track not present in AccurateRip database.
    Statistics
        Read error                          : 0
        Skipped (treated as error)          : 0
        Edge jitter error (maybe fixed)      : 0
        Atom jitter error (maybe fixed)      : 0
        Drift error (maybe fixed)            : 0
        Dropped bytes error (maybe fixed)    : 0
        Duplicated bytes error (maybe fixed) : 0

Track 02
    Filename : /Users/Trikimees/Music/02 Yann Tiersen - Naval.m4a

    CRC32 hash            : 1AAD21DF
    CRC32 hash (skip zero) : 92B869B6
    AccurateRip signature  : 3C7F64C3
        ->Track not present in AccurateRip database.
    Statistics
        Read error                          : 0
        Skipped (treated as error)          : 0
        Edge jitter error (maybe fixed)      : 0
        Atom jitter error (maybe fixed)      : 0
        Drift error (maybe fixed)            : 0
        Dropped bytes error (maybe fixed)    : 0
        Duplicated bytes error (maybe fixed) : 0

No errors occurred

End of status report
.

XLD found problems and bug list

Reply #5
Esanssi from the information displayed by you I don't think its the way you have XLD setup.  I hope someone with a similar system configuration will try to duplicate the same problem.  If another user with a similar system configuration does obtain the same result, then we will be able to report the problem with this useful information to developer and let him concentrate on programming instead of testing.  Sorry nothing has helped so far!

XLD found problems and bug list

Reply #6
I believe it would really help if those posting in this thread provided some information about  the system they are using. I have found (and tmkk has fixed) a couple of PPC-specific bugs in XLD.

Pepzhez I added a guide lines for reporting problems and bugs to the 1st post of this thread.  Hopefully this will inform all new posters of this thread what information is necessary for other HA members to hopefully find a solution their problem.

XLD found problems and bug list

Reply #7
I've noticed an issue during format conversion that I believe it XLD related and not user related ... although I'm happy to be corrected!

It looks like XLD does not respect the "Format of filename" setting when converting from one format to another, it only outputs converted files to the output directory setting. For example,

[blockquote]Output Directory: /Volumes/library/music/xld
Format of filename: %f/%a/%T/%n. %t
Formats: FLAC, AAC[/blockquote]

Output therefore looks like:

[blockquote]/Volumes/library/music/xld/FLAC/<artist>/<AlbumTitle>/etc.
/Volumes/library/music/xld/MPEG-4 AAC/<artist>/<AlbumTitle>/etc.[/blockquote]

When converting a file, e.g. from FLAC to Ogg Vorbis, the converted file is output to the output directory only. I'm losing all of the filename formatting and consequent structure. Mass conversion is not usable at this time.

XLD found problems and bug list

Reply #8
mookr I do know that there is an issue when you rip a CD and try to output two formats simultaneously.  XLD will not let you choose to output Save as a single file(+cue) for one of the choosen formats and to select Include pregap in the end of the previous track or Exclude pregap for the other output (which output separate track files).  The developer is aware of this.  You can only pick one output type when ripping!

I think my work flow may solve some of the problems you seem to be having.

This is my current work flow with XLD:

1. I choose FLAC and I rip the CD Save as a single file(+cue) the Output directory: to Specify User/macman4hire/Music, the Format of filename: to Specify %A/%T/%f/%T  The following outputted structure 1st Arist 2nd Album 3rd Format 4th the file saved with correct Album Title is saved in my Music folder.

2.I next open the newly created FLAC file from the freshly ripped CD and select MPEG-4 AAC for my next format(note you can select Multiple Formats if your desire more than one format) and change the Format of filename: to Specify %A/%T/%f/%n %t  next I hit Decode and the output is place in the existing 1st Arist 2nd Album folders with newly created format folder which is reads MPEG-4 AAC , inside the new format folder are the separate tracks with the track number first and the correct track title.

I tried using the Multiple Formats selection with MPEG-4 AAC, LAME and OGG without any issues.  This seems to work for me.  I hope this was useful.

 

XLD found problems and bug list

Reply #9
...
I tried using the Multiple Formats selection with MPEG-4 AAC, LAME and OGG without any issues.  This seems to work for me.  I hope this was useful.


Hi macman4hire - I'm successfully ripping to multiple formats, no problem there (and I'm ripping to individual files, not cue sheet). The problem I'm experiencing is when I want to convert already ripped files to a different format. For example, I have an already ripped FLAC file I want to convert to AIFF or Ogg Vorbis. The conversion output is not respecting the filename format setting - the converted file will be placed into the output directory only, ignoring any filename format structure that would otherwise have put the file in the correct place. Or am I missing something in what I'm doing that would otherwise correct this behavior?

XLD found problems and bug list

Reply #10
The other small issue I've found recently was with the logging. Log files now go in the directory of the album, but only if the file is in the AR db (I *think*). Now, I've not tested to determine whether AR settings in preferences have any impact on this, but I've noticed that two albums that were *not* in AR have their log files in the output directory and not with the album. I've got "Test and Copy" set if the album is not in AR; "Query AR db to check integrity" is also set, but "Treat AR mismatch as inconsistency" is not set.

Example albums:

Nick Cave and the Bad Seeds: Abattoir Blues
California Guitar Trio:  Whitewater

Edit: Updated with example albums

XLD found problems and bug list

Reply #11
The FLAC file you already have ripped how did save it Single cue+, Include pregap, Exclude pregap?  If you are using individual FLAC files XLD will out the file to the Output directory and not into the Format of filename structure.  Unfortunately XLD does not recognize cue for multiple file yet!  This why rip to a Single(+cue) file.

XLD found problems and bug list

Reply #12
.. If you are using individual FLAC files XLD will out the file to the Output directory and not into the Format of filename structure ...


Yes, that's what I'm experiencing. I'm ripping in multiple formats (FLAC and AAC) to single files with pregap included. Occasionally I want to transcode and would like to see the transcoding respect the output filename convention as well. Currently, outputting files to the output directory doesn't make it that useful to me. If I want to mass-transcode, I'm left with a lot of structural tidying up to do!

XLD found problems and bug list

Reply #13
I will send this info along to the developer tmkk.  Sorry it took so long to isolate the problem.

XLD found problems and bug list

Reply #14
No problem - it hardly took long, but I'm not measuring in "tmkk minutes"! Thank you for collating all the info (and raising the feature request - thanks!).

XLD found problems and bug list

Reply #15
I think my problem (look above) is somehow related to the way the XLD rips the cd's. Today I used this method and everything worked as it should (songs played properly etc.):

well, just to throw it out there, here's the process I use to encode my CD's to AAC (it works like a charm with my 2G iPod Touch), assuming both Max and XLD are installed-

- rip/encode CD to FLAC using Max (paranoia enabled, etc.)
- navigate to the folder containing the FLAC files, select all/right click, and choose "Open with XLD"

XLD found problems and bug list

Reply #16
An oddity noticed with the current release of XLD with multi-session disks and the use of GraceNote CDDB (iTunes open): after pregap analysis, the track listing is not displayed per the iTunes listing - no values are reported so you have to update via FreeDB or MusicBrainz (or whatever is available). This does not happen with single session CDs. Also, it's not possible for force a re-read via GraceNote (I'll put that in as a feature request).

XLD found problems and bug list

Reply #17
I have a badly scratched CD that XLD consistently hangs on.  Most of my disks rip within a half hour, but I left this one overnight (8 hours) and came back and found it not making any progress.  XLD was able to quit cleanly, but the "cancel" button did nothing for several minutes.  I was able to get a log at one point with dozens of suspicious sectors; unfortunately I don't have it on me...  I've been overwriting the files every time.

Machine: Macbook
OS: 10.5.5
Processor: Intel Core 2 Duo 2.4 GHz
Drive: HL-DT-ST DVDRW GSA-S10N Revision BP10 ("Superdrive") (Caches 36kb)
Memory: 2 Gb

XLD settings:
Convert to FLAC w/ embedded cue sheet
cdparanoia mode
No C2 pointers (does this drive support it? I'm guessing no)
Retry count: tried 100 and 50
Offset correction: 667 (set automatically)
AccurateRip query activated (the disk isn't in accuraterip anyway)
Automatically save log when ripping to single file + cue
Verify suspicious sectors
Don't test before copy (see below)
Don't scan ReplayGain

Anyway, I'm trying it again now with a max retry of 20 and no suspicious sector verification.  I'm not that "paranoid" about this one since it's technically a Taiwanese bootleg anyway (that was a nasty surprise when I found out), I just want to get as much quality out of it as possible.  So since I'm not getting any data with verification on, let's see if that helps.  Would the old cdparanoia engine help here?

Ok, good, the time remaining is now in the low thousands... seems like it's working better so far :/

XLD found problems and bug list

Reply #18
The key phrase is badly scratched CD, that  is the reason for the hang up in XLD.  I have been using XLD for sometime now and find it will on occasion hang up when ripping a badly scratched CD. It will hang up at the same location during a 2nd attempt at ripping.  If you have another drive you want to try ripping the CD on that drive.  Certain CD's rip well on one drive and not on the other!  What you can do is uncheck to the CD Paranoia box and attempt a rip using the burst mode.  I would still use AccurateRip to verify the tracks.  For me on several occasions  the problem was only on one track and all the other tracks were verified using Accurate.  I then would listen to the track that was not verified by AccurateRip for any readily apparent audio distortion.  If I can not detect any audio distortion on the non verified track, I will then put it to bed.  I will not repurchase a CD for one or two tracks that I can not detect any audio distortion on.  Another solution would be to try ripping the CD with EAC if you have Windows on your Mac.  EAC will work under Boot Camp, VMware Fusion and Parallels.

Good Luck,
macman4hire

XLD found problems and bug list

Reply #19
The key phrase is badly scratched CD, that  is the reason for the hang up in XLD.  I have been using XLD for sometime now and find it will on occasion hang up when ripping a badly scratched CD. It will hang up at the same location during a 2nd attempt at ripping.  If you have another drive you want to try ripping the CD on that drive.  Certain CD's rip well on one drive and not on the other!  What you can do is uncheck to the CD Paranoia box and attempt a rip using the burst mode.  I would still use AccurateRip to verify the tracks.  For me on several occasions  the problem was only on one track and all the other tracks were verified using Accurate.  I then would listen to the track that was not verified by AccurateRip for any readily apparent audio distortion.  If I can not detect any audio distortion on the non verified track, I will then put it to bed.  I will not repurchase a CD for one or two tracks that I can not detect any audio distortion on.  Another solution would be to try ripping the CD with EAC if you have Windows on your Mac.  EAC will work under Boot Camp, VMware Fusion and Parallels.

Good Luck,
macman4hire


I'm afraid AccurateRip is a no go since the disk isn't listed (I'm sure the bootleg part doesn't help with that).  I don't have any other drives either, and though I can get a discounted copy of Windows I oppose that on principle 

That said, I would consider burst mode a last resort.  There's got to be a way around this...

A few options:

1. I have Max installed as well; I can just use the comparison ripper on that.  Problem is, cdparanoia reports that my drive caches 36kb... doesn't that render the comparison ripper useless?  Also, I really like embedded .cue sheets.  But I can always rip to a separate .cue and convert again with XLD... awkward but effective, assuming the comparison ripper works on caching drives.

2. There's a Darwin port for command-line cdparanoia, but it hasn't been updated since 2006... supposedly.  How exactly is XLD using a Linux ripper anyway?  Does tmkk have a Darwin port lying around, and would he be willing to distribute it seperately from the GUI?  I understand XLD has a command line interface, but it doesn't mention cdparanoia (or any ripping capability for that matter) anywhere in the documentation.  Then again, Darwin's UNIX-based... is it possible for me to download the cdparanoia source and compile it on my Mac?  I'm not exactly an experienced programmer; my only training is in Java, so this cross-platform stuff isn't really in my playbook.

Any suggestions, or is burst mode and crossed fingers my best bet?  To tell you the truth, I actually have in my possession an old FLAC of this disk from a copy of EAC I had on my old PC... but all these errors are making me question its integrity, especially since I recall EAC generating some pretty bizarre .cue files for that rip (multi-minute pregaps and other strange things).  Fortunately I had daemon-tools and didn't have to worry about pregap for individual track conversions (at least I think that's how I ended up with decipherable files, either that or I ripped them directly).

Not that it matters much (bootleg specter again), but well... you know... once this kind of thing pops up, you have to nip it in the bud or computers will think they can do whatever they want with our data.  They're plotting something big, I'm tellin' ya...  Seriously, at this point I just want to see it through and get this data if it kills me.  What's the best course of action?

XLD found problems and bug list

Reply #20
XLD uses cdparanoia 10.2 via libcdio. No, tmkk does not have a ported version of the command line 10.2, sadly.

I think your best bet would be to use the extant command line cdpanoia III 9.8 OS X port, slowing down the drive to 1x speed. I've actually had good luck salvaging certain tracks via this method.

It's available through Fink and Macports. You can also Google around for a standalone installation. Your drive caches far less than 300KB worth of audio, so using 9.8 won't be a problem for you.

No one has yet ported the command line cdparanoia III 10.2 to OS X. Sadly, no one seems very interested in creating one either. I attempted to do a simple update of the cdparanoia engine with the old port, but couldn't get it to work properly. You can compile cdparanoia 10.2, but you'll still need a hardware interface in order to use it on OS X. An all new cdparanoia OS X port is definitely needed. It probably wouldn't be all that difficult to make one using libcdio (which didn't exist when the original cdparanoia OS X port was made).

XLD found problems and bug list

Reply #21
Seriously, at this point I just want to see it through and get this data if it kills me.  What's the best course of action?


Have you tried repairing the scratch?

I just use a big slowdown in ripping speed as my cue to take out the CD and spend a few minutes on repairing the disk. Beats waiting hours for a rip that will only most likely come out with problems anyway.


XLD found problems and bug list

Reply #23
The text posted below and highlighted was from a specific iTunes/Mac question.  I did not post it in this thread initially because I did not want to limit the responses from just XLD users.  I am sure one of XLD users would have the answer but was wanting an immediate response.  Anyway  Pepzhez had the answer to my question.  The reason I posted question below in the first place was to test a potential workaround for a problem I was having with XLD.

XLD Version 20080926 (93.3)
Mac Pro Model Identifier: MacPro1,1
Tiger 10.4.11 OS
Intel architecture
Sony DVD RW DW-D150A with the following firmware: 1.MD
1 Gig of Memory

Does any know how to clear the audio CD history on Mac? I want to clear the cache of all opened audio CD's. When you open a CD with iTunes and search Gracenote for the CD info it is cached some where so the next time you insert the CD it will display the title. I currently have a problem with a new CD coming up as previously played CD when using XLD. XLD displays the incorrect CD info and creates a cue sheet for the wrong CD. I think it is title issue because this the second time it has occurred with the title "The Greatest Hits". I don't really care about maintaining this cache. Be advised I removed the XLD and iTunes cache and the incorrect title is still displayed instead of just" Audio CD". So if I could clear the cache I think that I will not have this problem when using XLD.

Work around to XLD displaying incorrectect CD title info

XLD found problems and bug list

Reply #24
garden,

1. How does the CD playback in a stand alone CD/DVD player?
2. How does the CD playback in your computers drive?

The reason I asked you the above posted questions is that if you hear less audio distortion when playing the CD on either of the stand alone CD/DVD player or your computers drive than the ripped version you have other options. Players have error correction that can do a decent on guessing what information should be on an audio disc. You can leverage this correction capability to your benefit. Depending on which player yields the best playback result over the ripped version you may have the following options.

1. A..If the stand alone CD/DVD player plays back the CD the best you can use an optical or coaxial connection from the stand alone player and connect it to your computer to record the digital signal using the error correction of the stand alone player. Note this option is the preferred option over B. because it leaves everything in the digital domain. On the Mac there is a an application called Disk Doctor that facilitates this.
B.If the stand alone CD/DVD player plays back best you can use the analog rca outputs and hook it up to your computer analog rca inputs if you have them. Disk Doctor again will work here.

2. If the computer drive plays back the CD the best over the ripped version you can record the analog signal from the sound card to a digital file. On the Mac there is an application called Audio Hijack that facilitates this. Note option 1 A is still preferred unless the playback result on the stand alone player is less than the computers drive.

Before anyone chastises me about that fact it is better to keep things in the digital domain note I would rather have the ability to archive a deteriorating CD before it is to late to a decent sounding digital file. This circumstance warrants leaving the completely digital ideal.