GNOME Bugzilla – Bug 357001
Album improperly guessed from folder name at the root of the library
Last modified: 2009-01-02 21:45:57 UTC
Please describe the problem: I set my music library location to be a folder named "music". Now I've noticed that a number of my songs list an album of "music". They shouldn't be picking up the parent folder name. Also, some display as met@music ... I'm not sure where that came from. Likewise, the artist on some matches the name of the folder above "music". While I understand the desirability of grabbing that information from the folder names, it shouldn't grab it from the root of the music library, and certainly not above that. Originally filed at: https://launchpad.net/distros/ubuntu/+source/banshee/+bug/52060 Steps to reproduce: Actual results: Expected results: Does this happen every time? Other information:
Please look into this. I have a lot of mp3:s that don't belong to an album (downloaded from blogs, artists' homepage etc). When I import these files, which has blank metadata for album and track #, banshee likes to fill these in using some guessing work (sometimes parent folder name, but not always). IMO, it should be possible to have tracks with blank track# and album metadata fields.
This is confirmed behavior. It is possible to clear them with the edit metadata dialog though. Still happens in 0.11.3 too.
*** Bug 353064 has been marked as a duplicate of this bug. ***
Comments from bug 353064: Opened by Patrick van Staveren (reporter, points: 12) 2006-08-27 05:08 UTC This is so small, but has always annoyed me... When Banshee sees no Album tag on a new file, it always tries to guess album info from the parent folder name. This is intelligent, of course! However, one thing that defies logic would be to grab the album name from the music library directory. In my case, I have some random singles that I keep in the top level folder of my music library (eg. a track that's right in the library directory as set in the prefs - not in a subfolder). Some of these don't have artists in them, and thus banshee tags them with the music library folder name. Naturally, this is undesired as I get a bunch of files with an incorrect album name. Specifically, * My music library is set to /pub/media/music * Files in question are located as /pub/media/music/crap.{mp3,ogg,flac} * When importing, Banshee sets the Album name to "music" This was just annoying before, but I'm sure that once tag writing becomes a default and automatically gets written, then I'll have a few hundred tracks on the album "music" that will now have it in it's id3 tag. Sick! What should happen: In this case, where the track is at the top level and we know it's not in an album folder, Banshee shouldn't use the folder name but rather blank or "Unknown" (not null of course, as this would break things). I think Unknown might prove to be the best option as this makes tracks who don't have an album easy to locate. Would be useful futuristically when we have an interface that's more advanced than ours in a filter based view. Unknown is probably best, as blank might create trouble in a number of things, such as DAP devices creating filesystem heirarchies, audioscrobbler reporting pulling malformed URLs, etc...
This is still happening in SVN trunk, confirming.
Can anyone test whether this still happens in 1.x?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!