[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 309697] New: Fix metadata with last.fm scrobbling response
From:       Diego Agulló <aeoris () gmail ! com>
Date:       2012-11-07 14:42:46
Message-ID: bug-309697-17878 () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=309697

            Bug ID: 309697
          Severity: wishlist
           Version: unspecified
          Priority: NOR
                CC: sam@sentynel.com
          Assignee: amarok-bugs-dist@kde.org
           Summary: Fix metadata with last.fm scrobbling response
    Classification: Unclassified
                OS: All
          Reporter: aeoris@gmail.com
          Hardware: Other
            Status: UNCONFIRMED
         Component: Services/Last.fm
           Product: amarok

Created attachment 75077
  --> https://bugs.kde.org/attachment.cgi?id=75077&action=edit
Erroneous track metadata notification

Amarok could provide a way to fix a track's metadata following the information
provided by last.fm API in response to a scrobble or nowplaying request. As of
today, the API is returning a piece of XML code as in:

  <lfm status="ok">
    <nowplaying>
      <track corrected="1">Wish You Were Here</track>
      <artist corrected="1">Pink Floyd</artist>
      <album corrected="0">Wish You Were Her</album>
      <albumArtist corrected="0"/>
      <ignoredMessage code="0"/>
    </nowplaying>
  </lfm>

As far as I can see, this information is being discarded, but it may be useful,
isn't it? The confirmation could be handled via an optional notification as
shown in the attached image (with yes/no buttons, of course)..

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]