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 Requested Features List (Read 204561 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

XLD Requested Features List

Reply #125 –
I didn't say it was an uncorrectable error. It isn't.

See my post above. I identified the problem. It will be fixed.

XLD Requested Features List

Reply #126 –
Quote from: knucklehead on
Quote from: Pepzhez on


Forget about the AccurateRip result for a moment.


Wouldn't this tend to confuse most users a bit more than the existence of the "use old CDParanoia engine" checkbox?


Not if they can read and understand the options in the preference panel. XLD gives you the choice to use "Treat AccurateRip mismatch as an inconsistency in the log," if you want to use that. I don't care at all for this option because the log becomes even more confusing. You then have to check if the "inconsistencies" are AR mismatches or sector inconsistencies.

Without that option checked, XLD reports similarly to the way the EAC log does. The actual ripping results are what counts, and a log shouldn't be telling you that errors or "inconsistencies" occurred in the actual rip if they did not in fact occur.

Besides, most discs don't even exist in the AR database, so you can't always rely on AR to be your guide.

XLD Requested Features List

Reply #127 –
Hi,

I've been using XLD for the past week or so and discovered this forum along the way. Let me first say I'm very pleased with the rips I'm getting from XLD. However, I'm noticing a consistent problem with CDs that also contain a data - the last audio track appears to be padded (times are extended) and will always hang toward the end of the rip. This will occur whether pregap is included or excluded. Max can rip these tracks, however, and does not appear to pad out the track time. I'm not technical enough to understand what's happening here, but it is consistent and is the only issue I've found to date with XLD ripping.

Example CDs that this has occurred with:

- Fiona Apple, When The Pawn, Track 10: "I Know"
- Auf der Maur, Auf der Maur, Track 12: "I Need, I Want, I Will"

Has anyone else experienced this and found a solution/workaround?

I understand this is a feature request thread, so can I request a feature that enables XLD to rip final audio tracks on CDs that also include a data track :-) I didn't want to bombard XLD's author with seemingly random user emails but also could not find anywhere to log possible issues.

Another CD that XLD did not like is "Songs For The Deaf", Queens Of The Stone Age. It has a hidden pregap track of ~1'30" to track 1 (HTOA?) and XLD goes into a hanging state when trying to rip track 1 with pregap included or excluded in the options. Not related entirely and possibly hardware based, I know, but other CDs with small pregaps on track 1 rip okay with XLD. Max rips track 1 and ignores the pregap track. Ideally, I'd love to see XLD rip track 1 with the hidden track, but a successful track 1 rip would be a good too.

One feature request that does come to mind is the ability to specify output folder name values for the formats that you rip. For example, I'm using multiple outputs at present and would like my folders to be "flac" and "aac". At present they are "FLAC" and "MPEG-4 ACC", based on the rip format (%f). Customization of these values would be useful in this context. Not exactly top priority, but a "nice to have".

Thanks.

XLD Requested Features List

Reply #128 –
Quote from: macman4hire on
Previous versions of XLD didn't, but would it be possible to copy over ALL tags when transcoding from one format to another? Even non-standard ones?...Or at least the tags that iTunes can/will append to files it recognises (e.g. ALBUMSORTORDER, ITUNESCOMPILATION, etc.)
ALL is impossible, because the way to store the entry of metadata item in MP4 metadata and ID3 tag (4 bytes binary) differs from the way in ape tag and vorbiscomment (unlimited(?) length text). If you want me to do this, please list the all tags that should be supported by XLD.
Quote from tmkk XLD developer

Hoo boy. Well, correct me if I'm mistaken, but doesn't foobar copy over all tags? I know I've converted from FLAC/WavPack to AAC and MP3, and all my tags (including non-standard ones) were copied over. 

I suppose my "must-haves" would be:

ALBUM
ALBUMSORTORDER
ARTIST
ARTISTSORTORDER
BAND
COMPOSER
DISCNUMBER
GENRE
ITUNESCOMPILATION
TITLE
TOTALDISCS
TOTALTRACKS
TRACK
TRACKSORTORDER
YEAR

I'd imagine that other people have their own "must-haves" as well... I'm just thinking of the iTunes specific ones.

XLD Requested Features List

