After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 547814 - Edit paths to renamed/re-located song files
Edit paths to renamed/re-located song files
Status: RESOLVED DUPLICATE of bug 385965
Product: banshee
Classification: Other
Component: Metadata
1.2.1
Other All
: Normal enhancement
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-08-14 18:07 UTC by Matthias Stefan
Modified: 2008-08-14 23:17 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Matthias Stefan 2008-08-14 18:07:26 UTC
Sometimes a song stored in Banshee needs to be renamed or moved to another folder for whatever reason.

Then this song in Banshee is marked as "missing", and the only way to make it playable again in Banshee is to re-import it (and to re-tag afterwards, if the option "Write metadata to file" has not been used).

Not only does this appear to be a quite complicated way and not user friendly at all; the real (time consuming) problem behind it can be playlists: If there are many different (non-smart) playlists, you need to check any of them whether the re-located song was in and the add the newly (re-)imported (old) song once again to any of them (if appropriate) in order to prevent loss of this information. (Or you link the song from its new location to the old one. Then you will not need to update your playlists, but what if the links accidentally get lost or deleted some day?).

Proposal / Solution:

The most logical way to "keep Banshee informed" about the location of a song is to enter its (new) recent location into the location section in the song metadata window. That's why I suggest to simply make the field "Location" in "Edit Metadata" > "Details" writable for the user. So the new path of a song could quickly be entered here if necessary and Banshee can use this input - after a appropriate plausibility check (does the provided path exist?, is the new file really a music or video file?) to update the database entry immediately.

Additionally, the "X" (symbol for "missing") in the song list could be made clickable, leading to a file selection dialogue where the song's new location can be chosen the point-and-click way. (A similar button could also be provided beside the "Location" field in "Edit Metadata" to make it all even more user-friedly / fool-safe).
Comment 1 Andrew Conkling 2008-08-14 23:17:58 UTC
Thanks for your bug report. Banshee will soon (hopefully really soon!) have an extension that allows to monitor changes to the Library (much like Rhythmbox already does). That will require no user intervention at all, so it should be quite elegant, but care should definitely be taken for moved files and their metadata (especially ratings and play count, as those cannot be written back to the file.

Marking as a duplicate of bug 385965. I'll add a comment there about that particular case.

*** This bug has been marked as a duplicate of 385965 ***