Well, what can I say?  I've had no end of troubles with "Fast Forward".  First my iPod issue (in another thread) and now this.

I've just ripped a couple of CDs using KAudioCreator.  I used lame, with the Extreme preset (~240kbps).  xmms plays the resulting mp3s fine, but amaroK simply refuses to acknowledge their existance.  If I go to the folder they're in via the "Files" tab, they just aren't there.

This may be related to the fact that if I move ~/.kde/share/config/amarokrc to a backup location, amaroK tells me that the xine engine (which I use) can't play any mp3s at all.  I put amarokrc back and it's fine again.  I'm using xine-lib-1.1.2_pre20060328-r1, by the way.

Oh, and one more thing - something I ripped with KAudioCreator earlier (The Who - A Quick One) does appear.  Twice.  I have two identical entries for artist "The Who", the tracks of which reveal themselves to be the exact same files.

This whole thing is ridiculous, and I'm considering dropping back to 1.3.8, which worked perfectly for me.  Unless there's any fix, of course...

Well if amarok says your engine can't play mp3s i supect that it might be that way. Are you able to play mp3s with xine itself. What distro are you using, or did you compile xine yourself ? And what engine have you used with 1.3.8 ?

Yes, I'm sure that xine can play my mp3s - it worked perfectly with 1.3.8, and it also works if I say "xine song.mp3" on the command line.

It would appear that the "not recognising mp3s" problem was my bad - their names didn't end in .mp3, and amaroK evidently isn't as clever as Konqueror at looking at a file's contents to determine its type (they had the music icon in Konq, so I assumed they were fine).

But... the duplication thing still stands.  Why do I have two Whos?  Would it be a database issue?

You're not using mysql5 are you? Some weird behaviour has been seen there.

Maybe it IS worth creating a new mysql db and using that.

It might also be worth reinstalling taglib.

Nope, mysql-4.1.19.

Hmm, I manually deleted all the entries from all the tables in the amarok database and it seems OK now.  I guess it was just an upgrade issue.

SQL needs to recognise DELETE FROM * ... I guess it's a safety thing to stop me from accidentally doing something as destructive as I was intending

Thanks for helping me so much, by the way - I have Applauded you