Reply #129 –
The format chosen should be displayed SOMEwhere other than in the preference pane so that accidental encodes aren't done (and time isn't wasted... and yes, I realise it was my own fault... but 2 CDs later... not so impressed).

XLD Requested Features List

Reply #130 –
Quote from: mookr on
Has anyone else experienced this and found a solution/workaround?


Yes, I've experienced this. This is definitely a problem with XLD. It's impossible to rip the last track of any CD that contains a data track at the end.

XLD Requested Features List

Reply #131 –
Quote from: Pepzhez on
Yes, I've experienced this. This is definitely a problem with XLD. It's impossible to rip the last track of any CD that contains a data track at the end.

Ahh... that would explain why those two CDs won't rip entirely.

Bugger.

XLD Requested Features List

Reply #132 –
Quote from: ozmosis82 on
The format chosen should be displayed SOMEwhere other than in the preference pane so that accidental encodes aren't done (and time isn't wasted... and yes, I realise it was my own fault... but 2 CDs later... not so impressed).

What about placing the format section drop down menu in XLD's main application window(the window with decode button).

XLD Requested Features List

Reply #133 –
For the past several years, the OS X port of cdparanoia III 9.8 does have a method for properly ripping the last track of a multi-session CD. (This is why xACT can do it as well, as it uses this very port.)

From the README.OSX file:

Quote
Multi-session CDs are now properly supported (OS X only, though the change could be easily applied to the Linux code as well). Previously, cdparanoia would treat the end of the last track of one session as being the same as the start of the next session, which caused the inter-session gap to be included.  This gap lasts about two minutes, and gets read errors (and sometimes nasty noise) near the end. Now, it checks the session lead-out to determine the end of the last track of each session.

XLD Requested Features List

Reply #134 –
Quote from: macman4hire on
Quote from: ozmosis82 on

The format chosen should be displayed SOMEwhere other than in the preference pane so that accidental encodes aren't done (and time isn't wasted... and yes, I realise it was my own fault... but 2 CDs later... not so impressed).

What about placing the format section drop down menu in XLD's main application window(the window with decode button).

I was going to suggest adding the extension of the format being created in the "Progress" window (since it displays the rest of the output filename), but that's a much better idea! It would be a much more convenient place for it to be.

XLD Requested Features List

Reply #135 –
Quote
Besides, most discs don't even exist in the AR database,


I don't believe this to be a true statement, most discs are in AR, there is a % which are not, I would guess < 5%

XLD Requested Features List

Reply #136 –
I'm not trying to argue with you or to dismiss AR, but how in the world do you arrive at the < 5% figure? It's my experience that the vast majority of discs in my collection are not in the AccurateRip databse. Granted, my tastes run towards the obscure, but it's rare to find a lot of well-regarded jazz improv albums or 20th century composers of some renown (Stockhausen, for one) in AR.

There is also a vast world of quite famous Latin American, Indian, Middle Eastern and Asian popular music that rather surprisingly seems barely represented at all in the database.

This isn't meant as a criticism. I realize that this is solely a matter of people not submitting the results, certainly, but if you consider the sheer amount of recorded music available throughout the world, I honestly wouldn't be surprised if even 5% of all CDs ever released are in the AR database.

Perhaps in a few more years, though. 

Sorry to stray so far off topic.

XLD Requested Features List

Reply #137 –
Quote from: macman4hire on
If you have compliant cue sheet that is correctly associated with the MP3 file XLD will allow you to convert it into another format. 

are they 'losslessly' split or are they re-encoded??
No. Unless you convert the file you want to split into a lossless format.  Be advised you will never be able to reconstruct the original MP3 that has been encoded but if you choose a lossless format it will preserve what you have left of the original MP3 you wish split thus being closer to the source file.

thanks for the reply. I'm looking to get everything I have currently on JR MC12 / windows (cue+mp3/flac) into itunes+mac (mp3 + alac).

