View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0015396||MediaMonkey 5||Synchronization||public||2019-01-28 10:57||2020-07-22 16:38|
|Target Version||5.0||Fixed in Version||5.0|
|Summary||0015396: Playlists synced to GPM are duplicated when synced back to local library|
|Description||1) create a playlist 'Test1' and put a track into it|
2) check the playlist on the [Devices & Services > Google Play Music > Library Content] page
3) click [Sync now]
=> playlist is synced to GPM as expected
4) check the option '[x] Scan Google Play Music content to the local database' on the 'Remote Content' page
5) click [Sync now]
=> playlist 'Test1' is now duplicated in MM library
|Tags||No tags attached.|
|Fixed in build||2153|
Further issue is that GPM playlists has only 1000 tracks, this seems to be GPM's limitation: https://productforums.google.com/forum/#!msg/play/aEYeLSQqWng/XinPPJXyBQAJ
GPM playlist(s) are synced back to MM as another copy because they have different GUID than the original MM library playlist(s).
This doesn't happen in case of other cloud based sync profiles (MMS, OneDrive, Google Drive, DropBox), because there the playlist (and its GUID) is always created in MM5, so the instances are always the same.
GPM is special also with relation to the limitation to 1000 tracks per playlist. Because of this I guess that it is all right to track the GPM playlists as another instance of original MM playlist (i.e. duplicate), but we should group them under the 'Google Play Music' parent playlist in MM library, so that the origin of such a playlists is clear.
||Fixed in 2153|
Unable to replicate, tested on 10 Playlist even renaming playlist on both MM5 and GPM once paired changes are propagated to MM5.