View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0012689 | MMW v4 | Synchronization | public | 2015-03-30 11:03 | 2015-03-30 21:13 |
Reporter | Ludek | Assigned To | |||
Priority | urgent | Severity | major | Reproducibility | always |
Status | resolved | Resolution | fixed | ||
Product Version | 4.1.6 | ||||
Target Version | 4.1.7 | Fixed in Version | 4.1.7 | ||
Summary | 0012689: A lot of files in /MediaMonkey/artworks/ directory slows down MTP transfer | ||||
Description | As pointed by a user in #JAQ-960-39231 If one checked "Copy Artwork to file tags" and unchecked "sync all Artwork to file folders" then MMW copies all the artwork to the /MediaMonkey/artworks/ directory (because MMA is not read/write tag capable yet (0011794) and cannot read embedded artwork from the file tag) According to the user's experience: 8600+ jpgs in a single folder leads to two problems: 1) Large album art led to a huge amount of space used (~3-4gigs!) 2) 8600+ files in a single folder on a microSD greatly slowed down USB-MTP syncing when MMW tried to write more album art in the directory (sync times for individual files went close to 60sec compared to ~2sec per file at the start of the syncing process). | ||||
Additional Information | #JAQ-960-39231 | ||||
Tags | No tags attached. | ||||
Fixed in build | 1738 | ||||
|
a) we should evaluate whether /MediaMonkey/artworks/ is really needed (MMA can read the thumbs from the Android's media provider AFAIK) b) we should change the cache paths (to eliminate many files in a single directory) so that the cache path would be rather \MediaMonkey\artworks\98\b1\52294ffb.jpg instead of current \MediaMonkey\artworks\98b152294ffb.jpg |
|
Not sure if this is relavant, but one user found that running MMW as admin when syncing solved artwork problems: http://www.mediamonkey.com/forum/viewtopic.php?f=21&t=80394 |
|
b) is fixed in 4.1.7.1728 |
|
b) Verified in 1738 it took longer as at first I was not sure that existing were deleted on resync, but they were. |
|
a) I would keep it as for what I know we are planning to have own tagger. |