View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011036 | MMW v4 | Synchronization | public | 2013-07-03 22:05 | 2013-07-05 15:36 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 4.1 | ||||
| Target Version | 4.1 | Fixed in Version | 4.1 | ||
| Summary | 0011036: Wi-fi sync: Autoplaylists are always updated even when no changes occur | ||||
| Description | Adding an autoplaylist to the sync list --> the playlist is always updated even when no changes occur. e.g. 1 Create an auto-playlist: 5-star accoustic: rating:5, genre=accoustic (containing ~5 tracks) 2 Add it to the auto-sync list 3 Initiate wifi sync --> tracks and playlist sync successfully 4 Initiate wifi sync --> even though not changes were made, status indicates that the playlist was updated | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1646 | ||||
|
|
This is because MMW always serves timestamp = 'now' = 'current time' for auto-playlists. Because auto-playlist's content is 'live' and can be changed anytime (based on used criteria). The only reasonable solution that I see is for MMA to check whether the playlist is auto-playlist and in that case compare the content before actual update of the playlist, but I am not sure about the performance impact, it would always depend on particular auto-playlist. Therefore I would suggest to defer this issue. |
|
|
Thinking about it further, MMW doesn't need remember the old content for every device, but update the auto-playlist's timestamp before each sync in case the old auto-playlist's hash doesn't match (despite the device being synced). So please change the project from MMA->MMW and I will fix it on the MMW side. |
|
|
Fixed in MMW build 1646 with minimal performance impact. |
|
|
Verified 1646. |
