on 02.7.10 3:05 PM, Philip Aker at [EMAIL PROTECTED] wrote: >>> So how's about >>> you come up with a description of a Sib >>> articulation/expression/playback effect that I can't reproduce >>> in Finale? > >> A crescendo in less than 5 minutes and 3 swear words? <g> > > > Richard, > > I appreciate a quick wit however--
<technique snipped> > In all seriousness, let's see that Sib > articulation/expression/playback effect that's not possible to > do in Finale. In all seriousness, I think the proper question is how hard you want to work to achieve a desired effect, and for Finale users the question ought to be, "Why do I have to work so hard to get things done?" Why shouldn't a crescendo be reasonably good (maybe not perfect, but better than nothing) with one keystroke instead of ten? Why shouldn't expressions understand what is wanted without me having to intervene all the time? Why is so much of what I want to achieve such a pain in the ass to get done? Contrary to appearances, I'm not trashing Finale. Really. There's an awful lot about it that I like, but having tasted the other side, I think there's an awful lot of mediocrity, and downright perversity, in the user interface too, and there's really no reason to accept it. Power users may have discovered workarounds and cludges, or cracked the code, or made their peace with the status quo, and from those lofty heights this may all appear petty and childish, but damnit, a program shouldn't take ages to master and it shouldn't be so cantankerous that only a chosen few can get much good out of it. I submit to you that "steep learning curve" really just means "programmers who haven't thought hard enough about the interface." Why put up with that? >From the soapbox of: Richard Walker Rousing the rabble in Yokohama _______________________________________________ Finale mailing list [EMAIL PROTECTED] http://mail.shsu.edu/mailman/listinfo/finale
