View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0016673 | MMA | Synchronization | public | 2020-05-28 23:38 | 2020-06-03 15:19 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.3.9 | ||||
| Target Version | 1.3.9 | Fixed in Version | 1.3.9 | ||
| Summary | 0016673: On upgrade to 1.3.9: Playlists fail to update | ||||
| Description | Upon upgrading to build 922 from 921, and initiating a sync --> playlists failed to update correctly The tracks in the playlists appear to sync (there are 470 tracks in 'Tracks' roughly matching to the selected tracks), but the playlists on the device don't display the synced tracks. e.g. 80's and 90's 3+: contains 90 tracks even though the auto-playlist has 100 (random track) ! Good stuff 3+: contains 5 tracks even though the auto-playlist has 30 tracks (random track) ! Good stuff 4+: contains 14 tracks even though the auto-playlist has 100 tracks (random track - refresh all) ! Hebrew Good Stuff: contains 170 tracks (limit is set to 250 tracks, but there are only 170 that match the criteria, so it matches correctly) Marvel DC: contains 36 tracks (it's a regular playlist and matches correctly) New pop 2.5+: contains 48 tracks even though the auto-playlist has 50 tracks (selected by Rating-highest) MMA Log: QAYDZGGUML Could this somehow be caused if MMA 921 was installed via the store and 922 was installed manually? | ||||
| Additional Information | Tested on a pixel 2 XL running Android 10. | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Fixed in build | 923 | ||||
|
|
Note: after changing the search settings back to 'Ignore diacritics', and attempting to sync, this issue was _not_ resolved. |
|
|
Analyzed the MM5 log and see that e.g. for "New pop 2.5+" all 50 tracks have been included on the sync list. .. MMA downloaded some tracks ... MMA asked for list of the playlists and MM5 served these 6 playlists: 80's and 90's 3+ Good stuff 3+ Good stuff 4+ Hebrew Good stuff Marvel DC New Pop 2.5+ ... later MMA requested content only for two of those playlists: - Good stuff 4+ (100 tracks) - Hebrew Good stuff (170 tracks) 1) MMA has not requested e.g. content of "New pop 2.5+" for some reason, could be because of an older timestamp? 2) To be found why "Good stuff 4+" has only 14 tracks in MMA (acording to Rusty) when MMW served 100 tracks ? EDIT: At the end of the sync I see that MMA sent <SyncSummary succeed="0" ... This means that MMA has an issue and terminated the sync probably while updating the playlist "Good stuff 4+" @Martin: please try to look why MMA sent <SyncSummary succeed="0" |
|
|
80's and 90's 3+ Good stuff 3+ Marvel DC New Pop 2.5+ "Remote playlist is not newer. Update only sync time" Good stuff 4+ 1 playlist media were not found: Harlem Shuffle Playlist Good stuff 4+ updated (99 tracks) During the wifi sync, the playlist Playlist "Good stuff 4+" was updated up to 99 tracks. (one missing track is reason why MMA sent <SyncSummary succeed="0" ... ) Unfortunately, after that, the playlist was updated from the Android media store back to 14 tracks. I will analyze why. |
|
|
This one might be related: https://www.mediamonkey.com/forum/viewtopic.php?f=21&t=96475 |
|
|
OK, so the main issue is that Android media store versions of the playlists fails to update and subsequently overwrites the MM versions of the playlists in MMA. IMHO: The best and most safe way would be if media store version of a playlist _couldn't_ overwrite MM playlist at all. I undestand that editing MM playlists in another Android app wouldn't work then, but that is a minor issue agains the risk that any third party app on Android can damage/clear MM playlists this way!! As for the missing track "Harlem Shuffle", I see that MM5 served it as stream to \\192.168.0.147\Qdownload\Decades\Decades - 50s 60s 70s 80s 90s [22 Albums] - Part 1 of 3\60s\Hits Of The Sixties\Hits_Of_The_Sixties\Cd2\07.mp3 MMA failed with "SocketTimeoutException: Read timed out", so it looks that \\192.168.0.147\ was just temporarily unavailable. |
|
|
Fixed in build 1.3.9.923 |
|
|
Verified 923. |
