I am especially intrigued by part of Mr. Patterson's post of today:
"The only downside I can see is if the file is big enough to be anywhere close the 32767 frame limit. If 20-30 staves becomes 40-50, a dense piece of several hundred measures could potentially hit it. A frame is an internal Finale data structure that holds music for 1 layer in 1 bar in 1 staff. 32767 is the maximum positive value in a signed 16-bit integer. This limit is a holdover from Finale having been developed in the 1980s. "Why haven't they fixed this?" you might well ask. I have no idea, but I would guess it must be a really painful and risky change to the code base." I am still using Finale 2006 for most of the jobs that matter (because of the enduring non-compliance with OpenType), and have been especially frustrated with long scores that eventually have odd problems: they don't optimize correctly; part names and numbers don't appear, etc. Could this problem be due to this frame limit? Christopher Husted _______________________________________________ Finale mailing list [email protected] https://lists.shsu.edu/mailman/listinfo/finale To unsubscribe from finale send a message to: [email protected]
