TGTools menu shortcut for ties

[David Ward]

I think the real cause is the interference with that Finale pre-programmed setting for the 0 which opens and closes a Speedy frame (which is actually quite pointless, what is it for?). But I see no way to de-program that bult-in short cut. Is there?

I use this ‘0’ very frequently in Speedy. It's definitely not pointless for me. Anyone else?

[bopeuph]

I don't believe you can call them. But you can file a support ticket on their website and they will answer one on one, like email.

Hmmm, all I found was a phone number on their support page.

[bopeuph]

I use this ‘0’ very frequently in Speedy. It's definitely not pointless for me. Anyone else?

I used to, but the QWERTY 0 key would still function the same, even when I remapped the NUM pad 0 key. I don't know about 27, but 2014 didn't respace music properly when I would do that, so the workaround was to bump a measure to the next system and back to fix the spacing. It was a ridiculous workaround, but my engraving work was down over the last five years that it was a quick inconvenience.

You just reminded me that there's a number of bugs I can't wait to see if are fixed!

• The respacing bug in speedy entry

• The reversed Y-axis values on articulations when a note is cross-staffed and the notehead flipped

• The stuck MIDI loop when using a MIDI device in speedy and I alt+tab to another program and alt+tab back (the last note[s] entered would be "stuck" until I play the note again on the MIDI device).

These are all bugs I just kind of "accepted." The last two have been bugs in Finale since at least 2005, if not earlier.

[mmike]

I don't believe you can call them. But you can file a support ticket on their website and they will answer one on one, like email.

Hmmm, all I found was a phone number on their support page.

You have to do it from here: https://makemusic.zendesk.com/hc/en-us#finale. Bottom right - Get Help, you have to sign in to your account, and then you can fill in information on the form and ask a question.

[bopeuph]

Oh, funny that I found a completely different page! Thanks!

[michelp]

I suspect a confusion here :
mmike seems to speak about 0 (zero) which enters the first frame (at least on the Mac), not to be confused with letter O, also in Speedy, which hides a note or a rest.

[mmike]

mmike seems to speak about 0 (zero) which enters the first frame (at least on the Mac)

indeed (also in Windows)

[bopeuph]

Yep. QWERTY 0 (not the letter O or NUM pad 0) is what I use to enter/exit Speedy. I really just use it to update spacing if things are getting too illegible to continue, so I hit 0 to exit Speedy and respace notes, then hit 0 again to return to the measure in which I was working (though, I stopped using it in 2014 because the spacing wouldn't update, and the only way to fix it was to use the fit measures tool. Looking forward to seeing if that was fixed). NUM pad 0 is also set to that by default, but I use it for tie/untie note. I don't use the letter O at all, because H is the first key to come to mind in hiding a note.

[bopeuph]

And I hope this gets fixed soon. I noticed I keep entering ties by memory and noticing later that they aren't there for this reason!

[motet]

I stopped using it in 2014 because the spacing wouldn't update, and the only way to fix it was to use the fit measures tool.

Do you have Automatic Music Spacing turned on? You should. Just hitting Esc should cause the measure to be respaced.

[bopeuph]

I do, it just didn't work in 2014. I've yet to really start a score from scratch in 27, so it'll be interesting to see how work goes next week.

[bopeuph]

I actually just checked automatic spacing, and it works exactly how it worked 12 years ago. I'm pretty stoked about that!

I also sent tech support a video of my menu shortcut bug. Hopefully they do fix it.

I'm spending the morning trying to catch Finale in some older bugs that have been with Finale at LEAST from 2000-2014, and I can't trip it up right now. I'm really stoked that they've been caught! There are some bugs I was never mad about, because working with a very postmodern composer, there were some very program-breaking things, but some of the more "standard" things have definitely been fixed!

[bopeuph]

Hi Nick,

Thank you for getting back to me. I wanted to take a moment to discuss your case.

After some testing with the team we were able to replicate the behavior. I then spoke with our development team letting them know about the issue. Unfortunately, they said that while we do ship Finale with these plug-ins, since they are made by a third party we do not and cannot actively maintain them. I know that is disappointing to hear, but I would recommend reaching out to Tobais at TG Tools directly and seeing if he has any suggestions, workarounds, or fixes for this particular issue:

[Tobias's direct email]


I know that you are a Speedy entry user, but do you also use Simple entry? There is a way to modify that shortcut using Simple Entry, but I know that may not fit your workflow. If this particular workflow is essential for your work, I might consider purchasing the full version of TG Tools, but I would still reach out to Tobias to get some additional insight into the issue.

While that is disappointing, I do understand their position. I did email TGTools on a more generic email on their site, but maybe I should try this one for Tobias directly? Edit: I looked in my sent folder and I did send directly to Tobias. He has yet to respond, but I figure this won't be a priority for him.

And I know Simple Entry had a huge overhaul like a decade ago, and it's apparently really efficient now, but I just never wanted to relearn an entry method.

[motet]

What about using one of the other keypad keys instead, like / or *?

[bopeuph]

I should try, but after 15+ years of having the tie on the 0 key, I keep hitting that first, remembering it doesn't work, then using 't'. It's so hard-wired into my brain now, that changing it up, even if it works in the software, won't change my habit!

Also, / is used quite a bit for beam breaks on my end. Maybe if PgUp/PgDn work, that might be slightly more helpful, because I end up disabling those keys because I keep accidentally hitting them when I miss the buttons immediately below them and accidentally hit those keys, and it makes me lose my place.

[motet]

It seems to me you can continue to suffer the loss of 0, or you can break your habit.

[bopeuph]

I'm hoping Tobias fixes everything!

[motet]

I have a feeling it's nothing to do with Tobias. The key mapping is correct.