View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0009941||MediaMonkey for Android||Synchronization||public||2012-11-06 11:51||2019-11-07 10:30|
|Target Version||2.1.0||Fixed in Version|
|Summary||0009941: Sync with multiple MediaMonkey libraries (databases)|
|Description||Currently there is a problem that MMW <-> MMA sync is designed in a way that |
1. MMW can sync with multiple MMA libraries
2. MMA cannot sync with multiple MMW libraries
The reason is that we uses unique id for each track that is based on track id from MMW database.
Because MMW can start multiple sync servers then we cannot distinguish MMW Library based on server ID, therefore I added (in 126.96.36.1994) another element to the DeviceConfig.xml
Where 885639355 is unique ID of MMW database.
i.e. Based on this ID MMA can distinguish between multiple MMW libraries/databases.
|Tags||No tags attached.|
|Fixed in build|
|related to||0011016||closed||Ludek||MediaMonkey (current)||USB Sync: Renaming playlist yields strange confirmations|
|related to||0011780||assigned||martin||MediaMonkey for Android||WiFi Sync Settings: Each SSID should have own settings|
|related to||0012190||new||MediaMonkey (current)||Authentication: Add some sort of User/Password authenticaton for accessing MMW from External IPs|
|related to||0011982||feedback||rusty||MediaMonkey for Android||Simplify and improve wifi sync wizard|
wifi_item_id will not be stored within table media (as currently), but within another table as triplets
<media.id, wifi_item_id, database_id>
MMA gets DatabaseID on sync start and gets particular wifi_item_id from that table for each song.
||Assigning to Marek to implement as suggested. As for timeframe, in case it's a reasonably easy fix, we should implement asap, otherwise it could probably wait for MMA 1.1.|
||Implemented just quick test of changed DB to be present in build 67|
||Decreasing priority. It will particularly be needed in the future, e.g. when we include some kind of a cloud sync, etc. That said, should be implemented reasonably soon, to be ready for this scenario.|
Note that instead of pairing based on MMA.media.wifi_item_id = MMW.Songs.ID and adding another MMA relation table, there would be better to pair based on GUID
MMA.media.GUID = MMW.Songs.GUID
The same we implemented for playlists, details here: ~37173
||Note: current behavior is that upon attempting to sync with another instance of MMW, all pairing data from DB is removed, and all tracks are paired again with new MMW instance.|
||I think that this can be implemented with 0011982 in 1.1.1|