Bug 17857 - Last "composer" tag gets returned as "artist" in CLI/JSON interface
: Last "composer" tag gets returned as "artist" in CLI/JSON interface
Status: UNCONFIRMED
Product: Logitech Media Server
Classification: Unclassified
Component: CLI
: 7.7.1
: PC Linux (other)
: -- normal (vote)
: ---
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-01-08 08:44 UTC by DK_Dennis
Modified: 2012-01-08 08:57 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments
contains 3 files: CLI.txt, tags.jpg and lmstags.jpg (42.38 KB, application/zip)
2012-01-08 08:44 UTC, DK_Dennis
Details

Note You need to log in before you can comment on or make changes to this bug.
Description DK_Dennis 2012-01-08 08:44:16 UTC
Created attachment 7602 [details]
contains 3 files: CLI.txt, tags.jpg and lmstags.jpg

I'm currently coding a small cross-platform application for catalogging tracks
and albums from an LMS server.

During this work, I've stumbled over what seems to be a bug in LMS.

As of writing this, I've only tested on LMS 7.7.1, running on a 64-bit opensuse
10.4 server.

The error:
When querying the JSON interface, I get the last "composer" tag as "artist",
when querying for tracks.

In other words: if the music file has composer(s) tagged, this gets set in LMS
as "artist" for the track, when using the JSON interface.

I've tested querying both with "a", "A" (and both) as tagged parameters "tags"

The file is seemingly properly tagged; see the screenshot from puddletag
(attached; tags.jpg).
(In order to troubleshoot, I've changed the composer names to Composer1, -2 and
-3. At first, I had only two composers tagged; then "Composer2" was reported as
artist.)

Taking a look in the sqlite library.db (attached screenshot; lmstags.jpg),
album artist and track artist (roles 5 and 6) made it into the database as
expected.

Still, when querying the JSON interface, I always get the last "ComposerX" as
artist.
The attached file, CLI.txt shows output from the JSON interface. 

I believe that this phenomenon is maybe also responsible for the Bug 13284,
since the players in question are probably using CLI/JSON for communication
with the server.


I should think the information here is enough to both reproduce - and hopefully
find and fix the error.
Should you, however, need more (or clearer) information from me, please do not
hesitate to contact me for further information.

Kindest regards, and thanks for the Squeezebox/LMS software :)

Dennis Hestbech