MusicBrainz query doesn't return year (anymore)

[Alexandre Maciel]

When I try to get tag information from MusicBrainz, the year field doens't appear. This was working in Ubuntu Dapper (1.3.9), possibly Ubuntu Edgy (1.4.3) as well.

[effraie (effraie)]

Please, try with feisty original package, and give us feedback :)

[Alexandre Maciel (amaciel81)]

Hi,

I tried with Feisty original packet as well with Backports 1.4.6 version and I get the same result. My versions are:

- amarok 1.4.5-0ubuntu7
- amarok-xine 1.4.5-0ubuntu7
- libtunepimp5 0.5.2-1ubuntu3
- libtunepimp5-mp3 0.5.2-1ubuntu3

I'm sending another screenshot (Amarok original Feisty packet).

Best regards,
Alexandre Maciel

[Albin Tonnerre (lutin)]

Reporting in musicbrainz/ubuntu as it's not a medibuntu issue in particular.
Cheers

[Lukáš Lalinský (luks)]

This is not a libtunepimp bug. Since version 0.5, libtunepimp doesn't provide any API to lookup MusicBrainz. This functionality is implemented directly in Amarok.

[Launchpad Janitor (janitor)]

[Expired for Medibuntu because there has been no activity for 60 days.]

[Harald Sitter (apachelogger)]

What's the status on Gutsy and Hardy?

[Alexandre Maciel (amaciel81)]

In Gutsy, Amarok have the same status. Check the attachment.

Best regards,
Alexandre Maciel

[Harald Sitter (apachelogger)]

Well, this feature was at least present in Dapper (Amarok 1.3.9), though from looking at the changes over 1.3.9 (dapper), 1.4.3 (edgy) to 1.4.8 (hardy) I didn't find anything which would indicate that this was removed.

My guess, without looking at the code, is that Amarok generates the result rows in the MusicBrainz window in a dynamic way, depending on the query results. So, either libtunepimp/libmusicbrainz doesn't pass the year to Amarok at all, or Amarok doesn't process it properly, or some other wicked issue.

Someone, please file this upstream.

[Jonathan Thomas (echidnaman)]

The Amarok crew has dumped MusicBrainz support for Amarok 2.0 in favor of "something better" (See: http://amarok.kde.org/blog/archives/809-Missing-features-in-Amarok-2.html)
As such this bug probably is not going to be fixed.