And if it's a matter of file format and backwards compatibility, I would think that at some point that has to be addressed.

When I use Noteworthy Composer and load an old file, it converts it to the new file internally. Then when I go to save it, it warns me that I had opened an old format file that will now be overwritten by the new format, which preclude the previous versions of the program from opening it. I also know there are other apps that allow you to save as the previous version (I believe Finale does this as well); however, when you do, you lose the new features you wanted in that saved file.

I think file format will ultimately have to be addressed if many of the things being suggested are implemented, especially those things that are song specific (sing that information needs to stored in the file) and we'll have to reckon with the fact that older versions won't be able to open newly created content.

Old content should be able to be open, because you would still have global defaults set, so those new fields can be filled in with those defaults when you open the file, and saved with the file when you save (but you won't be able to test the file in the older version).

I could be wrong, but I suspect some of this is the reason for perceived hesitancy to implement some of these ideas.

Or maybe the file format is extensible enough that it's not a problem, but I just had that thought.

John

Laptop-HP Omen I7 Win11Pro 32GB 2x2TB, 1x4TB SSD
Desktop-ASUS-I7 Win10Pro 32GB 2x1.5TB, 2x2TB, 1x4TB SATA

BB2025/UMC404HD/Casios/Cakewalk/Reaper/Studio One/MixBus/Notion/Finale/Dorico/Noteworthy/NI/Halion/IK

http://www.sus4chord.com