Everytime I come back to Amarok after a little while the usability of Amarok2 continues to improve, it's been a long road... but  the work is really starting to shine through. So, kudos and thanks to the developers...

That being said... I got some issues.

I have a portion of my songs (about 3000 worth) that are showing up under an "unknown" (or blank) genre. This happened before in 1.4, and was normally fixed by compiling Amarok with the --with-mp4v2 option. I compiled Amarok2 this time with all available libraries, however I still have this unknown genre. I can, at least, edit the tags though.

After much research... I read that Amarok2 uses unicode for reading tags, I found a couple posts that referred to reseting the tags in iTunes. I have a vmware image around, so I did just that. Changed all the tags to unicode v2.3... That didn't help this issue...

The real fun part... when I try to edit certain tracks - Amarok just crashes. I've attached the crash report, hopefully it's helpful... it seems to complain extensively about taglib.

I'm at a loss as to what to do next. I can see no discernible difference between the tracks that crash amarok and the ones that work fine. I've found several m4a that are fine... and others create this issue.

Any insight would be helpful... thanks again.

Ok... this is not a shameless bump... this is an actual update.

I got Amarok to stop crashing... by compiling my own version of taglib-extras from the kde-svn, and recompiling amarok with that. So, Amarok doesn't crash when I try to edit the "unknown" files anymore... but I still have them.

I'd love to figure out how to... either: 1) properly encode my id3 tags so Amarok doesn't through a fit 2) properly compile Amarok so it can read my id3 tags, without it throwing a fit...

tanx...