Version: 2.0.90 (using 4.2.2 (KDE 4.2.2), Kubuntu packages) Compiler: cc OS: Linux (i686) release 2.6.28-11-generic I moved two directories from my collection to somewhere out of the collection using Dolphin. Since then, I clicked "Rescan collection", restarted Amarok and even restarted the PC, but they are still in the collection somehow: Filtering for them in the collection browser shows nothing, but the number of tracks did not go down. In addition, when I move the whole collection to the playlist, the removed files are in there (of course, it can't play them). I don't want to (again) remove the collection database, but obviously that is the only way to get a track out of the collection which got removed by another application? This is Amarok 2.1 Beta from kubuntu-unstable
Even when it's amarok which renames the files (by choosing "organize"), it doesn't remove deleted files and instead duplicates the ones it renames. Selecting "Delete track" on such a non-existing crashes with a backtrace I will attach. I just lost all the track ratings I did today (what a fool I was to start doing that at all) because I had to remove the collection database - about the 10th time since I updated to Amarok 2...
Created attachment 33278 [details] crash backtrace
There really is no way to get a track out of the collection (besides removing the database, that is) - the "Remove track" feature of Amarok removes the track from the collection browser, but the track count does not go down, and dragging it to the playlist still contains the removed track.
*** Bug 190169 has been marked as a duplicate of this bug. ***
I have the same issue with the current trunk
Does this still happen with Amarok 2.1?
Yes it still happens. Tracks only get removed after a restart
*** Bug 194200 has been marked as a duplicate of this bug. ***
I tested it again with current trunk. Renaming a file works great now, be it by an other application or by Amarok itself using "Organize Tracks". Removing still has some problems though: Removing the file works, and the overall track count is correctly reduced. However, when I copy the same file back, it reproducibly (tried it two times) is not recognized by Amarok. The track count goes back up, but the file is not shown in the collection, no matter how often I restart amarok or rescan the collection. Only removing the database fixes it.
Can you try with current trunk? There's been a commit that should have fixed this.
Yes, it seems this got fixed - thanks a lot :)
Thanks for testing :)
*** Bug 195139 has been marked as a duplicate of this bug. ***
Also it doesn't reread tags of existing files. I'm russian and many song in our (russian) case have ID3 with cp1251. Amarok doesn't work with diffrent encodings - ok. But when such files fall into collectio, I see names in wrong encoding. I convert tags to utf8 but! There is no way to make amarok see such changes, except deleting the collection and rescaning folders again. It's annoy.
Sorry, dosn't notice that this report is closed :-D
(In reply to comment #14) > Also it doesn't reread tags of existing files. > I'm russian and many song in our (russian) case have ID3 with cp1251. > Amarok doesn't work with diffrent encodings - ok. But when such files fall into > collectio, I see names in wrong encoding. I convert tags to utf8 but! There is > no way to make amarok see such changes, except deleting the collection and > rescaning folders again. It's annoy. I don't understand. How exactly do you expect Amarok to notice that tags have changed if it doesn't rescan those files?
(In reply to comment #16) > (In reply to comment #14) > > Also it doesn't reread tags of existing files. > > I'm russian and many song in our (russian) case have ID3 with cp1251. > > Amarok doesn't work with diffrent encodings - ok. But when such files fall into > > collectio, I see names in wrong encoding. I convert tags to utf8 but! There is > > no way to make amarok see such changes, except deleting the collection and > > rescaning folders again. It's annoy. > > I don't understand. How exactly do you expect Amarok to notice that tags have > changed if it doesn't rescan those files? May be rescan files with changed last mod time?
Well, a full collection rescan should be enough to make those show up. Vovochka, please do not post to closed bugs of other version, I bet you do not use Amarok 2.0.90, don't you?
Well right -- I asked how you expect Amarok to notice changes in the tags of files without rescanning, and your answer is to rescan -- which was my point. FWIW, Amarok detects changes in the mtimes of the defined folders in your collection -- not of each individual file. (There are several reasons for this that I won't go into here.) Simply doing a "touch" on the directory with the changed files will cause the incremental scan to include that directory next time. Note that this behavior changed a bit around 2.2.1 -- if you have changed files in subdirectories as well, you touch those subdirectories too.