Version: 2.0.2 (using KDE 4.2.1) OS: Linux Installed from: Fedora RPMs Amarok is does not see to be able to read the id3 data of .oga file. It seems to be able to edit the data ( though it will not be displayed in the editing window ) and renaming the file from .oga to .ogg will rectify the problem. It would seem that the problem is most likely cause because Amarok does not properly recognise the .oga extension so that Amarok looks for any id3 data in the file. There were no problems found with .mp3 or .ogg file. As .oga seems to be the new standard for ogg audio file it would be nice if Amarok could properly handled them. Also could be a good idea to test .ogv file if Amarok supports video files ( don't uses them my self so have not tested that ).
A quick scan of Amarok's code revealed that we do actually seem to support both "ogg" and "oga", so the problem might be on another level (e.g. TagLib). However, I only checked this with SVN trunk, so it might have been changed recently. Next TODO for us: Renaming an "ogg" to "oga" and testing what actually happens.
Yeah, it's definitely TagLib to blame. I just talked to its author on IRC, and here's his reply: 10:11 <@markey> 10:10 < wheels> markey: svn does. And I really will get around to rolling a new release soon. I've been feeling guilty for a few weeks. So you just have to wait a bit for a TagLib update :)
taglib issue, see bug #178602
*** This bug has been marked as a duplicate of bug 178602 ***