Registered Member
|
Hello all, I'd like to give Amarok2 a shot now that it's matured a bit, but I'm unable to import my music collection.
When I set up my collection folder and tell it to scan it finds no music and spits out this message:
I also tried importing my Amarok 1.4 database, but it only pulls in 1,715 of my ~50,000 tracks. It seems random in what it finds. Most of the albums in my Amarok 2 library have but one or two tracks. During the Amarok 1 import, I get a lot of messages like this on my console:
My computer is running FreeBSD 8.0 amd64 with a raidz1 array holding my music. Amarok 2.1 had this same problem when I tried it months ago on FreeBSD 7.2, but I waited for 2.2 to be committed to Ports in case the problem was fixed. I erased my amarok preferences and database before trying 2.2. If anyone has any suggestions I'd love to hear them |
Registered Member
|
Hello again. Excuse the double-post, but I just updated to 2.2.2 through Ports and am still unable to scan a collection.
|
KDE Developer
|
So, after looking at the code, I think I know what happened there:
Amarok 2.2.2 is using a new feature of the "amarokcollectionscanner" tool, which requires the argument "--savelocation". It's not yet listed if you type "amarokcollectionscanner --help", but that's only a small oversight, we will fix that. The real problem: The version of your scanner is probably not the one from Amarok 2.2.2, but instead from an older Amarok version. One way this could happen is that you have installed it in two different places (from a previous install). Try to search your system for the file "amarokcollectionscanner", please.
--
Mark Kretschmann - Amarok Developer |
KDE Developer
|
Ok, I have added this to "--help", to make it easier to tell if the scanner version is correct (will appear in Amarok 2.2.3).
--
Mark Kretschmann - Amarok Developer |
Registered Member
|
Aha, that sounds like exactly what happened. I do indeed have two copies of amarokcollectionscanner:
And the one in /bin from 1.4.10 is first in the path:
|
Registered Member
|
Everything seems to work fine after changing the path and starting Amarok:
I'll make a launcher script to do this and then launch Amarok, lest I make the change permanently and break 1.4 in the same way |
Registered users: Bing [Bot], claydoh, Google [Bot], rblackwell, Yahoo [Bot]