View Issue Details

IDProjectCategoryView StatusLast Update
0009941MediaMonkey for AndroidSynchronizationpublic2019-11-07 10:30
Status assignedResolutionopen 
Product Version1.0.4 
Target Version2.1.0Fixed in Version 
Summary0009941: Sync with multiple MediaMonkey libraries (databases)
DescriptionCurrently 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 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.
TagsNo tags attached.
Fixed in build


related to 0011016 closedLudek MediaMonkey (current) USB Sync: Renaming playlist yields strange confirmations 
related to 0011780 assignedmartin 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 feedbackrusty MediaMonkey for Android Simplify and improve wifi sync wizard 



2012-11-06 12:07

developer   ~0032958

Last edited: 2012-11-06 12:11

View 4 revisions

Technical details:

wifi_item_id will not be stored within table media (as currently), but within another table as triplets
<, wifi_item_id, database_id>

MMA gets DatabaseID on sync start and gets particular wifi_item_id from that table for each song.


2012-11-06 12:42

administrator   ~0032960

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.


2012-11-29 00:42

developer   ~0033477

Implemented just quick test of changed DB to be present in build 67


2013-01-24 13:44

administrator   ~0034656

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.


2013-08-16 10:13

developer   ~0037174

Last edited: 2013-08-16 10:14

View 4 revisions

Note that instead of pairing based on = MMW.Songs.ID and adding another MMA relation table, there would be better to pair based on GUID = MMW.Songs.GUID

The same we implemented for playlists, details here: ~37173


2014-01-21 22:07

administrator   ~0039321

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.


2014-09-25 12:27

developer   ~0040586

I think that this can be implemented with 0011982 in 1.1.1