• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Sync Two Kindles
#1
I have two Kindles - Kindle Fire HD 10 - and I would like to get each to have the same songs and Setlists without doing each one manually.  Is there a way to make the MSP data the same by syncing both Kindles?
Reply
#2
It's fairly easy to synchronize two device libraries. This would be my advice:

1) Back up your Android library first on one of the Kindles by going to Settings->Backup and Restore->Backup Library. This will generate a .msb file containing your entire library.
2) Transfer the .msb file to the other kindle or the cloud, and restore it by going to Settings->Backup and Restore->Restore Library from Backup.
3) For synchronizing future changes, you can transfer changes between the two Kindles by tapping the three dots at the top right of the library screen and clicking "Sync Library->Sync to another device" (you can also sync to a cloud folder but this method is a little faster over WiFi). You can set up the sync either to be two-way (if you've made changes on both sides that need to be sent back and forth) or one-way if you know you only want to send changes from one device to the other. You can change the merge behavior to either use the tablet with the most recent changes (the default) or you can have it prompt you any time a change is detected so you can review every modification that will occur.

Let me know if you have any questions about this. 

Mike
Reply
#3
A belated Thank You!
Reply
#4
This is a repeated request, I know. But is it difficult to make an optional box for excluding the actual sheet files from the backup (not only the audio files)?

It would have helped me with my recent troubles with the database quite a bit.
Reply
#5
It's still not something I really want to support as an option due to past experiences. If you can already expose your database file and copy that, why do you need the backup file without any song files or audio files? That is basically just the database file and the settings files. If you can provide an explanation for why that would be valuable, I can consider adding some way of not including song files, although it would require multiple prompts to ensure the user understood what they were doing.

Mike
Reply
#6
Can you back up a fresh install with setup?
Dell Latitude 13.5" 2-in-1 Win 10, ver 19.--
Samsung Note Pro SM-P900 12.2 Android 5.0.2
Asus TF700T, os = CROMi-kk_R1 KitKat-4.4.4r2-CM11-US DEODEX, Based on Android 4.4.4
Nook HD+ OEM
Reply
#7
(03-08-2019, 04:44 AM)Zuberman Wrote: It's still not something I really want to support as an option due to past experiences. If you can already expose your database file and copy that, why do you need the backup file without any song files or audio files? That is basically just the database file and the settings files. If you can provide an explanation for why that would be valuable, I can consider adding some way of not including song files, although it would require multiple prompts to ensure the user understood what they were doing.

Mike

Just out of curiosity: what is "the settings file"? On Android I can see only mobilesheets.db, user_filters.xml and mobilesheets.db-journal in the MSP folder.
first language: German
Acer A1-830, Android 4.4.2 - HP x2 210 G2 Detachable, Win 10 2004
www.moonlightcrisis.de - www.basdjo.de - www.frankenbaend.de


Reply
#8
Happy to share my point of view with you.

In general I dislike it when companies like Microsoft or worse Apple block or even remove features to "protect the dumb user" and make things difficult for more advanced users to tweak their device like they want.
It's a little bit of that here as well.

But of course I'm not talking about defaults. I was thinking like an advanced options tab or link which only opens if clicked on it and there there are the boxes (already preticked) for including audio files and sheet files.
It may of course always appear "preticked" and also have alway showing a warning about the risks to have those files not included in the backup.

I have a pretty big database and also about 7-8 GB source sheets for MSP alone (and many more in the storage location not included in the MSP database). So If backup that even excluding audio files it always takes
several minutes (about 10 right now I think) and I end up with a msb file that's 8 GB in size.

Actually I don't change much with my source files. It's more about adding to the database with more metadata, new setlists, collections, annotations and so on. Also I backup/sync my storage location over several devices 
independenlty from the backup and syncing with MSP so I don't really need a backup of theses sheets.

It's true that exposing the database and the interchangeability because of the recent relative path upgrade have made it much easier for me. But the settings aren't all in the database as you know (I still don't understand exactly which files do what in Android and W10). For a quick backup of the current database and settings to a msb file the option to exclude the sheets would do wonders for me and I would use the backup feature often which I don't do now. Even a quick reinstall when I (or MSP) messes up my data like the day before without affecting the actual files in the storage location would be possible.

Also a restore of a backup (without files) from W10 to Android (and vice versa) would be possible, am I right?

So all in all, after my latest mess, I would appreciate this "quick backup function", especially after I learned that certain files can corrupt MSP so that it always show the welcome message and you can't access the settings any more. The puzzling thing is, that the same local state directory with exactly the same files content (and of course all the same paths) works fine on the Surface but copied to my W10 desktop doesn't. I'm still investigating this. When I have time I will try file for file to see which one causes the abnormal W10 behaviour.
Reply


Digg   Delicious   Reddit   Facebook   Twitter   StumbleUpon  


Users browsing this thread:
1 Guest(s)


  Theme © 2014 iAndrew  
Powered By MyBB, © 2002-2021 MyBB Group.