Re: [Finale] Fin2005a question
Aaron Sherber wrote: Thanks for checking. Jari seems to have the impression that this is not fixed as well as it might be. With these conflicting reports, it looks like I will be passing on 2005 after all. Do you still have the rest/bracket/triplet problem screenshot available, that illustrated the problem you produced in the initial Fin2005Demo release? Best regards, Jari Williamsson ___ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] Fin2005a question
At 09:58 AM 11/17/2004, Jari Williamsson wrote: Do you still have the rest/bracket/triplet problem screenshot available, that illustrated the problem you produced in the initial Fin2005Demo release? No, it looks like I've cleaned it off my website. But looking at the email I sent, if you create a triplet consisting of eighth rest/eighth note/eighth note and make the two notes an octave apart, the number would be completely outside the bracket (again, in the initial demo). Moving the notes closer together gradually brought the number in line with the bracket. Aaron. ___ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] Fin2005a question
On Wednesday, November 17, 2004, at 10:19 AM, Aaron Sherber wrote: At 09:58 AM 11/17/2004, Jari Williamsson wrote: Do you still have the rest/bracket/triplet problem screenshot available, that illustrated the problem you produced in the initial Fin2005Demo release? No, it looks like I've cleaned it off my website. But looking at the email I sent, if you create a triplet consisting of eighth rest/eighth note/eighth note and make the two notes an octave apart, the number would be completely outside the bracket (again, in the initial demo). Moving the notes closer together gradually brought the number in line with the bracket. Aaron. Ah. When I tried your example (and a few of my own) in FinMac2005a, the number was indeed displaced higher if the first two notes (or rest and note) were high and the third an octave lower, and lower if the first two notes were low. I don't have the original release of 2005 anymore on any of my computers, so I can't compare it with the original, but this is indeed an instance of wacky number movement. Sorry for the bad news. Christopher ___ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] Fin2005a question
On Monday, November 15, 2004, at 06:49 PM, Christopher Smith wrote: On Monday, November 15, 2004, at 06:23 PM, Aaron Sherber wrote: Hi, Can anyone with the 2005a update confirm that Engraver Tuplet bugs are fixed as listed in the Readme -- in particular, that tuplet numbers no longer avoid expressions with undesirable results and that the vertical position of the number no longer varies greatly depending on the context? I don't know when the demo will be updated to 2005a, and I'd like to order Fin2005 if these bugs have actually been quashed. Thanks, Aaron. I'll check it when I get home, but are you on Mac or PC? I'm on mac. Christopher I tried it in Mac, and I can't get the number to behave badly under any circumstances in the way that it did before. If there is a specific test you would like me to try, I will, just explain it to me. This particular bug seems to be squashed, in my tests, anyway. As for avoiding expressions, the tuplet doesn't seem to do that at all, but I don't remember it ever doing that. The number stays where it should in all cases that I tried, and I actually like the default angles of the brackets in most cases. With articulations or slurs, or both, is another story, though, as I need to adjust all of this by hand. The number looks good all the time, though. Christopher ___ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] Fin2005a question
Aaron Sherber wrote: Can anyone with the 2005a update confirm that Engraver Tuplet bugs are fixed as listed in the Readme -- in particular, that tuplet numbers no longer avoid expressions with undesirable results and that the vertical position of the number no longer varies greatly depending on the context? The bugs regarding tuplets being affected by expressions and articulations are fixed. However, I would say that the bracket/number bug is still there, although it's not as huge as in the initial version of Fin2005. (The sequences of the tuplet marketing material on MMs site are still not what you get in Fin2005a.) Best regards, Jari Williamsson ___ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] Fin2005a question
At 06:49 PM 11/15/2004, Christopher Smith wrote: I'll check it when I get home, but are you on Mac or PC? I'm on mac. I'm on PC, but it shouldn't matter. This was not a platform-specific bug, so hopefully the fix isn't, either. Thanks, Aaron. ___ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] Fin2005a question
At 07:34 PM 11/15/2004, Jari Williamsson wrote: The bugs regarding tuplets being affected by expressions and articulations are fixed. However, I would say that the bracket/number bug is still there, although it's not as huge as in the initial version of Fin2005. (The sequences of the tuplet marketing material on MMs site are still not what you get in Fin2005a.) Damn. So I guess the key words in the Readme are no longer varies *greatly* -- now it just varies somewhat? I was hoping for doesn't vary at all. Thanks, Aaron. ___ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale
