[Zubersoft]

Version 3.9.19 is now available (although it's waiting for approval on the Apple App Store). This update addresses some issues users faced after updating to version 3.9.18. For users that encountered an error with the incorrect transpose key being used for their text or ChordPro files, the only fix is to restore a library backup file from version 3.9.17, or go to Settings->Backup and Restore->Restore Automatic Database Backup and revert the database back to a version from before the 3.9.18 update. Please be aware that you will lose any changes made to the library since that backup. The full list of changes can be seen below:

Changes affecting all platforms v3.9.19

• Fixed incorrect conversion of transposed key with text and ChordPro files.
  
• Fixed errors that could occur when importing a .msf file and selecting the new option to keep the existing songs
  
• Fixed error with viewing the advanced settings through the default text display settings dialog
  
• Adjusted the default subtitle size to match the older meta size. This change only affects users updating from 3.9.17
  

Android v3.9.19

• Fixed bug that could occur if trying to synchronize to a Dropbox folder immediately after accessing the synchronization screen
  

Windows v3.9.19

• Added code to forcefully fix the database for users that encountered errors with text and ChordPro files after updating
  
• Fixed error with renaming a library with isolated storage that could cause some files not to be moved correctly
  
• Fixed error with modifying an existing library to use isolated storage that could cause some files not to be correctly moved
  
• Fixed bug when creating a backup file using a cloud service where the default name didn't correctly use the current library name
  
• Fixed bug with annotation favorites not correctly loading the file in the application folder
  
• Fixed error that could occur when loading an ABC file with a filename containing umlauts or other special characters
  
• Fixed bug with the metronome sound effects dropdown being cut off if the metronome window was displayed using the quick action box without the overlay visible
  
• Fixed issue with the sharing options for Setlists not working correctly.
  

iOS/iPadOS/MacOS v3.9.19

• Fixed bug that could occur if trying to synchronize to a Dropbox folder immediately after accessing the synchronization screen
  

I will be working on other reported issues, so I appreciate everyone's patience while I try to investigate and reproduce those issues.

Mike

[pau.cordoba]

Thanks Mike! Great App. 

At MicrosoftStore only display 3.9.18. Not update options.

[Zubersoft]

The update should be available soon, however, version 3.9.20 will be released for users that are encountering problems with text or ChordPro files. I finally found the source of the problem (it's a localization issue that only impacts users whose language uses commas instead of periods for numbers with decimal parts (i.e. 1.2 is 1,2) ).

Mike

[Doumepib]

Thank you Mike for this update, that is functional for me now. But I lost the modifications I had made since the last backup, and I lived some stress without direct access to my chordpro files... I understand it is difficult to test exhaustively all the possible configurations under Windows, due to regionalization of some parameters, so as we cannot decide the moments when updates come, could we envisage to get the possibility to revert to the previous version in case this situation occurs ? A bug is always possible, loosing access to the scores may be very hard in many musical situations...

Now I will have a more serene look to the new functionalities !
Regards,

Domi

[Zubersoft]

None of the app stores support reverting to an earlier version, and if the database is changed during the update, it cannot be reverted by downgrading. You can disable automatic updates through the Microsoft Store, or users of the FastSpring version (https://zubersoft.onfastspring.com/) get to control when updates are installed so that there are never surprises before a performance. I do the best I can to prevent issues, and I fix them as quickly as possible after they do occur, but users should never update the app right before a performance, especially with a large update.

Mike