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...