| Summary: | Make it easy to move database | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Alex Dănilă <alex.danila.web> |
| Component: | Collections/Local | Assignee: | Amarok Bugs <amarok-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | wishlist | CC: | matej, ralf-engels, tuomas |
| Priority: | NOR | ||
| Version First Reported In: | 2.8.0 | ||
| Target Milestone: | 2.9 | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Alex Dănilă
2014-11-14 23:46:01 UTC
This should be (partially or even fully) resolved by Konrad's GSoC 2013 (to be included in next Amarok release), see http://konradzemek.com/ Changing the description, as it is about moving the database from one computer to another, not about actually moving the collection (physical files). If you never want to loose the rating again, just go to "settings/metadata" and switch on the syncing. This would store the metadata in the file. Storing rating and playcounts is even somewhat compatible because there is a standard for it. Update: actually I think the method of copying database files has worked. I started Amarok today and can see that many many songs have ratings, tags and play counts. They see correct. Closing as based on the last comment, this might have actually worked back 10 years ago. If everything's in right place on first start / first collection update / rescan, the copy process probably works. (This is somewhat sensitive, as the tracks not being in collection for during a scan can easily lead them to be deemed removed, but writing stats to files is a possibility. Additionally, some related bugs that might have caused loss of statistics if the paths were not exactly the same have been fixed since.) |