XLD will help splitting flacs into alacs but for splitting mp3 without loosing quality I only know musiccutter (would be a lot of work and doesn't run on MAC). the other option is splitting mp3's into alacs which would be incredibly inefficient (storage-wise).

why don't more apps do the same as musiccutter and split mp3 without reencoding? any app on mac does this?

sorry if this is getting a bit offtpic

thanks!!

XLD Requested Features List

Reply #138 –
Quote from: spoon on
Quote
Besides, most discs don't even exist in the AR database,


I don't believe this to be a true statement, most discs are in AR, there is a % which are not, I would guess < 5%


Yeah right... 

XLD Requested Features List

Reply #139 –
Quote from: macman4hire on
neovibe asked for a for a lossless solution using XLD.  The key word here is re-encodes. I gave a solution using XLD's current capabilities as asked.  The solutions that everybody has given neovibe  are great and simply rewrites the file with out re-encoding(transcoding,converting) the MP3file.  These applications split(slices) the existing MP3 file into several segments which then become individual tracks with no changes to audio signal other than splits including the new metadata.  These applications mentioned simple automates the process.  I think this should  be a feature to eventually be incorporated into XLD if any of these applications source is available for use.  tmkk stated XLD is an audio converter and we the users have placed the emphasis on the ripping portion of XLD here of late.

I must be very tired because the way this forum works (the software) is pretty strange at first, so my last reply was before reading all the answers.

So, ok, for mac there's fission and maybe pcutmp3 (will try to find a link via google) and for windows musiccutter. as far as I've researched these are the only apps that will get this right.

I know it's not a priority but would be very nice if xld could do all of this.

thanks for your help everyone

XLD Requested Features List

Reply #140 –
Quote from: Pepzhez on
Not if they can read and understand the options in the preference panel. XLD gives you the choice to use "Treat AccurateRip mismatch as an inconsistency in the log," if you want to use that. I don't care at all for this option because the log becomes even more confusing. You then have to check if the "inconsistencies" are AR mismatches or sector inconsistencies.

Without that option checked, XLD reports similarly to the way the EAC log does. The actual ripping results are what counts, and a log shouldn't be telling you that errors or "inconsistencies" occurred in the actual rip if they did not in fact occur.

Besides, most discs don't even exist in the AR database, so you can't always rely on AR to be your guide.

I misread your post on the "uncorrectable" part. It makes sense now.

I'm trying some perfect condition CDs now, and 10.2 paranoia does seem to be producing the same errors as I've been getting with the slightly scratched CD that I've been using up to now. Not audible, but enough to mess up the AR report. All I've looked at so far are nearly identical blips at just before the end of the track.

For other feature issues ---

The offset listings don't don't show up if you start the program without the external drive on. If you turn on the drive you need to restart the program to get the offsets to show up, which is a bit inconvenient.

A BIG one - A good help file!
For anyone who hasn't used PC ripping programs, and is coming from using MAX, all the new things like usable logs, T+C, AR, etc, is a bit of an adjustment trying to come up with an efficient workflow.

XLD Requested Features List

Reply #141 –
I spoke with tmkk about creating a Users Guide that would be included in XLD's down load.  This not a simple task and will take some to complete a comprehensive Users Guide.  I have created a lay out design and a preliminary content outline.  I do not have an estimated time of completion at the moment.

XLD Requested Features List

Reply #142 –
New XLD Version 20080921 released today with following features and corrections.

Fixed some issues with the new cdparanoia engine
Fixed a problem when ripping Mixed Mode CD/Enhanced CD
Removed redundancy of the cue sheet generated by XLD
Offset correction value is now set automatically when opening

XLD Requested Features List

Reply #143 –
Quote from: knucklehead on
I'm trying some perfect condition CDs now, and 10.2 paranoia does seem to be producing the same errors as I've been getting with the slightly scratched CD that I've been using up to now. Not audible, but enough to mess up the AR report. All I've looked at so far are nearly identical blips at just before the end of the track.


Update to 20080921 and try it now. I just tested this, and the issue has been resolved. !0.2 in secure test and copy mode is now working correctly. No more CRC mismatches.

He also fixed the enhanced CD issue. Works perfectly now!

Once again, very impressive support.

Thanks, tmkk!

XLD Requested Features List

Reply #144 –
Quote
I'm not trying to argue with you or to dismiss AR, but how in the world do you arrive at the < 5% figure?


It was a guess, how in the world did you come up with your 51% or more discs not in the database (world wide releases)? Would you also say that most discs are not in freedb or Musicbrainz? (for those 2 someone has to type the track names and submit, AccurateRip is pretty much automatic).

XLD Requested Features List

Reply #145 –
Quote from: spoon on
It was a guess, how in the world did you come up with your 51% or more discs not in the database (world wide releases)? Would you also say that most discs are not in freedb or Musicbrainz? (for those 2 someone has to type the track names and submit, AccurateRip is pretty much automatic).


I would say that there are many discs that are not in freedb or Musicbrainz. What's the percentage? I have no idea. They do however contain a great deal of the popular Turkish and African pop that never seem to give any AR results.

If one is dealing mainly with Anglo-American rock/pop of the less underground persuasion, it may indeed be a safe bet that AR does cover 95% of that particular field. I am sure that all 12,000 offset variations of Dark Side of the Moon are there. Other things? Considerably less so. You'd be hard pressed to find many Derek Bailey or Cecil Taylor discs in AR. (Or around half of the Can or T.Rex discography, I noticed last week; those are not exactly ultra-obscure non-rock artists either.)

That's not a flaw with AccurateRip. Such stats merely reflect the relative ubiquity of what is popular amongst the vast majority of the AR user base. The same can be said of freedb and Musicbrainz.

Perhaps there exists a localized Chinese CD database that flips these demographics considerably. (I don't know if there really is one, but if one does exist, I believe its database would reflect rather different preferences.)

However, I didn't bring this subject up to argue about AR. It came up because I was pointing out that a ripping log shouldn't list the lack of an AR result as an error or "inconsistency," that's all.

I actually quite like AccurateRip. If only I were able to submit results with XLD, I could add quite a few titles to the database, you know.

XLD Requested Features List

Reply #146 –
Quote
Update to 20080921 ... fixed the enhanced CD issue. Works perfectly now!

Once again, very impressive support.

Thanks, tmkk!


Agreed. Just updated and all prior multi-session rip problems appear to be resolved. Excellent support turnaround. Still can't rip track 1 of "Songs For The Deaf" that has htoa, so hoping that will happen in a future release too.

Thanks tmkk - great stuff.

XLD Requested Features List

Reply #147 –
Quote from: mookr on
Agreed. Just updated and all prior multi-session rip problems appear to be resolved. Excellent support turnaround. Still can't rip track 1 of "Songs For The Deaf" that has htoa, so hoping that will happen in a future release too.

Thanks tmkk - great stuff.
I can rip the hidden track 0 of "Songs for the Deaf" fine so I think it has sth. to do with the capabilities of your drive.

XLD Requested Features List

Reply #148 –
This new option to use C2 error pointers seems really interesting.  I will try a new rip using this feature to see what happens.  tmkk is pushing the envelope once again with new features!  Thanks tmkk you really have taken Mac users to another level in  digital audio management!

Version 20080921a:

    * Added option to use C2 error pointers
    * When the option is turned on, XLD first read a sector in burst mode, and check the occurrence of C2 error. If C2 error occurs, then XLD re-read the sector with cdparanoia. This accelerates ripping extremely for the drive with C2 error support (Plextor, NEC, etc), without losing safety. If you use this option, please make sure that your drive supports reporting C2 errors. Modified wavpack encoder to store MD5 checksum by default
    * Added option to prevent XLD from setting offset correction value automatically
 

XLD Requested Features List

Reply #149 –
Firstly, can we rely on EAC to determine the C2 reporting ability of a drive and secondly, this latest version is providing:
Code: [Select]
X Lossless Decoder version 20080921a (93.0)

XLD extraction logfile from 2008-09-21 13:48:59 +0100

The White Stripes / De Stijl

Used drive : MATSHITA DVD-R   UJ-867 (revision HA13)

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  : 102
Max retry count         : 100
-------------------------------
snipped
-------------------------------

List of alternate offset correction values
        #  | Absolute | Relative | Confidence 
    ------------------------------------------
        1  |   -565   |   -667   |     31     
        2  |  -1244   |  -1346   |     20     
        3  |   -562   |   -664   |      8

These three alternate offset correction values have not appeared before and, AFAIK, are completely incorrect.