Using your Google play library as a target

AlbumPlays can publish and refresh playlists to your Google Play Music library. The general features & benefits of AlbumPlays playlists are described here

The aim of AlbumPlays’ Google support is to enable you to easily publish, and refresh, the contents of your MediaMonkey playlists into Google Play Music playlists. … and the reason for that is because the Google playlist facility is horrible, and the MediaMonkey facility is great.

An implication is that the playlist tracks already need to be in both your MediaMonkey database and your Google library. Usually, but not always, these will be your own tracks, where you have taken advantage of Google’s free offer, allowing you  to upload up to 50,000 tracks from your collection.

AlbumPlays support of Google library targets is currently limited to just a single Google account; ie. you can only publish AlbumPlays playlists to just one Google account.

Some preparation is required before your Google Play library may be used as a target by AlbumPlays:

Index:

Provide access credentials to your Google Play library

The household member wishing to publish playlists to their Google Play library, needs to:

Although AlbumPlays allows multiple household members to provide their Google credentials, currently just a single listener may use AlbumPlays’ Google library support, ie. the one whose Google track IDs have been imported by the following step.

Import Google’s track IDs from your Google library

  • when you upload your tracks, Google assign their own ID’s to your tracks
  • or when you add Google’s version of a track which you also own, to your Google library, Google retains their own ID for the track

Before AlbumPlays can place one of your tracks into a Google playlist, it needs to know the Google ID for the track.

This is achieved by AlbumPlays importing the dictionary of all tracks from your Google library, and then matching those dictionary entries against the tracks indexed by your MediaMonkey database. This matching task is achieved by comparing the tags (Album, Track, Artist & AlbumArtist names) in your Google library against those in your MediaMonkey database.

The size and difficulty of this task will be somewhere within a range from a simple fully automated process, to requiring quite a lot of work for you to do. The point at which your library sits within this range depends upon:

  • the size of your Google library
  • the degree of conformity between Google’s and your track tags
  • the amount of tracks, which you don’t own, that are included in your Google library … these tracks will not be in your MediaMonkey library, so we don’t need them, but the issue is that a great number of such tracks, which can never be matched against your MediaMonkey database, may obscure those of your own tracks which would match except for some tagging difference between your version and Google’s

Tracks which you have uploaded to Google should match the easiest, unless you have done significant re-tagging in one, or the other, of the platforms.

AlbumPlays employs fuzzy logic during the matching process to assist with small tag differences. It also has quite a few tools to assist with resolving tag differences which defeat the fuzzy logic.

The matching tools are described here and here, where they are documented for the purpose of importing historic scrobbles to seed AlbumPlays’ play history. You need to read those User Guide sections if you have mismatches to deal with.

The steps to complete the import & matching process are as follows:

a. Firstly, supply credentials to your Google library as described above

b. Put AlbumPlays into a special Google import mode via the Set Options button

Set Options button

Google ID mode
Type your AlbumPlays Listener ID (select from the ID’s listed at the right)


c. Run the GET action while in Google ID mode

Google ID mode: Get action
Press the Run button
get encryption phrase
]10 You will need to resupply the phrase which was used to encrypt the stored copy of your Google account credentials

A white log screen will open while the track dictionary is being imported. It will go black when complete, and a message will be displayed showing your Google library track count.


d. Match the Google track dictionary against MediaMonkey

AlbumPlays has progressed to the APPROVE action, Press RUN again

This step will attempt to match your Google tracks against your MediaMonkey tracks.

If everything matches, the Google IDs will be recorded into the AlbumPlays database, and this step will be completed.

But the most likely situation will be that there will be at least some unmatched tracks, in which case the Approve action will pause to allow you to deal with the mismatches


e. Deal with any mismatched tracks

Use the AlbumPlays tools described here, and expanded upon here, to address the mismatches which you care about.

The general advice is to:

  • process album-based rule templates first; you may be able to fix all tracks from the album with just the one action
  • rule templates for mismatched albums are sequenced by descending album size .. this is so that you can deal with full albums while you still have energy, as it pushes to the back any mismatched sole streamed tracks that you have added to your library …. nb: albums where neither the album artist, nor the album, are found in your MediaMonkey library, have been flagged as being streamed, and are already filtered from view
  • if you mark albums, which you are sure that you don’t own, as being “streamed”, when you run your next Approve action, those marked albums will be removed from view, making it easier to focus upon albums that you care about
  • if there are many mismatched albums, the rule templates are presented in batches to save from exhausting either you or your computer
  • view all album-level template batches (“Next” -> “Next” -> “Next” … until “Finished”) … skip past each without reading if you want, but make sure to press The “Update” button at the bottom of each, as this will approve the fuzzy logic pre-selections
  • when all album-level templates batches are “updated”, Press the Run button again, to retry the *Approve” action … this will apply any of your entries, along with the approved fuzzy logic suggestions … the count of unmatched albums should decrease

  • maybe run through this twice, and then proceed to track-based rules

  • much the same process … don’t worry too much about streamed tracks … the main thing is to accept all fuzzy logic suggestions by Updating each batch

  • also make as many manual adjustments as you can be bothered with …. sometimes the best approach is can be to adjust your MediaMonkey tag to agree with Google … but take care if you are already using AlbumPlays to import your scrobbles from Last.fm or Sonos units … you need to take the potentially conflicting situations into account, ie. Last.fm tags vs Google tags vs MediaMonkey vs AlbumPlays (see here)

  • you can always come back later to add further matching rules later… you would need to run all steps again, starting with re-importing the track dictionary, but all of the rules, which you have already created or approved in this step, will be retained, and pre-applied

  • force close the batch when you are done

force close the batch
Force close the batch by checking the “Ignore” checkbox, the press the Run button one last time

The Google ID’s for all matched tracks will be stored into the AlbumPlays database, and the ID’s for any unmatched tracks will be discarded.

Assign your AlbumPlays playlist(s) to your Google library

assign the playlist to a Google account
For instructions [see here for MM playlists]13, or here for native playlists

Although AlbumPlays currently can only publish to a single nominated Google account, you need to update any playlist that will be used to publish, advising which Listener’s Google library it should use.



Associated links: