View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007565 | MMW v4 | Properties/Auto-Tools | public | 2011-03-22 20:40 | 2011-04-26 23:11 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 4.0 | ||||
| Target Version | 4.0 | Fixed in Version | 4.0 | ||
| Summary | 0007565: Rationalize storage location for thumbnails | ||||
| Description | As described in 0007052: - Big thumbnails (those generated at the size of the video) are stored in C:\Users\<User>\AppData\Roaming\MediaMonkey\Metadata Cache - Small thumbnails (used for AA views and Art Browser) are stored in MM temp folder together with covers cache In the forum, lowlander made a valid point that considering that large thumbnails can take up a lot of space, it might be preferable to store them to a location decided by the user (e.g. temp folder). Since we're already storing small thumbnails there would it make sense to store both there? | ||||
| Additional Information | http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=55666 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1358 | ||||
|
|
On the other hand: if Big thumbnails are stored to the same location as the DB (i.e. if the user-configured DB location also affects where the big thumbnails are stored), then this is a non-issue. Need clarification. |
|
|
I think that thumbnails shouldn't be generated in a temporary folder, since it can be deleted anytime and thumbnail generation isn't a fast process. So generating them in the current folder makes sense to me. As for their size - they shouldn't occupy too much space, particularly after 0007515 is fixed (increased priority to Urgent). So, I think that this can be closed. |
|
|
Does the location of the thumbnails match the settings of the DB? i.e. if a custom DB location is set, should the big thumbnails also be placed in the same location? I'm referring to: http://www.mediamonkey.com/support/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=46 |
|
|
No, it's fixed this way. I don't think it's overly important to make this configurable, we just should test that it correctly works in Portable mode. |
|
|
Per subsequent discussion with Jiri, we should fix this because if the user sets the db to be stored to a certain location, it's because: a) they'd want the data to be stored to a location other than their local drive b) they want the data to be shared among more than one machine If the large images aren't stored to the same location, we're going to break these usecases (particularly the second--shared databases). Summary: we should store big thumbnails to a subdirectory of the location configured to stored the DB (applies to Regular, Portable, and custom configurations). |
|
|
Fixed in 1358 |
|
|
Verified in 1358 that it stores it in the custom DB location as subfolder, although I would have preferred to have seen this customizable by the user. I haven't verified if it does this properly over the network when a network location is used of the DB. |
|
|
Verified 1367 |
