[mrchipk]

I am currently using Songbook Pro for our church worship band. They have a subscription feature for groups that automatically syncs setlists and songs to others in the group. Problem is that when it works it is good, but it is bug riddled, frustrating, and unreliable. Was wondering if there is an easy way to automatically sync Mobilesheets setlist and songs to others seamlessly and reliably without the others having to go into settings and do a manual sync up. Many users are not tech savvy and will not be able to remember how to remember to manually sync. I love Mobilesheets and was using it until i needed something that does automatic cloud syncing. The developer of Songbook pro doesn't seem to be able to or doesn't care to fix their unreliable syncing that has been going on for months now even though I am paying a monthly subscription for that feature. Any help would be greatly appreciated!

[Zubersoft]

Adding an automatic synchronization feature is certainly on my list of things to do, but the immediate plan for that is to allow users to keep all of their devices exactly the same. If you only want to sync just songs and setlists and not keep all the devices the same, then this feature will most likely not work well. Perhaps when the feature is rolled out, it can be modified to only synchronize certain things automatically, but the feature is already going to be incredibly complicated to implement. This is because the user needs to be able to continue using the app while the synchronization is occurring, so I have to basically take snapshots of everything that is changing so that only those changes are synchronized. It is much easier if I can basically just replace the database file with a new copy (meaning it just replaces all of the current data), but that won't work if users want to be able to only synchronize a subset of the data. Then I would have to use a much more complicated approach, meaning it is more likely to have bugs and will be much more complicated to maintain (increasing development time for every new feature that impacts the synchronization in some way). 

Mike

[mrchipk]

Adding an automatic synchronization feature is certainly on my list of things to do, but the immediate plan for that is to allow users to keep all of their devices exactly the same. If you only want to sync just songs and setlists and not keep all the devices the same, then this feature will most likely not work well. Perhaps when the feature is rolled out, it can be modified to only synchronize certain things automatically, but the feature is already going to be incredibly complicated to implement. This is because the user needs to be able to continue using the app while the synchronization is occurring, so I have to basically take snapshots of everything that is changing so that only those changes are synchronized. It is much easier if I can basically just replace the database file with a new copy (meaning it just replaces all of the current data), but that won't work if users want to be able to only synchronize a subset of the data. Then I would have to use a much more complicated approach, meaning it is more likely to have bugs and will be much more complicated to maintain (increasing development time for every new feature that impacts the synchronization in some way). 

Mike

My desire is to have all the song and setlist databases to be the same except for individual annotations on songs. But also need to to be easy for the members of my team to synchronize their data.

[BRX]

Mike, a thought you probably had yourself already, but anyway:

Would it be possible to set a requirement for such partial syncs that the devices have to have the same songtitles and all songs have to be in the same (if needed an extra created one) collection? Each user could still have his own annotations for that (or even another file if the songtitle is the same).

[Zubersoft]

My plan is to allow users to pick which groups are synchronized, but this would also handle new songs, not just merging existing songs. 

Mike