View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0015314 | MMW v4 | Synchronization | public | 2019-01-07 23:53 | 2019-01-11 16:07 |
| Reporter | peke | Assigned To | |||
| Priority | high | Severity | major | Reproducibility | always |
| Status | assigned | Resolution | open | ||
| Target Version | 4.1.24 | ||||
| Summary | 0015314: Sync: USB Sync calculate wrong sync size in some very specific cases | ||||
| Description | Due the limited storage user select only few tracks and Playlists to sync MMW calculate completely wrong sync size, which result in failed sync. Images of sync settings, total number of tracks and size and log file from sync is uploaded to FTP. NOTE: Music Folder and all other folders that MMW access from Sync Settings on Device are Empty prior to sync and MMW shows 1.9GB of Audio Files and 1.6GB of Other While Report Capacity 1.9GB and 0 Free which is completely wrong. Expected Behavior that on MMW scan it shows 0 Audio/Video/other and calculate Free Size reported-Size to sync | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
In the log I see 426 files on the sync list. There are albums on the sync-list, e.g. whole album "Billboard Top100 Single Charts vom 22 12 2012" was added to sync-list etc. Can you please share C:\Users\Peke\AppData\Roaming\MediaMonkey\MM.DB for analyze? |
|
|
Uploaded to FTP. Sync List should contain only 12 Tracks as shown in pics not 426 that can't fit on device. If you check each selected item you can see that all is same as in supplied pictures. Note: You can also use same MM.DB for testing 0015309 |
|
|
In the original log (SyncLog.LOG) I see that this SQL query: SELECT Albums.ID, Albums.Album, Albums.Artist, SynchAlbum.MaskPath, SynchAlbum.PersonType, SynchAlbum.IDArtist FROM Albums INNER JOIN SynchAlbum ON (Albums.ID=SynchAlbum.IDAlbum AND SynchAlbum.IDDevice=233 AND SynchAlbum.FilterID=7) Returned the albums previously on sync-list (album ids like 19292, 48525, 48597, 60330, ....) resulting in 426 on sync-list. But with your current MM.DB the query does not return anything and the SynchAlbum table is empty. So I suppose that the issue no longer appears? If you still observe the issue with the attached MM.DB then please generate new debug log (including sync and corresponding to the attached MM.DB) ----------------------------------- BTW: Most of the 426 files in the SyncLog.LOG has failed to upload with MTP error, but I suppose this could be because the device was full? Example of successful upload: WMDM: Uploading result, Insert3: 0 (\\192.168.0.250\Download\pyload\Music\Billboard Top100 Single Charts vom 22 12 2012 [Mp3][www.lokotorrents.com]\009 - Justin Bieber ft. Nicki Minaj - Beauty and a Beat.mp3 -> \Music\Unknown\Billboard Top100 Single Charts vom 22.12.2012\09 Justin Bieber ft. Ni - Beauty and a Beat.mp3) Example of the first failure: WMDM: Uploading result, Insert3: 80070070 (\\192.168.0.250\Download\pyload\Music\Billboard Top100 Single Charts vom 22 12 2012 [Mp3][www.lokotorrents.com]\038 - Ellie Goulding - Lights.mp3 -> \Music\Unknown\Billboard Top100 Single Charts vom 22.12.2012\38 Ellie Goulding - Lights.mp3) |
|
|
I created new log and video file for creating 0015309:0052028 logs that both log and video shows MMW tries to Sync 426 tracks instead only 12 (74.6MB) and fill device completely. Added relations as these two bugs are clearly related. |
|
|
As discussed offline, the key factor to replicate the issue is to add an artist that is part of a large multi-artist album and click '[x] Hide unselected items' which expands the artist and makes the multi-artist album checked under this artist node. Then such a album (like 'Billboard Top100 Single Charts vom 22 12 2012') is erroneously synced as whole. Further factors to replicate the issue: - the artist needs to be also album artist of at least one album to replicate the issue (artists that are not album artists are not expandable) - the artist needs to be selected under the 'Artist' node (this node is disabled by default), the issue doesn't appear when the artist is selected under the 'Artist & Album Artist' node Lowering priority (due to the very specific circumstances for the bug to appear)... |
