Hi!
I copied an mp3 audio book with 83 tracks to amarok. Initially the files had not very helpful id3 tags, for example non-uniqe track number like 1/11, 2/11. I think I first imported them into amarok like this. Then I changed id3 tags with puddletag, amongst others to have track numbers from 01 to 83. But they are not displayed in amarok. Tracks 01 to 11 show the correct track numbers, but title12 has 1 again instead of 12, and so have others. I then changed the track numbers to 01/83 to 83/83. Did not help in amarok, still no change. I touched the dir and told amarok explicitly to refresh the album in the collection.

kid3 shows for example for track 12:
tag 1, ID3,v1.1, track number: 12
tag 2, ID3,v2.4, track number: 12/83

What going wrong here? How to get track numbers corrected without changing every track manually in amarok?
I'm using standard amarok 2.8.0 of kubuntu 14.04.

Thanks, Peter

Did you do a full rescan, then restart Amarok? There is a caching error in the Collection Browser display, please try that.

One thing that comes to my mind: did you set the track number as 12/83 in the track number field or did you set 12 and 83 in the total track number field? If it is the former, then that is the most likely cause of the issue, as total track number is another ID3 tag.

I entered the 01/83 as the track number. I did not find a total track number in amarok, puddletag or kid3.

Amarok is still refreshing the collection (at least I hope so. The blue bar is still there, but does not display the text any more after switching windows...).

Bad idea, that, as it is not standard in the id3 specification, and Amarok only uses that.
Both kid3 and puddletag do indeed not show that ID3 field, but easytag does so by default, and if you edit the track details on an album or a track you can see the field in Amarok as well.

Hi,
the rescan of the complete collection helped. Now amarok displays the correct track numbers, after all. Would be nice if that would have worked after the rescan of this album/directory. It seems you new this problem. Do you know if there is already a bug report for this?

Thanks for the tip!
Peter

Well yes, I told you so, we do know since quite some time there is a caching bug in the Collection Browser. We have opened and close certainly a hundred bugs about this over the years, but there is little information there, as we simply don't know what is causing the problem.

The most recent and current bug about this is this one: https://bugs.kde.org/show_bug.cgi?id=350292

You can subscribe to it if you want to get notified when something changes, but unfortunately this will not happen before the end of the Qt5 port.