Finale Forum

MAkeMusic responded: I've been able to recreate this issue outside of your document and I am writing it up as an issue for our developers. The fix for this will involve code fixes in the product so unfortunately I'm not able to provide a timeline for a fix on the issue. In other words, if there ever...

Okay, I understand that we are actually speaking of different things here. Some of you need to hear what you wrote, be it on a piano or by Finale's playback. Not to compose, but to check what you have composed. As I said before, composing takes place before there is anything to write down. In order ...

Jay Emmes, if you are implying that your music is in any way 'better' than the one composed with Finale, it would be interesting to listen to some of your compositions. Are they available on the net? Youtube? Soundcloud? Where do you read what you suggest I was implying? ____________________ MakeMu...

Just to be clear: Finale is a tool for notating music, right? Not composing, notating. Notating is not composing, notating is jotting down the result of composing. Finale is the substitute for the pencil and paper. And in some respects rather a poor substitute, in my experience. With a pencil (not t...

In other words (I'll gladly repeat my conclusion):
whereas

Really? Pa(dada)Pa(dada) is the same as Pa(daPa)da(Pada)? Please do me a favour: never play any of my music. Conclusion, however, is that there is a discussion possible when you notate two dotted quarters, whereas there can't be any discussion whatsoever when you notate dotted quarter, eighth tied t...

A syncopated note isn't necessarily a metrically accentuated note, whereas the second dotted quarter (fourth eighth) in a 6/8 measure by default is.

Not only is it technically incorrect to notate two dotted quarters, it also suggests a 6/8 time signature and thus a shift of rhythmical accents, which will very likely be audibly performed (only desirable if a huapango is what you want). Never notate a metrical division that is not consistent with ...

The full version of TG-Tools creates playback of a non-fingered glissando. It's horrible on the ears, but it's closer to what you want than an fingered (diatonic/chromatic) glissando.

They aren't glissandi. They're either 'hammer ons' or 'pull offs'.
See: https://www.fender.com/articles/how-to/ ... -pull-offs
Please also note how they're notated. It may solve your problem.

Thanks for looking into this. Your response isn't much of a relief, evidently, but at least it confirms that it's not just me or my setup. For playback purposes only, I could have three separate staves for every string instrument: one for bowed notes, one for plucked notes and one for tremolos. The ...

Is there an explanation for what is happening here? I know Finale has problems with HP. It should respond to text (such as 'pizz.' or 'mute') for making key switches, but more often than not it doesn't. However, until now I had the impression that Finale was pretty consistent in its refusal to do wh...

Software that isn't perfect can't work perfectly, simple as that. The fact that you have learned to accept the flaws and know workarounds for most problems, doesn't make the software more perfect. But not everyone is a long time user, knows all the workarounds. A helping hand in that case goes quite...

How can a software that has known bugs for years and years work 'perfectly fine' for anyone? Come on, we may not all have the problems that people report, but Finale is far from perfect and claiming that it works 'perfectly fine' for you isn't helping anyone, only aggravating the irritation of who a...

This bug was already present in Finale 25. It is very hard to believe that the bug was never reported to MakeMusic. Yet, MakeMusic didn't address this bug in any of the updates for 25 or 26 since. Business as usual, I'm afraid.

Thanks for your help. I have sent a PM with a sample document.

There is no need to attach a Finale file. The parameters of both figures are exactly the same. The only difference — and apparently the culprit — is the cross staff G (second 32nd note of the figure in the upper half of the image). When a figure consists of only one cross staff moment (lower figure ...

For some obscure reason Finale haphazardly decides to extend the upper beam in cross staff and reversed stem figures at one time, but the lower beam at other times. Why does Finale do that? More importantly: how can I convince Finale that extending the lower beam never ever makes any sense whatsoeve...

By the way, when are minims and quavers going to go the way of shillings and sixpence?

With a Brexit of sorts upcoming, I'ld say 'never'.

If Finale were really doing something to the file behind the scenes such as repairing it or cleaning up data, then you'd think if you immediately saved it and re-opened it, it wouldn't have anything to "change" the second time and wouldn't prompt you when closing. But it does. Not just that, but Fi...

Exactly. Yet, to get at least some bugs fixed, MakeMusic forces us to buy the next upgrade. And the next one and the one after that and so forth and so on, and still leave us stuck with a vast number of old bugs.

Why would they not make any money? Fixing bugs in existing versions doesn't exclude new versions with extra features. I do believe though that satisfied customers will generate more money, short term and certainly in the long run, than customers who will at one point turn to the product from another...

The file was created from scratch, that is with the set up wizard, and both tempo and time signature were set in the wizard panels. I have no idea whatsoever from where Finale derives the erroneous information.

I am wondering how useful the file information window (Finder:File>Get Info) actually is. E.g., for the document I'm currently working on, the window says "Tempo:69", but it really isn't. The starting tempo is 208 and nowhere in the document is 69. It also says "Time Signature: 4/8", but the first t...

Peter Thomsen wrote:It Would Be Nice If this cross-staff “pesky stem” shortcoming were fixed in the next Finale version.

Shouldn't known shortcomings and bugs be fixed in an update to the same version, rather than in (a paid for) next upgrade?