Chondog wrote: ↑Thu Jan 03, 2019 2:32 pm
I am asking about "bulk sync" as you referenced, particularly #1 ("this control enables sync of GPM track locations and hidden ID into your matching MM tracks") So, what does that actually do to the matching MM tracks?
Basically, up to this point (pre MM5), I've been trying to manually maintain the same tracks in both MM4 and GPM. However, my tags are only really cleaned up and maintained in MM. Thus, I don't understand what the syncing back to the MM library from GPM does to all of that information. I wouldn't want to overwrite "Rock and Roll All Nite" (in MM correctly) with "Rock and Roll All Night" (in GPM incorrectly). Does the process allow me to review each track it brings in from GPM to MM?
As I understand it, each of those numbered controls on my diagram control a different component of what we call a "sync".
MM already knows how to find your local tracks ... ie. it knows the path for each track
If you have a duplicate copy of tracks up in GPM, MM doesn't know the GPM "location" for each track ... this means MM cannot play the track from GPM ... and it cannot make a playlist which could be played against your GPM library
Control #1 allows you to import the GPM track "location", for all tracks where MM5 can tag match a MM track to a GPM track ... at the end of this process MM will know both the the path to your local version of the track, AND the GPM internal ID and path where Google has stored your track
the image I posted yesterday had #1 unchecked ... this was wrong, which maybe why you are confused ... I have updated the image.
https://www.dropbox.com/s/6p9q1sh9t9len ... l.png?dl=0
So with the controls set as illustrated above ... for tracks where MM can match GPM to local tracks, the MM db is updated; local tracks are updated with the GPM track locations .... NO extra tracks are imported into GPM ... NO .mp3 files are downloaded ... and your MM db and local tracks are NOT updated with tags from your GPM library
Control #4 is the one which triggers MM to update your MM db (and presumably you actual local tracks themselves also) with tags from GPM ... they haven't said which tags are updated
I don't imagine that I would ever use this ... and IMO it should come with a health alert.
I think that is for someone who has backed up their local tracks to GPM or Dropbox or One Drive, etc
Control #4 would allow them to restore their local tags from backup if their local copy ever got screwed up somehow.
I presume that is what it is for. .... I can't see the point of it for GPM though ... GPM is not like other net locations ... ie. an upload to Dropbox is just a simple file copy ... Dropbox don't screw around with what you have uploaded ... an upload using Googles Music Manager can reduce the size of the upload task by populating your library with Google's own copies of your tracks ... ie. not actual upload required ... it helps you, and probably helps them, because they don't have to store multiple copies of the same track ... and it looks like they try to make your GPM library more "useful" by upgrading your tags with community consensus tags ... most of the change I have seen is in the genre tags ... so a tag sync from GPM is not desirable IMO, because your GPM tags are a muddy soup, make from who-knows-what?
Also, as you say, you may have done re-tagging corrections to your local copy, which you didn't sync to GPM
btw, It is a different situation if you used MM
to do the upload, and syncing, to GPM ... in this case, he wrote the track, so you know that it is your file, with your atgs ... also GPM just store a basic set of track tags ... nothing fancy like Conductor or Involved People, etc ... but Ludek also uploads some, or all, of the extra tags ... so in this case a tag sync from GPM->MM may have a useful purpose if your MM db gets corrupted etc ... I presume that GPM doesn't mess with the files that he uploads, but who knows ??
I have never tested it ... I would want knowledge, and control over, which just tags he was syncing, before I even considered it.