View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011593 | MMW v4 | Synchronization | public | 2013-12-11 23:46 | 2014-11-28 00:30 |
| Reporter | peke | Assigned To | |||
| Priority | urgent | Severity | feature | Reproducibility | N/A |
| Status | resolved | Resolution | no change required | ||
| Product Version | 4.1 | ||||
| Target Version | 5.0.0 | ||||
| Summary | 0011593: Sync process: Profile Creation, Initial sync can be better automated | ||||
| Description | During last few changes to sync process it looks that we made things more complicated that they are which now require more user interaction/knowledge for setting sync than it should be normally. Here is how things should be done more simpler. I'll assume that user uses device without MMA installed prior to connecting to MMW and that MMW do not have created profile for that device. I'll present cases with MMA installed. 1. Install MMA and wait till scan completes 2. Start MMW 3. Connect Device 4. Wait till Scanning is done, if MMA is installed create \MediaMonkey\files\USB_Connected so that MMA can watch for USB disconnection and/or "sync_finished" (Handled in MMA) 5. Set MMW Sync profile (enable Scan on connect and grant remote) to sync number of playlists and tracks 6. press OK 7. Press AutoSync in MMW 8. Check for \MediaMonkey\files\SyncProfile.xml and if not existing create SyncProfile.xml.init containing settings for Wi-Fi Sync 8. MMA detects SyncProfile.xml.init and rename it to SyncProfile.xml if Wi-Fi is enabled and connected and Created SyncProfile.xml.loaded that is copy of SyncProfile.xml but with filled MAC Address and phone IP 9. MMA tries to connect to MMW over Wi-Fi where MMW Automatically so that MMW add device to allow list and pair profiles (Message in MMA showing "Initializing") and closes automatically 10. MMW creates \MediaMonkey\files\Sync_started.USB 11. Sync finishes normally After USB Sync is finished: 12. Press Sync Now in MMW to Sync over Wi-Fi and it should be done within seconds as there is no new tracks to sync. (Currently Sync Wizard shows to recreate new sync profile and track pairing which is time consuming and unnecessary) | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
Assigned to Rusty as talked over IM. Main reason for this approach is to eliminate different Sync profiles and cut sync profiles pairing and track Pairing a lot as currently even Initial USB Sync was done and MMW paired tracks initiating Wi-Fi Sync For first time triggers Wi-Fi Sync setup wizard along with not needed Track pairing. Instead of just simple Initiating Sync. Result would be that Wi-Fi sync Can't be initiated During USB Sync due the Step 10. and afterwards they would be paired and in Sync. NOTE for testing: Use same steps as described while ignoring those that are missing/new feature. |
|
|
Further optimization can be made that in Case Wi-Fi sync is started MMW checks if Device is Connected over USB and do sync over USB which should be faster than using Wi-Fi. |
|
|
Peke, it currently works similar way (but slightly better). Once device is connected to PC: MMW tries to find /MediaMonkey/files/StorageInfo.xml created by MMA - if the XML is there, it means that MMA was installed and it gets the pairing key from there and stores it to corresponding device profile - if the XML is not there then it means that MMA was not installed and it MMW creates new key and stores it to /MediaMonkey/files/StorageInfo.xml.mmw for MMA, once MMA is installed, it is taking the pairing key from the XML stored there by MMW and creates /MediaMonkey/files/StorageInfo.xml where the key is stored permanently. That is also reason why /MediaMonkey/files/StorageInfo.xml shoudln't be never deleted. So resolving as "no change required" (until there is a bug) |
|
|
You are right that was I thought from changes we made in sync process recently, I only wondered: a) why Connect wizard was started in MMA in step 12 if MMA imported settings? b) why MMW asked for confirmation when MMA tried to access MMW for Wi-Fi Sync? c) why MMW do not read StorageInfo.xml and check if it is empty and if empty/not set create StorageInfo.xml.mmw so that MMA can import pairing and make MMW/MMA Synched especially as Grant sync is enabled? d) why StorageInfo.xml do not contain device MAC so that MMW automatically allow device sync without confirmation? |
|
|
MMW does read StorageInfo.xml and uses the key from there for pairing. It is creating StorageInfo.xml.mmw for MMA only if StorageInfo.xml doesn't exists. i.e. if MMA was not installed. Yes, MMA was asking for confirmation, because access has not been granted by the user. User always needs to grant the access manually. The reasons are explained here: 0009013:0032873 |
|
|
It is not an issue anymore |
