Title: RE: [Finale] More Quickeys problems

    From:   [EMAIL PROTECTED] on behalf of Johannes Gebauer
    Sent:   Tuesday, March 8, 2005 7:25 AM

    I think I am going to give up on Quickeys. There are so many problems...

Sorry to hear your having problems. FWIW I have had very little issues with QK3

    1) When I try to record a complex macro in Finale, Quickeys regularly
    crashes.

I have never had this happen and I create some macros that contain 120 steps.

    2) I am trying to get a Macro to select a popup menu item in the Frame
    Attributes Dialog. I am trying to change a textblock from Single Page to
    Page Range. Either this doesn't work at all, or, if it does work, for
    some reason the second page range text field doesn't become active. I am
    sure this is partly Finale's fault, but it has already taken me almost a
    day now, without success.

I have had this issue also and seems to be a Finale problem. There are really no good work arounds but depending on what you are trying to do you should be able to get this to work.

    3) Although not as bad as iKey2, the user interface isn't exactly
    wonderful either.

It is a lot better than the past OSX versions.

    4) The editor is so slow.

It can be especially slow with large shortcuts. The great thing is that the shortcuts run very fast and are solid unlike the OS 9 version. I talked with a QK rep. and he said that speed issues were going to be addressed in the future.

    5) Programming complex macros is actually more fiddle than with iKey 2.

But the payoff is that I have a lot of control.

    Nothing I have seen on OS X even comes close to what OneClick could do
    in OS 9.

I don't know OneClick very well but I don't think it had logic and variables. QK3 is very powerful and so there is a bit of a learning curve (just like Finale). As in Finale, QK3 allows you to do the same thing in many different ways. Sometimes it is frustrating learning the best approach but over time you will be as comfortable with QK as you are with Finale.

Let me give you an example of what QK3 has done for me:

When I  finish a large orchestral score I have QK3 setup the file for part extraction. I hit a few buttons and the file is ready for extracting parts. One of the best features in the new QK3 is using the variables and logic functions to change the instrument names in the full score for part extraction. Basically QK looks through the staff attributes dialog boxes and changes the instrument names from what they should look like in the score to what they should look like in the extracted parts. So it changes "Flute" to "FLUTE" etc... but it does all of this in under a minute. Huge time saver. I setup the names as variables (which by the way was a big PINA and hope they figure out a better way to do this) and had the logic functions take care of the looped shortcut. Even though it took a lot of time to set this shortcut up it has shaved about 50 minutes (if I were to do it manually) off of my preparation for creating parts not to mention eliminated all errors in my work.

Similar to what I tell people about Finale...QuicKeys is worth the time invested in learning.

Don't give up on it yet.

Steve Fiskum

_______________________________________________
Finale mailing list
[email protected]
http://lists.shsu.edu/mailman/listinfo/finale

Reply via email to