The following is not the case yet:

Multiple scrobbles may be sent in a single batch request, this is recommended when there are cached scrobbles to be sent in the case of previous errors. A batch request may contain up to 50 scrobbles.

Must do.

Hey,

I've been experiencing troubles scrobbling Tracks to Last.FM. I think that this might happen due to changes in the Last.fm API.

Inside the function

- (NSOperation *)performApiCallForMethod:(NSString*)method
                                useCache:(BOOL)useCache
                              withParams:(NSDictionary *)params
                               rootXpath:(NSString *)rootXpath
                        returnDictionary:(BOOL)returnDictionary
                           mappingObject:(NSDictionary *)mappingObject
                          successHandler:(LastFmReturnBlockWithObject)successHandler
                          failureHandler:(LastFmReturnBlockWithError)failureHandler {

an example postCall to the Last.FM API looks like:

curl -X POST -H "Accept: application/json" -H "Cache-Control: no-cache" -H "Postman-Token: da56adfd-0553-0ac7-7da6-512738e91be2" -H "Content-Type: application/x-www-form-urlencoded" -d '' "https://ws.audioscrobbler.com/2.0/?album=&api_key=4cf8b0679f46df8d758b2561bfe1df74&artist=Magic!&duration=-187&method=track.scrobble&sk=*removedThisAccessToken*&timestamp=1485257969&track=Rude&username=takethefake&api_sig=17fcd67e6fde705f830369e70d141b54"

notice: removed my sk from the request above

this looks legit to the API but the answer is the following:

<?xml version="1.0" encoding="utf-8"?>
<lfm status="ok">
    <scrobbles ignored="1" accepted="0">
        <scrobble>
            <track corrected="0">Rude</track>
            <artist corrected="0">Magic!</artist>
            <album corrected="0"></album>
            <albumArtist corrected="0"></albumArtist>
            <timestamp>1485257969</timestamp>
            <ignoredMessage code="1"></ignoredMessage>
        </scrobble>
    </scrobbles>
</lfm>

as I searched the Last.FM Docs why this error occurs I came up with Filtered Request and that the ignoredMessageCode leads to errors with the Artist. I experienced the same Error with different Tracks of different Artists.

I'm not sure how to we can fix this.

On building with Xcode I'm getting an error.

ld: library not found for -lPods-SBShazamScrobbler clang: error: linker command failed with exit code 1 (use -v to see invocation)

Any ideas what could be the issue?

Just downloaded ShazamScrobbler (Version 1) for Shazam 1.1.1 but I'm not able to sign-in.

Best would be a toggle button.

I'm using version 1.2.1 with Shazam 1.2.0 on Mac OSX Sierra.
App appears to be pulling data from Shazam and interacting with Last FM (in that scrobbles show in-app with usual red or grey circles alongside)
But when I check my profile on Last.FM, the tracks listed in ShazamScrobbler aren't there.
I should mention that I have this exact problem with another 3rd party scrobbler on my iPhone.
In both cases, the tracks appear to have been scrobbled because the apps indicate successful output, and some interaction with Last.FM looks like it has been achieved. However, for whatever reason, the tracks don't end up in my plays history on my Last.FM profile.

I don't know where to ask this question since I can't find anything about auto-shazam on mac online besides the mac support page, which isn't helpful. But I'm wondering if there is a way to turn on auto-shazam on mac and have this app work with shazam?

What to do when Shazam detects a song being scrobbled by another scrobbler?

Suggestion:

• check if Last.fm is already "Scrobbling from X",
• or check if the song has already been scrobbled in the last 5 minutes.

Basically the goal of this enhancement is to let ShazamScrobbler open:

• even if we are scrobbling from somewhere else,
• without scrobbling the songs twice.

C'est de la GROSSE merde

The app should be able to:

• access the Mac notification center and disable the Shazam notifications,
• send the same notifications as Shazam, but with an unscrobble button inside the notification.

Hi, can you tell me how to run this app in Mac OS X?

Shazam Scrobbler is excellent, but one thing it is lacking is not submitting the album of the song to Last.fm with the scrobble. I know Shazam probably doesn't provide this information since a song doesn't need to be tied to an album, but I noticed that when a song is scrobbled on the Shazam app, an Apple Music link is provided:

That Apple music link could be scraped to determine the album title, which in turn could be submitted to the Last.fm API when the track is scrobbled.

The reason this is important is because, although in Last.fm the scrobbled song counts towards artist scrobbles and individual track scrobbles, it does not bump your album scrobbles of that track.

Thanks!

This is a known issue, please keep using ShazamScrobbler-1.2.0 if you don't use macOS Sierra!

I am running MacOS Monterey 12.1 and I am unable to log into Last.FM via the Shazam Scrobbler. See attached photo for the error. I have verified my username and password are correct.

The menu says "Enable scrobbling (108 songs awaiting)".

I'd like to enable scrobbling whilst listening to a CD, but don't want it to scrobble all those songs from TV it picked up.

As online/offline mode #17 isn't implemented, is there a way to clear the whole queue?

If I just let it scrobble them all, it'd be difficult and take a long time to go back through my Last.fm profile to try and find them and delete them one by one.

Thank you!

Suggest the user to:

• set the preferred song list size
• set the preferred scrobbling time (30 seconds being the minimum)
• show/hide unscrobbled items

I can only get new songs to scrobble if I toggle "Enable Scrobbling" on and off. if I don't, new songs scrobble in the mac app, but don't appear in the ShazamScrobbler or in my last.fm scrobbled tracks. Anything I can do to fix on my end?

I just got hit by a radio station playing lots of snippets of songs in succession.

At least one method of validation is not to scrobble until at least 30 seconds have elapsed. If a new track has come in from Shazam in those 30 seconds, then don't scrobble.

You can (and it'd be a great addition) to send a now playing notification as soon as a track starts playing, but wait on the scrobble one until later.

For reference:

For every track a user listens to the client should send a track.updateNowPlaying request and a track.scrobble request. ...

The "Now Playing" service lets a client notify Last.fm that a user has started listening to a track. This does not affect a user's charts, but will feature the current track on their profile page, along with an indication of what music player they're using. ...

A track should only be scrobbled when the following conditions have been met:

• The track must be longer than 30 seconds.
• And the track has been played for at least half its duration, or for 4 minutes (whichever occurs earlier.)

As soon as these conditions have been met, the scrobble request may be sent at any time. It is often most convenient to send a scrobble request when a track has finished playing.

http://www.last.fm/api/scrobbling

Hej!

How about a version for iOS?
I'm using an iPad when I'm listening to Vinyl (to browse my catalogue with Discogs and decide what to listen to next). And I would love to use the iPad to scrobble the playing vinyl.

Greetings

PS.: Windows 10 Version would be awesome, too...

This message appears when launched. Any song is detected.

http://stackoverflow.com/questions/2808016/how-does-apple-update-the-airport-menu-while-it-is-open-how-to-change-nsmenu-w

How about a version for Windows 10? I just learned that there is a new Shazam desktop app for Windows 10, so enabling scrobbling with it would be great: https://support.shazam.com/hc/en-us/articles/212932127-Shazam-for-Windows-10-version-4-6-now-on-PC-

No longer builds in 10.10
(it would be really nice if a binary was provided... just saying.)

Heya, you're not planning to make the app backwards-compatible with Mavericks, are you? I'm asking because that's (10.9.5., to be more precise) what I'm still using on the machine I listen to internet streams from.

I could get the most current version of ShazamScrobbler installed without problems, it also recognises songs (! they are listed as queued now), but none of the elements in the login window show up (i.e. it's just a 'blank' grey window, no input fields for user/pass, no logo), so I can't actually scrobble the tracks.

Thanks for ShazamScrobbler, it seems really useful!

Probably more of an enhancement than a bug report.

1. Uncheck "Enable scrobbling"
2. Listen to some music so Shazam detects it
   -> It's shown in ShazamScrobbler, but with no Last.fm logo next to it
3. Stop playing the music.
4. Check "Enable scrobbling (1 songs awaiting)"

Actual result:
Track is scrobbled.

Expected result:
Track not scrobbled.

At least personally, I would like the option of being able to use Shazam for recognising songs but not want then scrobbled. I know I can quit ShazamScrobbler, and then reopen it later, but it'd be more convenient to be able to just switch scrobbling enabled/disabled from the application. (I'd probably forget to re-open it afterwards.)

I suppose the current enable/disable option is more of an online/offline option. I can see the benefit of this too, but being able to set it to just ignore tracks for a while would be great.

What do you think?

Thanks!