Backup and restore tag feature is working great so far, but one aspect is different from what I expected.
I thought when it runs backup first time it would create a master db file with all tag values and then create each backup file only with changed tag values.
But currently it creates a complete tag db every time. For my test I used only 400 tracks, but each backup file amounts to 1.2 MB. This would make people with a huge library hesitate to use this feature frequently, not to mention auto-backup feature.
If it worked as I suggested the only downside would be a restore needs a backup file plus the master db file, but the advantages in sizes could be much greater. What do you think?