Finale Forum

TG Tools Pro works for me in Finale 26, as do the other third party plugins by Jari and Robert Patterson. What do you mean 'does not accept'? Have you installed it in the right spot?

I found an address here in Holland where I can buy it. The price in euros is the same as the US price + US sales tax, but the difference is that if I buy it here, I can deduct the Dutch tax. I still think it's strange that they charge US sales tax for an item which is being sold to a foreign country.

I just went through the MM website to download the upgrade to Finale 26 and, while I'm willing to pay the euro equivalent of $149, why should I have to pay more than $31 sales tax to the US government?

Sorry to bump this thread but I'd really like to know how well the third-party plugins work with Mojave. Not only TG Tools Pro but also all of Jari's plugins as well as those of Robert Patterson are essential for me.

Could someone test TG Tools Pro with Mojave? That could be a [partial] show-stopper for me if I can’t use them properly, as I rely heavily on some of them. That’s something that won’t be helped at all with v.26 either. I’m afraid Motet’s right: I haven’t heard anything from Tobias for a long time.

Both problems have been reported long before the advent of Mojave. I wonder if it’s been fixed in v26.

Congratulations, Mike! You deserve it!!
Perhaps the issue with 2014.5 is that you have to have had it already installed. But do you really need it?

Don’t worry, those little magnifying glasses have only been available since MM updated the expressions tool; they certainly weren’t there at the end of the last century!

So we have to wait three months before installing the new OS (assuming F26 is released in December) and even longer if we need to keep using F25. The beta versions of Mojave have been available for a long time; what has MM been doing?

I have the same comment as with the last announcement about the improved expressions library: these are things that should have been done properly from the beginning and which experienced users will have already done for themselves painstakingly. And I agree with Anders: these last two announced imp...

1. If you’re going to hide the rest, there’s no need for it to have any particular note value, especially a whole note which would overfill the measure. In this case I’d just enter a quarter and hide it. 2. If you’re entering cross-staff notes, you should use the TG Tools plugin for it which is not ...

John Ruggero wrote:...Turning off articulation collision avoidance improved the spacing in measures in which the accented note was followed by a leap . There was no problem and therefore no change when the notes move stepwise. This I also find curious.

Indeed! Finale moves in mysterious ways...

Isn't this the problem we've been having for years? In measures with more than one layer, flipped articulations sometimes have a mind of their own and even move contrarily to the arrow direction, forcing one to place the articulation by trial-and-error. There's a good chance that MM has solved this ...

I throw myself on the mercy of the court. Sarcasm is actually a low form of wit and I must admit to making myself guilty of it. It's just really hard sometimes when you see a more-or-less legacy program like Sibelius long since having dealt with the above-mentioned problems which are being touted as...

... not to mention the big improvements to lyric placement, cross-staff accidentals and linked parts.

Well said!

Oh dear. A couple of additions to the expressions and articulations libraries plus improvements to their placement which should have been right from the start? These are things we’ve generally had to take care of ourselves anyway. If they’re touting them as ‘new features’, then I’m afraid they’re ru...

True, but tieing to the second note seems a bit arbitrary. In tdlucas' example, the interval is large enough so as to make it quite clear that the first curve is indeed a slur and not a tie. Having clearly different settings for tie and slur placement helps, as well.

There are different thoughts about this last practice. I've always slurred to the last tied note as well, but sometimes, especially with a long series of tied notes, this leads to a lot of clutter. In such cases, it would be better to slur to the first of the tied notes.

It's most likely a bad setting. Prior to Finale 2016, you need to define two instances for every articulation, one for above the note and one for below, or one for note-side and one for stem-side. (I'm looking forward to not having to do this anymore with the next update!)

If you do it in Measure Attributes (Extra Space at Beginning), it will be fixed in eternity forever.

I’m looking forward to the new features. I just wonder how version 26 will treat old files.

I've had this a couple of times and I had to do exactly what you've done: split up the score into separate files.

Michel R E wrote:So if I'm getting this right, no matter what MakeMusic does with Finale, people will still bitch and moan?

I'll bet you'd at least remark on it if a company presented an upgrade to a word processor and the document they used to demonstrate the new features was full of spelling mistakes.

My favourite three Rossini jokes: When asked what he thought of Wagner: 'He has beautiful moments and horrible hours.' (actually he said quarter-hours but that doesn't sound so good in English) When asked what he thought after hearing Tannhäuser for the first time: 'That's an opera you need to have ...