Version: 2.0.1 (using Devel) OS: Linux Installed from: Compiled sources Amarok 2.X seems to have a problem identifying ID3 tags entered from kid3; I haven't had any other applications causing any trouble (including Amarok 1.X). Way to reproduce: take an mp3 file, change its tags with kid3 and try to open in Amarok. No tag information is read and even the bitrate and length information have disappeared.
This is most likely a support issue - make sure you are writing the correct version of the tag (id3v2.4). If you can narrow it down and are absolutely certain that this is a bug, please reopen and explain a thorough explanation why this is the case.
I've made sure to use v.2.4 ID3 tags, but it seems it might be more complicated. I had a file with a v. 2.3 tag and using eyeD3 I converted it to v.2.4 and I had the same behavior. Also, using eyeD3 I removed _all_ tags and added a new v.2.4 tag (using eyeD3 this time) and Amarok still wouldn't read it... I will not reopen the bus as I am not sure it qualifies, but it doesn't look like a support issue to me, as I found a second tagging s/w that produces the same behavior.
Christos - I'll reopen the bug until someone with a better insight into tag reading can verify or provide an explanation.
Please someone look at this or close it. Keeping it open for fun is of no use.
Okay, something really strange is going on here. I have most of my files on a USB NTFS-formatted hard disk. When I load them in amarok playlist from the usb, I get the aforementioned behavior: no tags are read (for most but not all of my files!). If I copy the same files on my laptop hard drive (not in the scanned collection) all the tags are read properly... I cannot understand what is happening... Changing to invalid as the title now seems completely irrelevant.