View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001576 | MMW v4 | Synchronization | public | 2004-11-05 06:11 | 2004-11-11 16:28 |
Reporter | rusty | Assigned To | |||
Priority | immediate | Severity | text | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Summary | 0001576: Text changes on H-xxx 'Device Configuration' tab | ||||
Description | Minor tweaks: 1) remove the periods at the end of both config entries 2) change (in both config entries) 'device Library' to 'device library' 3) can you clarify what is meant by 'Rebuild device library only for new tracks' ? | ||||
Tags | No tags attached. | ||||
Fixed in build | |||||
|
Fixed in build 804. 3) When this option isn't checked MM (or to be exact the device plug-in) reads all tracks from device and updates the internal DB according to tags. When the option is checked MM doesn't read tags for tracks that are already present in the DB, i.e. it doesn't update modified track metadata. In this case scanning is much faster, usually almost immediate. |
|
1) and 2) look fine, however, from your explanation of 3) the third pane is unclear. A quick hack (that is still somewhat ambiguous) would be: [x] Update device library after Synchronization . . . [ ] Update device library metadata only for newly added tracks A much clearer description is: On Synchronization: (o) Update device library only for newly added tracks ( ) Update device library for all tracks ( ) Do not update the device library (note: I changed Auto-Synchronization to Synchronization since I assume library updates occur for both Auto and plain Synchronization. |
|
Fixed in build 805. - I changed the options according to your suggestions, but respecting that the the two things aren't related, i.e. they don't appear in a hierarchy. We can discuss further over IM. |
|
I need some clarification: Your explanation of how this works (over IM) was that Re. hierarchy: - 1st option means _if_ MM should update library after Auto-Synch. - 2nd option means _how_ to update the library (in all cases). This led to the current UI of: [x] Update device library after Auto-Synchronization Update device library: (o) Only for newly added tracks ( ) For all tracks This is still confusing to me because this UI implies that: -The device library is _not_ updated after Auto-Synchronization unless 'Update device library after Auto-Synchronization' is enabled -The device library is _always_ updated after Manual Synchronization Why do we give the user the option of choosing to update/not update the library for one case and not the other? |
|
1. Yes, although by default the device library is updated after Auto-Synchronization, user can select not to do so. The reason is that not all users want/need the device library to be present in the device, the library can be used to browse by artist/album/genre in the device and if user turns the feature off in Hxxx, the library makes no sense there. 2. No, I decided not to do anything after manual synchronization for several reasons (we can discuss over IM if you want). If user wants to fill the device manually he can do so, either using MM or anything else (Explorer). When finished, he can only select 'Rebuild device library' from the context menu and the library is updated (based on the second option it either scans all tracks or only tracks added from the last scan). |
|
Based on IM discussion UI should be changed to: [x] Update device library when Synchronizing On 'Rebuild Device Library': (o) Update it only for newly added tracks ( ) Update it for all tracks (takes longer) Note: the first setting implies a code change so that this setting applies to both Synchronize Selected and Auto-Synchronize). We also agreed that we'll need to enter a new bug to cover the fact that any non-Synchronization operation on the device (namely: copy/move/deletele (by d&d), rename, tag change, does not update the device DB). We're not sure how severe an issue this is. |
|
Fixed in build 806. |
|
Crap: I made a minor mistake: [x] Update device library when Synchronizing the 'S' in synchronizing should be 's' |
|
Fixed in build 807. |
|
Verified in 807. |