View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0018468 | MMA | General | public | 2021-10-26 05:37 | 2023-07-03 20:02 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Fixed in Version | 2.0.0 | ||||
| Summary | 0018468: Changing metadata always causes certain tracks to resynch | ||||
| Description | Editing the rating of certain tracks on the sync list then syncing causes the track to resync instead of just updating the metadata. e.g. 1 Create Mix3 Playlist. Including several .m4a files > 256 kbps 2 Add Mix3 to the Sync list 3 Initiate autosync --> success --debug log starts here-- 3.1 Initiate autosync --> everything already in sync (MMA Log ID: SSA3YTK3E7) 4 Edit the ratings of 'Familiar' and 'Broken sleep' 5 Resync --> Instead of updating, the tracks resync! (MMA Log ID: 6HZS54BYA8) This doesn't seem to occur with MP3 or FLAC files, and only occurs with _some_ .m4a files. I can't figure out what's unique about them other than that they're high bitrate (but don't trigger any auto-conversion rules). Set as immediate, because we're in the process of releasing MMA 1.4.4 and just want to make sure that it isn't an MMA sync regression (I'll test that shortly). Logs/mmdc file/test files posted to ftp. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1093 | ||||
|
|
Reduced priority to Urgent as it seems that this also occurs when syncing MMW 5.0.2 to MMA 1.4.3. I used a default sync profile except I enabled deletion of library tracks not on the sync list. |
|
|
As it is log from Wi-Fi sync then I can't be sure why MMA re-downloaded this tracks, but my speculation is that the reason is changed file size. If I rate the track "Familiar.m4a" (attached by Rusty on FTP) then any rating lower than '5 stars' results in file size 13279891 bytes while rating '5 stars' results in file size 13279892 bytes. Assigned to Martin to confirm whether the changed file size by 1 byte is the reason for MMA re-downloading of this track + fix it by adding a tolerance (say 1KB ?) |
|
|
Changed ratings and file size really differ about 128 B local: 10997929B, remote:10998057B Added tolerance 1KB. This also solves the issue when uploaded tracks are re-downloaded immediately. Fixed in build 2.0.0.1093 |
|
|
Verified 1093. |
