View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011012 | MMW v4 | Synchronization | public | 2013-06-26 21:10 | 2013-07-20 01:40 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 4.1 | ||||
| Target Version | 4.1 | Fixed in Version | 4.1 | ||
| Summary | 0011012: MMW prompts to reverse sync unchanged tracks and playlists over USB | ||||
| Description | 1 Sync tracks and playlists over Wi-Fi Sync --> no tracks are reverse synced 2 Sync tracks over USB --> MMW prompts the user to Update 300 (out of 600) tracks, and a playlist I can't figure out why those tracks specifically are being reverse synced, but no changes were made on MMA that should have triggered a reverse sync operation. | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Fixed in build | 1648 | ||||
|
|
I cannot replicate, this is how I tested: - deleted all tracks in MMA - synced 1 playlist containing 10 tracks over WiFi - synced the same over USB => no confirmation In your case, were the files marked as 'New' or 'Existing' to copy to PC? Were the checkboxes auto-selected? Could you attach debug log? I was only able to replicate it in scenario like this: - sync some tracks/playlists over WiFi - delete the device profile in MMW (this step makes MMW think that all tracks are new) - sync over USB => tracks are marked as 'New to copy', but all are unchecked because they already exist in MMW library (per 0010948:0036291). Maybe it was your case? I was thinking that we could change it a bit and skip such a tracks complettely. i.e. if user copy a new track to device using another app and the track with same metadata already exists in MMW library, then such a track shouldn't be shown at all in the confirmation? |
|
|
Here's how I can replicate the bug: 1 Delete all tracks/playlists from MMA 2 Enable (in MMW) delete unselected and auto-sync files/metadata from the device to the PC 3 In MMW add to the sync list: 1 auto playlist, 1 artist, 1 album 4 Run MMA and click Sync -->Tracks and playlists sync successfully 5 Close MMA 6 Connect the device to the PC 7 In MMW (line 1956 of the debug log) press wired sync button next to device in tree --> MMW prompts to update 24 files from the device to the PC (line 3024 of the debug log) even though no changes were made in MMA that would warrant these updates!! Tested with MMA 148 / MMW 1646. Debug log attached. |
|
|
Although I haven't been able to replicate the issue, I think that I found the reason and fix it (based on the log). To be verified by Rusty in build 1647. |
|
|
No regressions in 1647 Left for Rusty to Confirm and Close |
|
|
Tested in 1647 and the bug is still occurring. Further testing shows the root of the problem. Auto-conversion is configured to convert files to custom VBR settings. However, it seems that MMW is ignoring the auto-conversion settings, and just converting files matching the filter to 128 CBR. I expect that when MMW syncs, it notices that the files on the device don't match the expect VBR bandwiths. Attached is a screengrab of the config settings. |
|
|
Rusty, I still haven't been able to replicate. Please, generate two more logs using build 1647: - one log of the WiFi sync - the second log of the USB sync (until the confirmation dialog appears) + attach screenshot of the confirmation dialog Also please test with the lowest possible amount of files. Re: the auto-conversion settings, you are true that there is a bug that MMW presents them as 128/CBR in MMW interface while they have been correctly converted to VBR/175 (I will fix it as 0008542 that I've re-opened). Nevertheless this shouldn't have an impact on the original issue. |
|
|
Attached is a log file syncing an autoplaylist consisting of 23 files: 0-7700: Initial wifi sync 8350: initiate wired sync 9030: confirmation dialog 10108: sync completion Also attached are images of the sync confirmation dialog, and of the tracks that are on the sync list. I can't see a pattern re. the files that were synced back--hopefully the log tells you something... |
|
|
Thank you, I analyzed the log and the reason is obvious now from this debug line: File for BiDi sync: File was changed physically in the device, Uploadtime: 2013-07-12 15:04:46, Device change: 2013-07-12 15:07:49 Because I take the device change timestamp from MMA's DB (the time when MMA synced the file with media store), but obviously in your case it is 3 minutes later than it was actually synced. I will ask Marek to add truly media.file_modified timestamp to MMA's DB for MMW to use it. For android devices without MMA installed I get the info over MTP protocol, but this would be too slow. |
|
|
Finally resolved another way for now (in build 1648) Because it would be problematic for MMA to keep media.file_modified in DB up-to-date for each file, and because we sync file metadata back from MMA, it doesn't make much sense to copy the synced files back physically. Thus if MMA is installed, then metadata are auto-synced, but not the files physically. New files (not MMW->MMA synced) are copied to MMW as expected, only the existing are not copied back for the reasons explained above. |
|
|
Verified 150 MMA-> MMW Seams to be faster now as files are not copied but only metadata is updated. |
