Take the 2-minute tour ×
Web Applications Stack Exchange is a question and answer site for power users of web applications. It's 100% free, no registration required.

I suffered the same problem as Force Google Music Player to refresh album art? but I fixed it manually. That is, downloaded a local copy of the music on my phone and manually updated each MP3's album art. However, the web copy is still bad.

If I "upload" the fixed mp3 files will it update the files rather than upload a duplicate of it?

I don't want to try and have the latter happen and have a huge mess to clean up.

share|improve this question
add comment

2 Answers 2

up vote 2 down vote accepted

ChrisF's answer is mostly correct, but I think it has a subtle error:

If you change the name of the file Google Music will upload a new copy of the file as, as far as Google is concerned, it's a new file.

I don't think this is entirely true. When the Music Manager scans a file, it generates a hash of it (you can find this in the Music Manager local database - it's called the "client id"). Importantly, the hash attempts to depend only on the track's audio, not on filename or metadata tags (further details here).

This means that if you change the tags or filename, the Music Manager should recognize it as a change to an existing file and not create a duplicate.

That said, there are two wrinkles to their solution:

  • the Music Manager doesn't recognize some ways of storing album art (eg if art is stored in a local file, but not in the file tags)
  • the hash isn't entirely dependent on the audio, since tag stripping is done on a best-effort basis. You can see this effect by adding more obscure tags (eg adding an APE tag on the end of the file will result in a different hash, while an id3 tag won't).
share|improve this answer
    
I figured that the checksum would remain the same -- I wasn't sure if the tags were stored in the metadata or the actual file binary, especially considering embedded album art (thus, changing the checksum). But i am changing basic IDv3 tags, so it shouldn't change the checksum, then. Assuming this is the case, Google should be able to update. Thanks! –  WhiskeyTangoFoxtrot Jan 5 '13 at 1:39
add comment

If you modify the music file - retagging, changing the album art, etc, Google Music will update the existing file.

I thought that if you changed the name of the file Google Music will upload a new copy of the file as, as far as Google is concerned, it's a new file. However, that appears not to be the case and the identity of the file is derived from it's contents.

If you are worried about creating duplicates you could always download the file, delete it from Google Play - which doesn't delete the local copy - then update it. This "new" file will then get uploaded.

You can also update the file in Google Play itself without downloading the file. Simply click on the arrow in the bottom right corner (1) and select the "Edit Album Info" option (2):

enter image description here

Then click on the album art itself to change it:

enter image description here

share|improve this answer
    
I need a local copy because Verizon's data coverage in my apartment sucks, so that's not a big deal. However fixing 100+ files' album art through the Web UI is cumbersome, so I used an app on my phone that has a feature to lookup and apply the album art based on the other IDv3 tags you have for the file. Still cumbersome, bet less so. This is helpful though, thanks! –  WhiskeyTangoFoxtrot Jan 1 '13 at 23:49
    
@Jonathan - I added the "in the cloud" fixing option for completeness. –  ChrisF Jan 1 '13 at 23:50
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.