Hello,
since weeks I try to import my collection from 1.4 to Amarok 2. Everything works fine, play counter and so on. But not my most important collum, the rating (or score or percentage). I tried it on many SVNs, RCs and even the final but it still does not want to import that...
Is anyone else experiencing this?
Is there a workaround?

The other thing is that the import collection scanner should be improved so it even imports the tracks that are not on the same path anymore. Just an example: Trying to import a track that was on /root/windows/blabla that is now on K:/blabla (read: migrating to Windows) does not work.

Thanks heaps for a reply...
Boni

Guess it's working for everyone but me...

There are a few bug reports for the Importer feature in 2.0. You could browse them and perhaps add your findings to a matching report:

http://bugs.kde.org/show_bug.cgi?id=174784
http://bugs.kde.org/show_bug.cgi?id=174269
http://bugs.kde.org/show_bug.cgi?id=173941
http://bugs.kde.org/show_bug.cgi?id=176237

Hi,

I've got the same problem with Amarok 2.0.1.1, and unfortunately none of the bugs offer a solution. Does anyone here know a solution?

Thanks god I'm not the only one...

I found another bug which describes this problem:
http://bugs.kde.org/show_bug.cgi?id=174444
They actually claim it's been resolved, but it still doesn't work...

roffffel wrote:I found another bug which describes this problem:
http://bugs.kde.org/show_bug.cgi?id=174444
They actually claim it's been resolved, but it still doesn't work...

In this case, feel free to reopen the report...

Mark Kretschmann wrote:

roffffel wrote:I found another bug which describes this problem:
http://bugs.kde.org/show_bug.cgi?id=174444
They actually claim it's been resolved, but it still doesn't work...

In this case, feel free to reopen the report...

Actually, I can't reopen the bug, even though I was logged in. Maybe I need some special rights?
Could you reopen the bug for me?
Thanks

roffffel wrote:

Mark Kretschmann wrote:

roffffel wrote:I found another bug which describes this problem:
http://bugs.kde.org/show_bug.cgi?id=174444
They actually claim it's been resolved, but it still doesn't work...

In this case, feel free to reopen the report...

Actually, I can't reopen the bug, even though I was logged in. Maybe I need some special rights?
Could you reopen the bug for me?
Thanks

Done