Version: 1.83 (using 4.00.98 (KDE 4.0.98 (4.1 RC1)), Kubuntu packages) Compiler: gcc OS: Linux (i686) release 2.6.24-19-generic "Edit track details" dialog opens normally, but the changes are not applied.
Should be fixed in alpha 2 which will be released in a few hours. Please reopen if it is still happening with alpha 2 once you can update to it.
*** Bug 167200 has been marked as a duplicate of this bug. ***
This bug was not totally fixed. Sometimes the tag editor works, sometimes it does not.
This bug was not totally fixed. Sometimes the tag editor works, sometimes it does not. (Resending comment 'cause I forgot reopening it).
*** Bug 167858 has been marked as a duplicate of this bug. ***
Is this still valid? Nota bene, I've noticed that Amarok currently requires a restart to pick up collection changes after a rescan. Could this be the case here too?
I can confirm this. In amarok2 the metadata for the file "1 Lion.flac" reads: Title: Lion Artist: Macross Frontier Album: Lion However using metaflac --list on the file yields the following: comments: 8 comment[0]: ALBUM=Lion - Macross Frontier OP2 Sinble comment[1]: ARTIST=May'n (Sheryl Nome) / Nakajima Megumi (Ranka Lee) comment[3]: DATE=2008 comment[4]: GENRE=Anime comment[5]: TITLE=Lion comment[6]: TOTALTRACKS=4 comment[7]: TRACKNUMBER=1
Isn't this just another description of the problem reported in bug 166908?
*** Bug 166908 has been marked as a duplicate of this bug. ***
Thanks Maarten. I knew there was a similar bug...
Partially fixed in r858155. We don't update Composer or Disc Number yet.
Fixed the rest of the way in r858232: OGG Vorbis and FLAC files now save composer and discnumber tags. MP3 should, in theory, save the composer tag. However, there seems to be a bug in TagLib that means the ID3v2 tag doesn't get written, so we can't save that data. Once TagLib is fixed, it should work, though.
Actually, it does work with MP3. It turns out the id3v2 command line utility can't cope with the way TagLib writes ID3v2 tags. I'm not sure who's at fault there, though. I suspect the i3v2 utility.
Yes, after some testing, it seems the the id3v2 utility just silently ignores ID3v2.4 tags. So it's all good.