simon-weber / gmusicapi

An unofficial client library for Google Music.
https://unofficial-google-music-api.readthedocs.io
BSD 3-Clause "New" or "Revised" License
2.48k stars 257 forks source link

[Feature request] "Use Suggestions" on Entire personal Library #314

Open RASMiranda opened 9 years ago

RASMiranda commented 9 years ago

Google has been improving quite a bit the "Use Suggestions" Feature when Editing the Album Information. So that means, that a lot of the Music uploaded since the "beginning of time" doesn't have the better information associated with album (names, year, genre, album cover image quality, etc). I was thinking about some way to automate the process, that can be dreadful if you try to update by hand all the albums you have. First was thinking of some kind of javascript extension plug-in. But did some googling and yours API popped right way (congrats btw, looks very good).

To conclude, do you think it would be easy to implement this kind of functionality (Use Suggestions for entire library, or artist or genre or etc)? It would probably fit in Webclient Interface. Additionally any guidelines of where I could start to try to implement the functionality on the API would be most welcomed :)

simon-weber commented 9 years ago

I haven't really looked into this, but I suspect "use suggestions" just means copying metadata from their store database when they were able to match it. That'd be pretty straightforward, but #224 blocks it.

RASMiranda commented 9 years ago

Ouh too bad, when updating the metadata i could even use a better source than the store. Is it remotely possible to workaround #224? Any tips of where to start to try and fix it?

simon-weber commented 9 years ago

229 mostly worked at one point; the only blocker was the webclient/mobileclient mismatch on metadata keys. If that endpoint is still around you could do that conversion yourself and it should work.

RASMiranda commented 9 years ago

I was looking at the code for change_song_metadata, and see that BatchMutateTracks and think that the endpoint is https://mclients.googleapis.com/sj/v1.10/trackbatch, where can I find the specification online? Googling got me nothing.

thebigmunch commented 9 years ago

There is no specification. The Google Music API is not really a public one. Endpoints are mainly found through traffic monitoring and then reverse engineered. Fiddler is a common tool for finding calls and responses.

Lapayo commented 9 years ago

Any news on this feature? Is change_song_metadata working again and is there a call to get the suggestions for a given song?

simon-weber commented 9 years ago

Any news on this feature?

Not that I know of. Following this issue is the best way to get updates.

valerianrossigneux commented 8 years ago

that would be awesome feature !

Charlie37 commented 7 years ago

Yes, this would be a very cool feature :)

hcwjcasey commented 7 years ago

Any update on implementing the updating of metadata with "Use suggested"

simon-weber commented 7 years ago

No updates; sorry.

bfaure commented 7 years ago

pls

simon-weber commented 7 years ago

As far as I know, the mobileclient still doesn't allow changing metadata. There's not a great way to implement this without that.

freeslugs commented 7 years ago

seems like you can change the song metadata. idk about using suggetions yet.

https://unofficial-google-music-api.readthedocs.io/en/latest/reference/mobileclient.html#gmusicapi.clients.Mobileclient.change_song_metadata

simon-weber commented 7 years ago

Sorry, the docs for that note that it doesn't work on any fields but rating:

Currently, only the rating key can be changed. Set it to '0' (no thumb), '1' (down thumb), or '5' (up thumb).

This is unlikely to be something we can do unless Google makes changes on their end.

chincherpa commented 5 years ago

also wishing for this feature...

any news here?

rrhobbs commented 4 years ago

Yes, please!

Scott-G commented 4 years ago

I vote for this too. Not looking likely now though :-(