I'm at work and only seeing today's messages, so I've missed the beginning of this thread, but if this is the problem I think it is, I remember it quite well. It's not actually an octave problem; it's a clef problem. I forget exactly how it plays out, but at some point in its logic Speedy assumes a treble clef positioning when you're actually in bass clef and somehow that results in the notes appearing way too high. (It's not actually an octave, I think it's a 9th.) Thinking back now, I can't figure what the process would be, but I remember there was a logic to it.
The problem is easily repeatable once you know the details. It has to do with how you enter the frame. Some ways of entering trigger the problem (or more likely, fail to trigger the proper clef recognition); other ways work fine. The problem definitely existed in v2002, which I used regularly for many years. I think it went away when I upgraded to v2004 (the last upgrade I made, which I didn't do until some time around 2006), but to be honest I've done so very little Finale work since then that I'm really not sure. I'm a compulsive note taker, so I've probably got detailed notes on the bug somewhere in the "archives" on my home computer. If anyone is interested in details, bug me about it and I'll see if I can't dig something up. mdl _______________________________________________ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
