Emplode erroneouslystating duplicate file

I recently purchased the unabriged audio version of "The Fellowship of the Ring" on CD.This was a 16 disk set with over 20 hours of audio. Anyway, after ripping it,(four hundred files), when I went to load it into the Empeg, Emplode responded that track 19 of disk 8 was a duplicate. This was not the case. I resolved the problem by make a few minor changes to the tag data for this track. Does anyone know why this occurred?

Thanks

I recently purchased the unabriged audio version of "The Fellowship of the Ring" on CD.This was a 16 disk set with over 20 hours of audio.

I don't have an answer to your question, but I would like to hear more about your CD set. Where did you get it, what did it cost? Is it a "reading" of the book(s), or is it a "performance" with different voices, sound effects, etc.?

tanstaafl.

If it's the same one I'm thinking of, it's a production of the trilogy made for BBC Radio. It's been available in bookstores in my area for ages, it seems.

If it's the same one I'm thinking of, it's a production of the trilogy made for BBC Radio. It's been available in bookstores in my area for ages, it seems.

No, I don't think so. I have that one, and it is a 13 CD set, about 10 files per CD. I recommend it highly, but to squeeze it into 13 hours, they had to leave things out (no mention of Tom Bombadil, for instance, and the battles at Isengard and at the Black Gate are all but ignored).

It is a production, as opposed to a reading.

tanstaafl.

I bought it at Barnes & Noble. It is a reading by Rob Inglis. This is the first book only. The others are available as well. The price as marked was 49.99 US but they charged me 29.99 US so it must be on sale. I also bought the dramatization but it wasn't what I was looking for so I took it back and bought this instead. I find that my mind does a far better job of dramatizing.

Does anyone know why this occurred?

Yes, the duplicate detection in emplode isn't that great. There's a couple of bugs about this in the internal bug database.

It'll get fixed eventually. In the meantime, just make small modifications to the tags.