© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Ok, let me answer separately:
- The ~15% CPU TagPlayer uses is normal and to be expected, it's mostly due to the playback, compare it with banshee and you'll see it's not at all a bad number...
- TagPlayer uses Last.fm info, which means, if a song isn't recognized by Last.fm (usually because of incomplete or wrong metadata on the song file) then TagPlayer won't keep in it's library, since it can neither identify it or assign it tags. That's probably what's happening with the songs you're not getting, check it's IDv3 metadata to see if it's correct. Still, this type of situations would be much easily debbuged if TagPlayer had some sort of debugging option, so I'll work on that.
- Python 2.x has a lot of problems with unicode encoding because some of its inner libraries are not ready to deal with it.. This type of errors is especially obvious for people whose language have non-ascii symbols, such as russian (i'm portuguese, so I have the same issue very often). In this case though, I only get that error when I use tagplayer with LANG=C, with utf8 locales that doesn't happen ( I even used a similarly named directory with cyrillic and greek characters to test ).
without the LANG=C prefix do you get any kind of error in the terminal?