GNOME Bugzilla – Bug 569009
[jamendo] Durations not properly loaded
Last modified: 2009-04-21 13:08:29 UTC
Jamendo has upgraded their database dump format. Because of this, the duration of a song is not loaded properly (it used to be in lengths attribute of the track element, now it is in a sub-element called duration). As a consequence of this, all durations are "unknown", and last.fm scrobbling stopped working (because a track has to have at least 30s). Note that the duration sub element is undocumented for some reason, it's present in the dump, but not mentioned in the documentation on http://developer.jamendo.com/en/wiki/NewDatabaseDumps
In addition, jamendo ocassionally has floating point values in the duration, and the simple conversion using int() will throw an exception. The magnatunes plug-in has a special parse_int() function in TrackListHandler.py for this: # parses partial integers def parse_int(s): news = "" for c in s: if c in '0123456789': # only positive integers allowed news += c else: break return int(news)
2009-01-25 Jonathan Matthew <jonathan@d14n.org> * plugins/jamendo/jamendo/JamendoSource.py: Parse track durations, protect against finish_loadscreen() being called twice due to gnome-vfs weirdness. Fixes #569009.
*** Bug 570229 has been marked as a duplicate of this bug. ***
*** Bug 579349 has been marked as a duplicate of this bug. ***