Improved notation features

I think it is time the developers turned their attention to the notation features of this programme. I am not talking about all those avante garde things, this is just the basic set of requirements for people producing regular scores and songs. this list includes some kinks in the program but the moderators in this forum tend to be a bit heavy-handed so pick them up in features and make up your own mind. 1. The ability to place system and staff text and objects over/under multibar rests without the rest breaking at the position of the text. 2. The ability to alter the base line and tracking of tuplet figures to accomodate variances in font metrics. 3. The persistance of absolute sizes for system lines and system objects (such as bar numbers) when placed over a small size staff. 4. The ability to lock a score, preventing any changes to system objects when parts are cast off as dynamic parts. i.e.(improve interoperability between dynamic parts and score to the point where we can choose every single item state - whether parts and score are synchronous or asynchronous with one another's setting.) 5. Allow adjustable base line settings for all text items in the font window. 6. Allow document layers in a much more explicit fashion and allow visiblity between layers to be toggled on or off for more complicated scores. 7. Allow group instrument names to co-esxit with individual instrument names and all those instrument characters in those names to be baseline adjustable so that we can truly have Horns I.II. with the roman numerals stacked and horns between them... Without complicated hacks if possible. I am not really bothered about sequencing or audio programming - the latest incarnation of this project had nothing for me - but I do care about notation and if you get that right the audio will be a nice addendum to the main reason for buying this program. To produce beautiful scores. At the moment we achieve this through tedious labour and righteous indignation. Developers, I don't care if it's complicated, because if I have a need I will find a way but you must start to think about meeting us half-way with design depth that allows professionals to reach into the guts of this application and pull out great notation without having to trick the system into doing something it was (and probably never has) been designed to do. So Please. And Thank You. Stop trying to be all things to all men and make at least one of your features Really Good.

Comments (1) Features