by Ludek » Wed Jul 28, 2021 12:24 pm
Actually there is the metadata dabase shared in the cloud (just not MM.DB, but in /MediaMonkey/meta_files/v3/ mix of zipped JSON and SQLite DB, i.e. more "lite" format including (auto-)playlist criteria and tracks metadata). So syncing (auto-)playlists and track metadata with one DropBox location and more MM5 instances should work (at least it worked when I tested it lastly), but it probably hasn't been widely tested yet, so backup your media files and databases at first (for sure).
e.g. try to sync just single (auto-)playlist from one MM5 instance to DropBox and scan this DropBox location using another MM5 instance: auto-playlists and track (including medatada) should be imported fine.
[quote=Lowlander post_id=484880 time=1627469637 user_id=262]
There is no support added to store the database file itself in the cloud, but you can Sync media files to cloud services including Dropbox: https://www.mediamonkey.com/wiki/WebHelp:Cloud_Services/5.0#Sync_from_MediaMonkey_to_Cloud_Service
[/quote]
Actually there is the metadata dabase shared in the cloud (just not MM.DB, but in /MediaMonkey/meta_files/v3/ mix of zipped JSON and SQLite DB, i.e. more "lite" format including (auto-)playlist criteria and tracks metadata). So syncing (auto-)playlists and track metadata with one DropBox location and more MM5 instances should work (at least it worked when I tested it lastly), but it probably hasn't been widely tested yet, so backup your media files and databases at first (for sure).
e.g. try to sync just single (auto-)playlist from one MM5 instance to DropBox and scan this DropBox location using another MM5 instance: auto-playlists and track (including medatada) should be imported fine.