View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005214 | MMW v4 | Properties/Auto-Tools | public | 2009-01-16 21:24 | 2009-01-23 18:23 |
| Reporter | Assigned To | ||||
| Priority | high | Severity | minor | Reproducibility | always |
| Status | feedback | Resolution | open | ||
| Product Version | 3.1 | ||||
| Summary | 0005214: Unsyncronized Tags node may provide false results | ||||
| Description | User reports recent edits may not be correctly reflected in the unsyncronized nodes track list. reproduction steps: With [X] Update tags when editing properties 1 In a tracklist track tag, press F2 and type some characters. Do not press ENTER. 2 Click on Unsynchronized Tags Expected: list does not include the edited track Observed: list does include the edited track The same happens if after 1, ENTER is pressed and with little delay, 2 performed. It appears Unsynchronized Tags is failing to wait for the tagging queue to empty. | ||||
| Additional Information | http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=36068&st=0&sk=t&sd=a | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
I'm not sure how much can this be considered a bug. The truth is that while MM is tagging on background, this operation is clearly visible to user on status bar and tracks are properly shown in Unsyncronized Tags node, since their tags really are unsychronized at that moment. Sure, we could take our internall tagging queue in account and compare its content instead of the real content of these tracks. However, in case of some problem with tag updating (inaccessible drive, corrupted tag, ...), it would result in false negative. So, although I see that it can be problem for some users, I'm not sure whether we really should do anything about it. |
|
|
The ideal scenario might be that MM always shows data based on the current status i.e. just as a track will be removed from the Library if the File monitor detects that it has been deleted (assuming MM is configured appropriately), other nodes should update dynamically in response to changes in Track characteristics. Assuming that's not a good option in the short term (if we want to release 3.1 any time soon), then there will be instances in which the node/tracklist are out of sync with the actual tag status. Possible approaches are to either: a) display nodes based on what is expected to happen to the tags at the moment that the node is selected b) display nodes based on what is actually in the tags at the moment that the node is selected Given that we're not fixing the underlying cause right now, I think that b) makes more sense (and even if not, the investment in implementing a) isn't worthwhile), but that in the long term, MM should display content in a more dynamic manner. |
