Is submission_client getting ignored when using old AudioScrobbler API?

ListenBrainz
1

Hello,

I have been scrobbling from LMS for a couple of years now using a custom made plugin based on the Audioscrobbler plugin which is using the AudioScrobbler API.

The plugin is sending submission_client/submission_client_version:

use constant CLIENT_ID => main::SLIM_SERVICE ? ‘snw’ : ‘ss7’;
use constant CLIENT_VER => ‘sc’ . $::VERSION;

my $url = HANDSHAKE_URL
. ‘?hs=true&p=1.2’
. ‘&c=’ . CLIENT_ID
. ‘&v=’ . CLIENT_VER
. ‘&u=’ . $params->{username}
. ‘&t=’ . $time
. ‘&a=’ . md5_hex( $params->{password} . $time );

However this info seems to be ignored. When inspecting the listen, the additional info does not seem to contain any client info, e.g.:

    "additional_info": {
      "rating": "",
      "recording_mbid": "a9cff012-ceac-41fe-abcb-66a6b21436c5",
      "recording_msid": "4ba76552-342a-44c0-aa71-773c07b8e1d9",
      "source": "P",
      "track_length": "305",
      "track_number": "9"
    },

Is there something I am missing in order to have client info submitted successfully?

Thanks!

1 Like
3

Hi @amatala,

The old Audioscrobbler API is deprecated, and I suspect the client and version were never implemented for it (it was only added as a suggested field in the ListenBrainz API maybe 5 years ago)

Judging from the code, I don’t see any parsing of v or c parameters, so I think thye are just ignored.

Is LMS Logitech media server? If so, there might be a better option to submit to ListenBrainz: Lyrion now supports ListenBrainz scrobbling - #2 by Paul_Webster

In any case, I’m happy to help you figure out a way to use the regular API, if possible, that works with your setup.
Let me know.

2 Likes
4

Hi @mr_monkey,

Thanks for your response and for confirming my suspicion that those parameters are indeed getting ignored.

I am still using an older version of Logitech Media Server because there are custom changes I have written over time for some specific needs.

Lyrion does indeed support ListenBrainz scrobbling starting with version 9.1 which is still in beta. I did a quick check and at this time the new Lyrion plugin is still using the Last.fm API by default. The ListenBrainz API can be selected but it’s still experimental so maybe not fully tested yet.

In the ListenBrainz API the client info should be properly taken into account, this is the new code:

my %additional_info = (
media_player => ‘Lyrion Media Server’,
media_player_version => $::VERSION || ‘’,
submission_client => ‘Lyrion Media Server’,
submission_client_version => $::VERSION || ‘’,
);

For now I will be waiting for the Lyrion plugin to get finalized and switched to the new API by default. Once they consider the code to be stable enough to be part of the official release, I’ll have a look to include the new code in my own plugin (or maybe switch to Lyrion altogether?).

As mentioned, this has been working fine as it is for several years (except for the client info which is getting ignored) so it is not a priority for the moment, I just wanted to know if there was any quick fix for this. :slight_smile:

Thanks again!

2 Likes
5

There is no active work on the ListenBrainz integration in LMS.

It is considered completed.

I doubt that the LMS last.fm integration will be changed from its use of the legacy API - at least it is not something that I have seen being discussed.

The ListenBrainz integration could relatively easily be back ported to LMS 9.0 but I suspect it would need a lot of people to clamour for it to be done and there is no sign of that. 9.0 should be only bug fix updates nowadays.

1 Like
6

Thanks! I assumed that “Experimental” meant some kind of early pre-beta phase which was still getting improved upon (especially that ListenBrainz scrobbling support is not even part of the latest official LMS version yet).

I have been scrobbling to last.fm from LMS since 2008 and it has always been working flawlessly. A couple of years ago, in 2022 or 2023 I wanted to start scrobbling to ListenBrainz from LMS. I have been an active MusicBrainz contributor since 2008 and still trying to submit all releases from my collection to MB whenever they are not known yet, so scrobbling to ListenBrainz seemed like the logical thing to do. The easiest way to achieve that was by creating my own copy of the Audioscrobbler plugin and modify it to submit to ListenBrainz instead of last.fm via the legacy API.

Again, this has been working flawlessly ever since, only recently I have realized that client info was getting ignored. Of course, this is no big deal, just a nice to have thing, but I understand no one will spend time and effort improving the legacy API. As long as scrobbling via the legacy API is working fine, there is no real issue. :slight_smile: