| Summary: | album is inaccessible after changing its name | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Silver Salonen <silver.salonen> |
| Component: | Collection Browser | Assignee: | Amarok Developers <amarok-bugs-dist> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | mitchell, ralf-engels |
| Priority: | NOR | ||
| Version: | 2.4-GIT | ||
| Target Milestone: | 2.4.0 | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Silver Salonen
2010-12-17 15:32:20 UTC
When I did the same thing, but the target album "2003 - Duplicate" already existed in the list (I had changed a single track before changing all the other tracks the same way I described), all the changed tracks appear under the correct album name, but the old one ("01 - 2003 - Duplicate") still exists without any tracks under it.
Did you try a collection rescan? No I didn't and now so much time has passed that the albums show up correctly. So I tried to rename the album to "02 - ..." again. After that the album appeared in the list as "02 - ..." (with no year preceding it). I updated collection - nothing changed. I restarted Amarok and now the album is listed as "2004 - 02 - ..." (ie. correctly). I now removed "02 - " from album name and now the album shows up as "02 - ..." (ie. incorrectly). I can drag the tracks from under the album to playlist, but I cannot edit their tags from the collection browser (but I can do it when opening tag editor from playlist). I updated collection too, but it changed nothing. OK, thank you for the feedback. Either this is still a caching problem in the collection browser or a problem in the collection itself. I think this is a misunderstanding. When your change the album of a track a new album will be created (if not already existing) and the track will be moved. However the old album will still be visible in the collection view until you refresh it (e.g. by doing a new search). The rest of the problems sound like you are still using an older Amarok version. Are you sure that you have the beta not only installed but actually running? Best to remove the old Amarok. Yes, I have beta also running. So I guess one of the problems is that collection browser is not refreshed automatically when I've changed something? Which part is a "misunderstanding"? The misunderstanding is that the album is removed from the view if all tracks are removed from it. That is not the case. However the view should be refreshed and the new Album displayed unless the tracks are now not longer in your search results. At least it works here. I just tried it ten seconds ago. That's why I wanted to make clear that you are really using beta. Just to clarify - I'm not using any search there, just plain view. So I'm hit by this again in Amarok 2.4.1 (on KDE 4.6.3), but a bit differently now :) Use-case: 1) Rename the album (album's name is updated in collection browser as it should) 2) Rename the album again (album's name is NOT updated in collection browser) 3) Update Collection (album's name is updated in collection browser as it should) 4) Rename the album again (album's name is NOT updated in collection browser) 5) Update Collection (album's name is STILL NOT updated in collection browser, but the old name is now without the year) 6) Restart Amarok (album's new name is shown in collection browser as it should) It happens every time. This is what I just tried: On the collection view (right side) right-click on "Absolute Rock Anthems II (CD.1)" Select "Edit track details" Change the Album title to "Absolute Rock Anthems II" - View was updated Same thing again, change it to "Absoulute Rock Anthems" - View was updated Same thing again, change it to "Absoulute" - View was updated Are you doing something different? Can you update to the latest Amarok release and try it again? It seems that you perform the same actions indeed. What is the latest release? I'm running 2.4.1 and I thought that's the one. Yea, 2.4.1 should be fine. Anything else that might cause this problem on your side? I am frequently renaming audio books with 100 tracks. No problem, except that the UI is blocked while I do that. I don't know.. anything I could check? Any news on this? Silver, did you try Amarok 2.4.1? I need your feedback on this so I can close this or bump it to the developer again. Just tried the same sequence of actions I've written before. New results: 1) Rename the album (album's name is updated in collection browser as it should) 2) Rename the album again (album's name is NOT updated in collection browser and the year disappeared from the beginning of the album's name) 3) Update Collection (album's name is updated in collection browser as it should and the year re-appeared also) 4) Rename the album again (album's name is NOT updated in collection browser and the year disappeared again) 5) Update Collection (album's name is updated in collection browser as it should and the year re-appeared also) 4) Rename the album again (album's name is NOT updated in collection browser and the year disappeared again) 6) Restart Amarok (album's new name along with its year is shown in collection browser as it should) PS. I'm still running 2.4.1. Thank you for the feedback. Looks like the old Collection Browser caching problem which is tracked in bug 172542. *** This bug has been marked as a duplicate of bug 172542 *** |