View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0008342||MMW v4||Synchronization||public||2011-09-06 21:30||2013-12-11 09:41|
|Target Version||4.1||Fixed in Version||4.1|
|Summary||0008342: Autosync fails to initiate if no changes occur within MediaMonkey during a session|
|Description||1 Configure auto-sync e.g. Artist A|
3 Open Explorer and delete one track
4 Click Autosync
--> Nothing happens
5 Disconnect/Reconnect device OR Restart MediaMonkey
6 Click Autosync
--> Track syncs
At step 4, MM should sync.
Note: Tested with USB MS device using wmdm plugin. This bug is new to MM4 (MM3 works correctly).
|Fixed in build||1677|
|parent of||0008374||closed||Ludek||MediaMonkey hangs for 30s on connection of some iPod devices (regression)|
|parent of||0008495||closed||Ludek||AV when browsing device and hitting F5 while synchronization begins (regression)|
|parent of||0011360||closed||Ludek||When device is connected via USB, content is not refreshed after WiFi sync|
|related to||0011560||resolved||Ludek||Usb sync with MMA fails sometimes|
|related to||0011766||closed||Ludek||Sync MMW->MMA USB sync can fail to transfer advanced metadata on occassion|
|related to||0012756||closed||Ludek||Sync: device content is not refreshed after sync|
Yes, this is designed this way for MM 4.0, the device is first scanned, then it can't automatically monitor changes on the device. It isn't automatically re-scanned on synchronization (to make it faster).
I think that it makes sense this way and can only be documented. That said, I understand that it might be hard to explain to users that they have to either restart MM or reconnect the device in case they need it. So we could either:
1. Add a button to Device config that would refresh device content.
2. Add a checkbox that would turn automatic rescan of device before auto-sync on.
3. Do the same as 2., but don't use a new checkbox and rescan the device before auto-sync in case '[ ] Scan as soon as the device is connected' checkbox is unchecked.
I'd prefer to not do anything for MM 4.0, but in case you think it's _really_ necessary, option 3. makes sense to me. Then option 1. could be added for MM 4.1.
Does option 3 really solve the problem? i.e. if the user makes tag changes from within another app while MM is running, this bug will still occur even if '[ ] Scan as soon as the device is connected' is enabled ?!
What about option 4: add context menu option 'Refresh' and/or if F5 is pressed with the device in focus, then trigger a rescan.
||Ok, so let's try to implement refresh on F5 pressed on the device node (and preferably also any subnode) for MM 4.0.|
||Fixed in build 1430.|
4. Verified in 1433
Can you please triage other Jiri proposals and add new bugs if needed.
||I'm not sure whether other changes are needed, but leaving to Rusty to review.|
||Closing and leavin Todoc flag|
Re-opened, it seems to have some others side effects that I believe should be fixed.
1. Connect Android device with MMA installed (content is scanned on connect)
2. Keep the device connected via USB and initiate WiFi sync in MMA that will copy 5 new tracks to the device
3. Keep the device still contected and perform USB sync
=> the 5 tracks are recopied
I think that for devices with database presented, where the scan is mostly fast (iPods, Android devices with MMA installed), MMW could re-scan the content before each auto-sync.
Or probably at least for the Android devices with MMA installed the content should be refreshed before USB auto-sync, because MMA's DB is downloaded anyway during each auto-sync.
Or even better the content should be refreshed immediatelly after WiFi sync when the device is connected also over USB, tracked as 0011360
Fixed in build 1677.
i.e. The contents are automatically re-scanned before each auto-sync for android devices with MMA database presented (this covers the situation when tracks are deleted in MMA between scan and next auto-sync).