Version 2.2.5 of the beta is now available. There are quite a few changes in this release, including:
1) Added the sync to cloud folder option. I will cover this in additional detail further below.
2) Changed all paths in the database to be relative to the storage location when possible with forward slashes. This means if all files are relative to the storage location, you should be able to drop an Android database on Windows (and vice versa) and if the files/folders are all available, it will just work without any additional changes.
3) Differences in song/setlist note settings are now ignored if there are no notes
4) Added fixes to handle songs that use the same file multiple times
5) Added fixes for restoring library backups to preserve subdirectories
6) Added code to properly delete files if a one-way merge requires it
7) Modified behavior when prompt user is selected with a one way merge so that a prompt is now shown with "do nothing" on one of the sides.
8) Fixed merge errors related to chord pro and text files having a different number of pages on each device due to screen size differences.
9) (Windows 10 only) Fixed link point radius sizes to ignore scaling factors
10) (Windows 10 only) Keyboard focus is now assigned to the main library list automatically
11) (Windows 10 only) Added code to correctly handle UTF-16 or UTF-8 with BOM text/chord pro documents in the editor
12) (Windows 10 only) Added fixes for uploading files to Dropbox and Drive to ensure the correct file size is used
13) (Windows 10 only) Fixed issue where audio player would occasionally not play an audio track due to loading the track twice in quick succession
14) (Windows 10 only) Fixed issue on the group editor screen where the entries could not be seen if dark theme or night mode was enabled
A beta version of the companion has also been released at www.zubersoft.com/mobilesheets/downloads/MobileSheetsProCompanion.exe that has the changes for relative paths. It would be great if some testers could test that out as well just make sure I didn't miss anything.
With the new sync to folder option, you have to pick Dropbox or Google Drive, and then select a folder. If you have never synchronized to that folder before, MobileSheets will prompt you to upload your library to that folder. It doesn't matter if you already have files and folders there - you still have to let MobileSheets upload your entire library, as it compiles important information about every file (like hashcodes), sets up the folder structure it needs (it will try to replicate what is on the device if everything is relative to the storage location) and updates the database that is uploaded to reference the paths to the files in the cloud folders. After you've done this initial sync, future syncs will download the database and hashcode file and then quickly look for differences between all of the songs and files in the libraries. Using this precompiled list of hashes prevents MobileSheets from having to recalculate the hash for every file in the cloud folder (meaning the entire file has to be downloaded) to see if any changes have been made to it since the last sync. If the last modified timestamp changes, then the hash has to be recalculated (in case you upload a new version of a file). Handling the sync to folder option this way was the only way I could come up with to handle common usage scenarios while still keeping the sync as fast as possible (without having to download the data for every file every time). For users that want to use this functionality please note: you CANNOT replace the database in the cloud folder with one from a device. That will break the synchronization functionality completely, as all of the file paths in the database would be incorrect. You can drop in updated versions of song files if needed (or new files to be imported), and the next sync will capture these, but the database and hashcode file must not be edited in any way.
Thanks,
Mike
1) Added the sync to cloud folder option. I will cover this in additional detail further below.
2) Changed all paths in the database to be relative to the storage location when possible with forward slashes. This means if all files are relative to the storage location, you should be able to drop an Android database on Windows (and vice versa) and if the files/folders are all available, it will just work without any additional changes.
3) Differences in song/setlist note settings are now ignored if there are no notes
4) Added fixes to handle songs that use the same file multiple times
5) Added fixes for restoring library backups to preserve subdirectories
6) Added code to properly delete files if a one-way merge requires it
7) Modified behavior when prompt user is selected with a one way merge so that a prompt is now shown with "do nothing" on one of the sides.
8) Fixed merge errors related to chord pro and text files having a different number of pages on each device due to screen size differences.
9) (Windows 10 only) Fixed link point radius sizes to ignore scaling factors
10) (Windows 10 only) Keyboard focus is now assigned to the main library list automatically
11) (Windows 10 only) Added code to correctly handle UTF-16 or UTF-8 with BOM text/chord pro documents in the editor
12) (Windows 10 only) Added fixes for uploading files to Dropbox and Drive to ensure the correct file size is used
13) (Windows 10 only) Fixed issue where audio player would occasionally not play an audio track due to loading the track twice in quick succession
14) (Windows 10 only) Fixed issue on the group editor screen where the entries could not be seen if dark theme or night mode was enabled
A beta version of the companion has also been released at www.zubersoft.com/mobilesheets/downloads/MobileSheetsProCompanion.exe that has the changes for relative paths. It would be great if some testers could test that out as well just make sure I didn't miss anything.
With the new sync to folder option, you have to pick Dropbox or Google Drive, and then select a folder. If you have never synchronized to that folder before, MobileSheets will prompt you to upload your library to that folder. It doesn't matter if you already have files and folders there - you still have to let MobileSheets upload your entire library, as it compiles important information about every file (like hashcodes), sets up the folder structure it needs (it will try to replicate what is on the device if everything is relative to the storage location) and updates the database that is uploaded to reference the paths to the files in the cloud folders. After you've done this initial sync, future syncs will download the database and hashcode file and then quickly look for differences between all of the songs and files in the libraries. Using this precompiled list of hashes prevents MobileSheets from having to recalculate the hash for every file in the cloud folder (meaning the entire file has to be downloaded) to see if any changes have been made to it since the last sync. If the last modified timestamp changes, then the hash has to be recalculated (in case you upload a new version of a file). Handling the sync to folder option this way was the only way I could come up with to handle common usage scenarios while still keeping the sync as fast as possible (without having to download the data for every file every time). For users that want to use this functionality please note: you CANNOT replace the database in the cloud folder with one from a device. That will break the synchronization functionality completely, as all of the file paths in the database would be incorrect. You can drop in updated versions of song files if needed (or new files to be imported), and the next sync will capture these, but the database and hashcode file must not be edited in any way.
Thanks,
Mike