Version: 2.2.1 (using KDE 4.3.3) Installed from: openSUSE RPMs Some days ago I installed openSUSE 11.2. Before I used openSUSE 11.0 with amarok 2.2.0. After the update of my distro I also updated KDE to 4.3.3 and Amarok to 2.2.1. First I was wondering why my collection was so small. With 2.2.0 I had more than 13k songs. Now I have about 12.900 songs. I also recognized that the albums I added with amarok 2.2.0 were shown in the collection-browser but with no songs. So you can click on the plus but with no effect. I found a little workaround: move the files to another folder, outside of the folders which are scanned by amarok. Rescan database, move the files back again und rescan a second time. Now the files are in the database but the scores (this stuff with the stars) are wrong and must be corrected by hand.
Well, you could have had this easier: do a full rescan, then restart Amarok. This only happened to people who transited from 2.2.0 to 2.2.1, where a forced restart should have been triggered after the full rescan. *** This bug has been marked as a duplicate of bug 214599 ***
A total rescan was the first thing I did, but it didn't work for me.
Hm, then it's not a duplicate, sorry.
I've the same problem. Some albums in my collection are not indexed by amarok. To solve the problem I try to edit the files or I rename the directory or move to force amarok to rescan the database, But in some case also this method don't work and the collection will be not updated. My collection is on an NTFS partition.
This problem also exist on amarok 2.2.1.90 I just added the new "Die Toten Hosen" live-album to my collection and did a total rescan and then I restarted amarok. The album does appear on the database but with no year and with no songs. The files were ripped with abcde and lame with the option -V2 Again I had to move a file to another directory - do a short rescan. After that the songs where listed in the collection.
Matze, did you restart Amarok after the first scan?
Yes. I wrote: [I] did a total rescan and then I restarted amarok.
I confirm this bug on amarok 2.2.2. Probably there's some problem in indexing the pieces where the tags are incomplete. For example only the tag for the title is filled: I've a case like this: if we search for with some words the in the list appears a sub-tree with a single piece named unknown.
Setting to confirmed.
Maybe I'm getting confused between possibly inconsistent information in the comments, but I have no idea what the problem is. If I add a new folder it's indexed without a problem.
(In reply to comment #10) > Maybe I'm getting confused between possibly inconsistent information in the > comments, but I have no idea what the problem is. If I add a new folder it's > indexed without a problem. In general I've observed that this problem appear with some old mp3 file where the tags for the title, artist, composer ... are empty or inconsistent. And all the information of the pieces are written in the filename. A good method for solving the problem is to write something in the tags.
I've recently observed also this problematic behaviour (amarok 2.2.2): I've added a new album and it was immediately listed in the collection. But after a modification of the title of the album and after setting up manually a cover the album has disappeared from the collection. I've solved with another modification of the album title.
(In reply to comment #12) > I've recently observed also this problematic behaviour (amarok 2.2.2): > > I've added a new album and it was immediately listed in the collection. But > after a modification of the title of the album and after setting up manually a > cover the album has disappeared from the collection. > > I've solved with another modification of the album title. Did you let Amarok update the collection? Is your collection on a remote share? I can't reproduce this here at all, not with Amarok 2.2.2 nor with the devel version.
(In reply to comment #13) > (In reply to comment #12) > > I've recently observed also this problematic behaviour (amarok 2.2.2): > > > > I've added a new album and it was immediately listed in the collection. But > > after a modification of the title of the album and after setting up manually a > > cover the album has disappeared from the collection. > > > > I've solved with another modification of the album title. > > Did you let Amarok update the collection? Is your collection on a remote share? > I can't reproduce this here at all, not with Amarok 2.2.2 nor with the devel > version. 0) For setting up the cover I've used the track details dialog box: -) Right click on a single piece in the play list. -) Select: edit track details -) Select: 'set custom cover' in the summary. > Did you let Amarok update the collection? I don't remember exactly: but in the firs case the album has disappeared after the manual update and in the second case I think that amarok has automatically updated the collection. Nb.: I've NEVER performed a full rescan of the collection >Is your collection on a remote share? My collection is on a separate partition in NTFS (windows Vista) and I use ntfs3g.
Then please do a full collection rescan and restart Amarok. This should solve the problem. Please tell me if it reappears. Jeff: could this be related to the remote collection?
(In reply to comment #15) > Then please do a full collection rescan and restart Amarok. This should solve > the problem. Please tell me if it reappears. > Jeff: could this be related to the remote collection? I've originally solved the problem by editing the title of the album. A full rescan is not necessary.
For me this problem has been solved with amarok 2.3.
Thanks for the feedback