GNOME Bugzilla – Bug 628372
Track names, artists, album, etc doesn't support percent-encoded format
Last modified: 2010-09-12 16:34:58 UTC
Created attachment 169128 [details] just an example Track names, artists, album, etc doesn't support percent-encoded format for example a track name like: 11 - Wolfpack is displayed: 11%20-%20Wolfpack and almost 3000 of my 25000 tracks have percent-encoded meta data. the worst is this data are scrobbled to last.fm this way and it makes everything ugly. Regards -- Sassan
What version of banshee are you running? Also, It seems that you've attached an incorrect screenshot.
Created attachment 169455 [details] example
Excuse me for inconvenience, I attached the right screenshot, I use banshee 1.7.4. maybe it's not a bug at all, but it would be nice if banshee could handle this type of strings, or maybe it can fix them in its "Fix Music Metadata...".
Do those tracks have proper metadata in the files ? If they don't, Banshee uses the filename for the Name column, and because of bug #608382, spaces were imported as %20. This bug should be fixed in Banshee 1.7.4 and above. So could you please try the following and post your results : - Check the metadata of one of these files with an other tool, like "Easy Tag" or eyeD3 - Remove this file from your library (don't delete the file), and import it again.
- I checked those files with "Easy Tag", those fields were empty. - It was solved when I removed one of these files from my library and imported it again. Now I think it was a problem with upgrading banshee (these library was created by banshee 1.5.x and I kept it when I was using all the later versions of banshee: 1.5.x, 1.6.x and now 1.7.x) I removed and imported again all the important tracks I need, so now my problem is solved, but I kept some files just in case, so if you want, you can ask me to check something and I'll tell you the result.
Thanks for following up on this report. Your tests show that your problem was caused by bug #608382, so I'm marking it as a duplicate. Please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 608382 ***