The CD is a 15 track CD. All my other CDs are fewer than 15 tracks, and they don't have this problem (all tracks keep their names). Since I don't have any other 15+ track CDs to test with, I can't confirm if it will do this for track 15 or for the last track for CDs with 15+ tracks.

I tested this in R14. The audio CDs all had more than 15 tracks.

Without the CDDB lookup, the tracks are labeled generically as Track 01, Track 02, Track 03, etc. After I ran the CDDB lookup, the track titles automatically renamed. I then noticed the last track on the CDs is named DATA or DATA TRACK. I suspect this last track cannot be renamed.

Nonetheless, I manually renamed that last (DATA) track and ripped the CD. As might be guessed, the last track never appeared in the final output directory, but all previous tracks were named as expected. Renaming had no effect on this last track.

Next I renamed the second to last track --- a valid song track and again ripped the CD. The final output directory showed the last song as renamed.

At this point, would seem there is no problem in R14, although this bug report was filed against 3.5.12.

Kristopher, do you want to keep this bug report open or close as resolved?

(In reply to comment #2)
> I tested this in R14. The audio CDs all had more than 15 tracks.
> 
> Without the CDDB lookup, the tracks are labeled generically as Track 01, Track
> 02, Track 03, etc. After I ran the CDDB lookup, the track titles automatically
> renamed. I then noticed the last track on the CDs is named DATA or DATA TRACK.
> I suspect this last track cannot be renamed.
> 
> Nonetheless, I manually renamed that last (DATA) track and ripped the CD. As
> might be guessed, the last track never appeared in the final output directory,
> but all previous tracks were named as expected. Renaming had no effect on this
> last track.
> 
> Next I renamed the second to last track --- a valid song track and again ripped
> the CD. The final output directory showed the last song as renamed.
> 
> At this point, would seem there is no problem in R14, although this bug report
> was filed against 3.5.12.
> 
> Kristopher, do you want to keep this bug report open or close as resolved?

If, on the CDs you used, track 15 is actually a DATA track, I'd recommend testing with a CD that has track 15 as an actual audio track.

Regardless of whether it was data or audio, you shouldn't have to rename the second to last song to make the final song rename. If you have to, I'd recommend keeping it open until that's resolved.

As soon as I'm able to test this myself, I will. That might not be for awhile though.

I renamed the second-to-last track only as a test because renaming the last (DATA) track proved nothing. With that said, I forgot to test renaming the 15th track.

I tested that and the 15th track retained the name I provided.

I don't have any CDs with exactly 15 tracks, although I could create one.

(In reply to comment #4)
> I renamed the second-to-last track only as a test because renaming the last
> (DATA) track proved nothing. With that said, I forgot to test renaming the 15th
> track.
> 
> I tested that and the 15th track retained the name I provided.
> 
> I don't have any CDs with exactly 15 tracks, although I could create one.

I'm not sure if having it at exactly 15 tracks will affect it or not. It might, or it might not. The one I had used had 15 tracks exactly.

Also, I don't know if using a custom-made audio CD will affect it since the one I used was a pre-made album. It could just be an issue with naming the tracks from CDDB lookup, or it could be naming the tracks in general (regardless of CDDB).

If this bug is still open when I can finally replace my hard disk, I'll test it myself on the latest nightlies using my 15-track CD (I don't have anything more than 15 tracks).

Is this report still valid?

(In reply to comment #6)
> Is this report still valid?

It seems fixed on 3.5.13.1, I will test later on R14.

Kris, any success testing in R14?

(In reply to comment #8)
> Kris, any success testing in R14?

R14 seems not to detect my DVD drive (either that, or there's a problem with VBox). Therefor I cannot test.

VBox? -> VirtualBox? Recently I had the same problem. I needed to enable pass-through. :-)

(In reply to comment #10)
> VBox? -> VirtualBox? Recently I had the same problem. I needed to enable
> pass-through. :-)

That fixed it, thanks.

This bug is now fixed. Marking it resolved.

Thank you!