At 9:29 PM -0700 6/04/04, Eric Dannewitz wrote:


Thats like letting Finale print the parts for you. I can't ever remember doing that and liking the results. It would be great to keep a score and the parts together in ONE file, and have separate layouts for each. Then you can change the music, but you have to go through and redo all the page layouts.


OK, I read your link about relational databases. Thank you for the easy-to-understand link. I think I get it now. For this to work in Finale, we would want to be able to click on Special Part Extraction, and have:

control over system breaks for each staff, OR apply the same ones to another staff, as we wish. Also, (kind of like Mirrors) we should be able to stay linked to another part, or break away, as we wish.

Have the titles in the upper left corner of Page 1 and in a defined text block on successive pages inherit the name of the staff, editable without destroying the name on the score if we don't want it to be changed.

have all staff expressions, articulations, etc., have two states, their score position, and their adjusted position in the part, if needed. Be able to make parts inherit changes made to positioning in the score. I'm a little foggy on this last one, should it be absolute positioning, or relative to the previous position? Maybe selecting an item and hitting Clear (Mac) would make it revert to default positioning, as some items do already.

Likewise for Smart Shapes, Lyrics, Chords, umm, am I missing anything?

Maybe we would like to be able to save the view in an easily retrievable format. Clicking the staff and then going into a menu is one mouse movement too much for me. Perhaps a keyboard shortcut would solve it.

Now comes the hard part: How far away is Finale's structure from a relational database to be able to accomplish this in a reasonable number of programmer hours?

Christopher

_______________________________________________
Finale mailing list
[EMAIL PROTECTED]
http://lists.shsu.edu/mailman/listinfo/finale

Reply via email to