Posts: 171
Joined: Jan 2011
Reputation:
0
I ran into the same problem, You have to rescan your library. That's the only way that I was able to get mine to work. Also, use Universal Album Scraper and Universal Artist Scraper for the "Default service for album information" and "Default service for artist information" in Music - Settings - Library. You can try changing those before you rescan, but I'm pretty sure it failed for me, sorry I don't have better news.
PS - Don't just take my word for it, I'm not a developer for XBMC, I'm just an avid user.
Posts: 79
Joined: Sep 2008
Reputation:
0
Thanks for your feedback, I will try this
Posts: 79
Joined: Sep 2008
Reputation:
0
I've tried a lot of other things after my initial problem without getting to the bottom of the problem. I've opend a Ticket (#13906) for this behaviour to find out if it is a bug or something wrong in my setup (even if I run an out of the box installation for testing purposes)
Posts: 204
Joined: Oct 2012
Reputation:
0
Now is May, after Frodo 12.2 and I have to tell you that I am now in the process of rescanning my entire music library, since Frodo had lost it after the upgrade from Eden.
Worse than that, I spent many hours in Eden completing the thumbnails images for all artists; and those are gone as well.
Major Major bug, I waited to install frodo, thinking it will stabilize soon, but my overall feeling is that Frodo was (and still is) not stable enough for release, and they released it just because of a stupid deadline.
Posts: 31,445
Joined: Jan 2011
(2013-05-28, 13:26)ilomambo Wrote: Now is May, after Frodo 12.2 and I have to tell you that I am now in the process of rescanning my entire music library, since Frodo had lost it after the upgrade from Eden.
Worse than that, I spent many hours in Eden completing the thumbnails images for all artists; and those are gone as well.
Major Major bug, I waited to install frodo, thinking it will stabilize soon, but my overall feeling is that Frodo was (and still is) not stable enough for release, and they released it just because of a stupid deadline.
Nah, we missed our original "deadline" by a month in order to address major issues, and the bug fix releases don't have hard deadlines. If this was a major issue that was happening to most users, we would have fixed it before release. Thousands upon thousands of users have upgraded without this issue, so don't assume everyone is the same as you. Even Berz had the issue he discovered fixed.