Day to day usage: LFM mode

This illustration shows AlbumPlays running in Last.fm mode; which is where you receive all of your track plays from Last.fm.

Background: see here for a comparison of this operating mode, versus Spy mode, which is available for Sonos owners only. In that other mode non-Sonos plays are sourced from Last.fm, but the Sonos plays are detected directly from the Sonos zones themselves.

Sonos owners may use Last.fm mode if they wish, provided that they have their Sonos configured to scrobble to last.fm.

The steps and facilities used to operate the main features of this application are the same as those used to initially seed the database with your historic Last.fm scrobbles. The difference is that you are now getting your new scrobbles, rather than your scrobble history.

nb: seeding your database is optional, but at some point you should read the database seeding sections of the User Guide, as those
instructions and tips are not repeated elsewhere in this User Guide.

The main processing cycle for AlbumPlays is controlled by the Express Wizard, which offers two actions:

  • GET action – download the latest batch of fresh scrobbles from Last.fm
  • Approve action – match the fresh scrobbles against your MediaMonkey database, and provided that there are no mismatches, update MediaMonkey play counts and date-last-played information

The wizard monitors your position in the processing cycle, and when you have completed one action, it will advance you to the next. You may override the default position, to run successive Get actions without fear of overwriting any scrobbles.

An illustration of the application in use

Ready to run the GET action

The Wizard is poised to run the Get action. Press the Run button.

The GET action is in progress

A run log window opens, and the Get action commences. The log window has a white background while the task is running. The download automatically gets only “fresh” scrobbles, ie. your new plays.

The log window turns black once the download has completed, and a run summary dialogue box is displayed. If it includes the blue “info” Windows icon (as shown on this illustration), the run completed without incident, and there is no need to review the log.

The GET action has completed

The Status Report shows a summary of the fresh scrobbles. They are all unmatched at this stage, as they haven’t yet been processed against the MediaMonkey database.

The Status Report showing a summary of unprocessed fresh scrobbles]

The Wizard has advanced to the Approve action. Press the Run button again. The Approve function performs the following tasks:

  • matches the fresh scrobbles against your MediaMonkey database
  • handles any mismatches, as described and illustrated, in the Seeding Your database section of the Getting Started User Guide
  • checks for any lost scrobbles (details here)
  • if there are no mismatches, and no suspected missing track plays, it accepts the batch of scrobbles, and updates MediaMonkey (track and album play counts, and also the date last played columns) … and the wizard resets to the Get action

Wizard has advanced to Approve action

In this illustration there were no unmatched or missing tracks, so we have another run summary dialogue box with a blue “i” icon indicating that the batch of fresh scrobbles has been fully processed.

Approve action has run successfully

When you press the OK button to dismiss the Run Summary, the Wizard will advance ready for the next Get action.

Back to the GET action again

Once you have been using AlbumPlays for a while, you will have built up a set of rules to handle any cases where Last.fm is in disagreement with you, regarding how your tracks should be tagged. This should mean that you mostly get a clear run, as illustrated above.

Scrobble Mismatches

If you do get some new mismatches, AlbumPlays does much of the heavy lifting for you.

Mismatches may be due to a variety of causes, which are discussed here. AlbumPlays has tools to detect and correct mismatches. Any fixes which you accept or make yourself, are retained, and automatically re-applied against any future unmatched scrobbles, avoiding future problems. … If a few unresolved mismatches remain, after you have made all of the fixes that you feel are worthwhile, you can force-close the batch of fresh scrobbles. Any remaining unmatched scrobbles will automatically be discarded.

If Last.fm begins to enforce a new auto-correction to one of your tracks, the simplest fix is often to just re-tag your track, and then re-run the AlbumPlays Approve action. This will re-audit and complete processing for the batch.

If you prefer your own tags, AlbumPlays has facilities to help you compensate for the mismatch. The following illustration shows some of the ways that AlbumPlays helps to you to create a rule to correct the mismatch from this, and also any other future, plays of the track (the following numbers refer to that illustration):

Handling mismatches

  1. I have an album which was once tagged as Europe ’72 [Bonus Tracks] … AlbumPlays has detected this old scrobbled tag, and auto-corrected it to my current tag, which is just Europe ’72
  2. The scrobbled artist was tagged as The MG’s … AlbumPlays has detected and auto-corrected this to my current tag of Booker t. & the MG’s
  3. This example shows that AlbumPlays doesn’t always get it right. My track’s artist is tagged as Charlie Haden, but looks like it was once tagged as Egberto Gismonti. … In MediaMonkey I do have two albumartist tags for that album; Charlie Haden, and also Egberto Gismonti, separately. … AlbumPlays has defaulted the “correction” to one of the correct choices for the album, but it is the wrong choice for that track. The mismatched will persist as it not be corrected by this rule. To correct it I will need to manually adjust the “correction”, but clicking on the row’s drop down control, and select the other available choice, which will be Charlie Haden
  4. This row illustrates how AlbumPlays usually assists by providing a drop-down list of valid options for each mismatch. … I had altered the album tag for one of Howard Shelley’s albums after it had been scrobbled, so the scrobble’s album tag was mismatched. … AlbumPlays has been unable to find a close enough candidate to be confident, but it has loaded the drop-down list with all of Howard Shelley’s album titles, as you can see in the illustration. I only need to select the correct album from the list.
  5. I do have some albums by Marc Johnson, but not that album. I played and scrobbled that track from a streaming service. … If I just ignore the mismatch, the scrobble will be rejected, which is the correct action. However if I mark the album as being streamed, as shown on the illustration, AlbumPlays will remember that I don’t own the album, and will automatically and silently reject any further unmatched scrobbles from that artist|album

As you can see, you get the opportunity to review the auto-corrections generated by AlbumPlays. You may reject or alter any suggested correction. If AlbumPlays has been unable to offer a auto-correction, you may select your own from the drop-down combo-box, or may type in your own correction using the keyboard.

The rules shown in the above illustration are at the album level, so the one rule corrects all tracks from the album. There is a companion facility which offers the same facility at the individual track level.

next step: Unmatched, Lost, Resurrected, Duplicated & Streamed scrobbles

back to top: Last.fm mode index