Bug 243101 - k3b "Rip Audio CD" doesn't record track numbers to mp3 tags
Summary: k3b "Rip Audio CD" doesn't record track numbers to mp3 tags
Status: RESOLVED DUPLICATE of bug 218614
Alias: None
Product: k3b
Classification: Applications
Component: general (show other bugs)
Version: 1.70.0
Platform: openSUSE Linux
: NOR minor
Target Milestone: ---
Assignee: Michał Małek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-29 03:30 UTC by Vivek
Modified: 2010-07-02 18:39 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vivek 2010-06-29 03:30:35 UTC
Version:           1.70.0 (using KDE 4.4.4) 
OS:                Linux

Whenever I rip an audio CD with k3b (format:mp3, encoder:lame), the track number is not recorded in the file's metadata.  It's strange because it's completely fine with recording the track number to the filename, but I can't figure out how to record track numbers to the mp3 (id3?) tags.

Album, Artist, Song Title are all present, but without Track Number some software messes the order around.

Reproducible: Always

Steps to Reproduce:
Insert Audio CD, rip a track, check track with preferred software (ie Amarok).

Actual Results:  
The track number should be recorded.

Expected Results:  
No track number in file metadata.

I'll see if it vanishes if I update to a newer factory version, but this bug's been present for a while.
Comment 1 Michał Małek 2010-07-01 19:46:55 UTC
Please go to "Settings"->"Configure K3b"->"Plugins" and click configure button on "External audio encoder" item. Next select "Mp3 (Lame)" and click "Edit". In "Command" see if there is "--tn %n" in lame command string. If not, add it and see if it works.
This is probably effect of bug 218614. It's fixed in 1.70, but may still be in effect if you've upgraded K3b from previous version (command string was saved in configure file).
Comment 2 Vivek 2010-07-02 18:39:10 UTC
Adding "--tn %n" in the command string fixes it. Thanks a lot! 

Marking bug as Resolved > Duplicate of 218614.

*** This bug has been marked as a duplicate of bug 218614 ***