...i recently worked on a orchestral score (63 parts) in which the composer had created 8 shape expressions with arrows indicating varying degrees of pitch inflection, and assigned them throughout the score using metatools (articulations). 59 pages A2 format, 5000+ shape expressions (in the shape selection dialogue box), 2.5M (subsequently reduced to 1.4 by using mirrors). since part extraction does not filter unused shapes, each part was massive as well, which then also slowed down saving: i could no longer effectively make use of auto-save, since i always had several files open (eg. 12 winds + score) at once for back and forth corrections, and because of the time involved in saving the files, i tried to space out my saves, both of which increase the risk (likelihood!) of lost data in the event of a crash... which happens from time to time with numbers of these mega files open without saving regularily. i know, i've heard it all before: buy a new machine ($$$), get more RAM (lack of RAM isn't a problem for me except for such finale quirks), but this wouldn't have been an issue in the first place, if the documents didn't bloat like this!
Ugh! Well hindsight is 20/20 but I suggest you turn on your composer/client to font technologies as a viable means of expression. Considering the amount of inconvenience endured, the cost of a custom designed font would seem well worth it in this case. Or even the purchase of a font creation application.
Philip Aker http://www.aker.ca
_______________________________________________ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale
