New post
Avatar
0

 It seems that for no reason whatsoever, Finale has decided that when I click the expressions option and then click on a measure, it will automatically just place whatever expression it wants (in this case, it's stuck on "p") instead of taking me to the selection box to let me choose/ create my own.  When I try to edit it, it just takes me to the expression designer, which is almost useless, especially when I want to add a rehearsal mark such as a boxed number or letter.  It is as if the Expression Selection box simply does not exist anymore.  I never once asked Finale to make this change and I cannot find a way to change it back.  Anyone have any idea what to do?  This problem is wasting so much time right now. 

I use Finale 2014.5

5 comments

Date Votes
Avatar
0

Update: It now happens with the articulation tool as well.  Once again, I did not tell Finale to do any of this, which is the most irritating part.  If anyone can help, please let me know.  This problem is wasting so much of my time and is keeping me from getting work done.

Comment actions Permalink
Avatar
0
Comment actions Permalink
Avatar
0
Comment actions Permalink
Avatar
0

I just wanted to piggyback on Lawson's comment. This sounds like it could be the result of key on the keyboard being virtually "stuck" in Finale's eyes, which would trigger metatools instead of calling up the dialog boxes you're expecting, giving the appearance that the dialog boxes are gone.

Since the default metatool for the "piano" dynamic expression is 7, try quitting Finale, try rapidly pressing the 7 keys (QWERTY and Numpad) multiple times, make sure nothing's obstructing either key, then try rebooting the computer and test Finale again.

Be sure to test one of your own files AND a default document to compare the results.

Let us know how it goes, and please let us know what OS you're using!

Comment actions Permalink
Avatar
0

Thanks for all the help. It was just a matter of turning off my laptop and then starting it up again later. When I tried it again, it was back to normal. The computer installed some updates while powering back on, so I don't know if that had anything to do with it.

Comment actions Permalink

Please sign in to leave a comment.