• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Synchronize with a backup file
#1
Because some musicians have lot of songs, the backup restore is not usefull and sometime confusing...
This option is risky if the librairy is not dedicated...

It could be really usefull to have an option "Snchronise with a backup file".
In this case, no questions requierd, the synch is unidirectional from Bachup file TO active librairy.
That option is more faster and avoid risk to clic "remove librairy" using the backup restore procedure.

   
Reply
#2
Isn't that exactly how the current option works when synchronizing with a backup file? The wording says synchronize to a backup file (which I know you don't like and is being changed) but it already does exactly what you are describing - it pulls changes out of the backup file to update the current library and effectively make it match what is in the backup file. I don't exactly get how this is any safer than restoring a backup file though - either way, it can overwrite changes in the library depending on the sync settings.

Mike
Reply
#3
(07-29-2025, 06:48 AM)Zubersoft Wrote: Isn't that exactly how the current option works when synchronizing with a backup file? The wording says synchronize to a backup file (which I know you don't like and is being changed) but it already does exactly what you are describing - it pulls changes out of the backup file to update the current library and effectively make it match what is in the backup file. I don't exactly get how this is any safer than restoring a backup file though - either way, it can overwrite changes in the library depending on the sync settings.
Mike

The backup file is always full and compact. At te moment "Backup files" are lot of files in a directory, sometimes subject to errors or external intervention. Furthermore, they do not contain only the active library and are difficult to transfer or move. 

Synchronization FROM the backup file (one-way) allows you to maintain the integrity of a backup file, transfer it, and compare its contents without restoring the entire file. In this case, personal annotations will be preserved. 

It is much easier to transfer a single backup file. It offer a safe solution to dispatch changes in a band.
Reply
#4
A backup file contains only the library that was active when it was generated. I do have the fix coming that you asked for where it won't change the active library in the settings, but that has nothing to do with which library was included in the backup and also you can just uncheck the option to restore settings to get around that issue until the update comes out. The only thing you've said that I agree with is that the synchronize option lets people keep their own annotations if that is required.

Mike
Reply
#5
(07-30-2025, 07:51 AM)Zubersoft Wrote: A backup file contains only the library that was active when it was generated. I do have the fix coming that you asked for where it won't change the active library in the settings, but that has nothing to do with which library was included in the backup and also you can just uncheck the option to restore settings to get around that issue until the update comes out. The only thing you've said that I agree with is that the synchronize option lets people keep their own annotations if that is required.

Mike

Yes, these are two different and complementary options. Normally, restoring a library from a backup.msb file easily risks destroying the library by mistake or carelessness. (forgetting option clic), last option choosed not memorysed... etc.

I think synchronizing the current library "from" an .msb file would be an option intended for the "average" musician who takes fewer risks. Moreover, this option exists in Compagniopn; you can "open" an .msb file. 

Another argument: the "backup directory" (the one you use for the current synchronization) no longer reconstitutes correctly if external intervention occurs. We haven't found a way to reconstitute it after a musician's mistake trying to "clean things up", deleting som double files... 

This directory, with hundreds of files, remains a relatively fragile element, requiring attention and knowledge. 

A "backup.msb" is much easier to handle and publish, and remains more compact and reliable.
Reply




Users browsing this thread:
1 Guest(s)


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