Finale Forum

Looks like you've got the 64-bit version of JW Staff Polyphony, which Zuill warned you about. That's why it's not showing up. Finale 2014.5 is 32-bit.

Here:

Try temporarily changing to this flavor of 12/8 before imploding. The function seems to be allergic to syncopation.

You want the .fxt file in the plug-ins directory, not the zip file. Look in Program options/Folders to make sure you've got the right directory.

Have you tried this? The G is 55, so try 56.

Or--though very unlikely--a fixed bug? I believe Ed has 2014.5 like me.

Here you go. I get this with Impode. Quantization settings?

And how are the repeats done? I have little experience with them, but when I apply them, the options to limit them to certain staves are grayed out. I suspect the O.P. is going to need a little detail.

Use the JW plug-in.

Implode or explode? Hard to know what you're talking about. It probably has to do with the shared notes (E's and A's). You might try JW Staff Polyphony instead.

This rang a vague bell, so I opened up Finale 2005 and the tenuto in the default document there has duration = 105%. I now remember having to fix that at some point. So perhaps RVS Lee's file is from an old version, or has music copied in.

The articulation has been duplicated. 63 has the playback effect, while articulation 7 doesn't, so that's why re-entering it worked.

The culprit seems to be the playback effect on the tenuto articulation setting the duration to 105%. Setting it to None fixes it, and doesn't sound any different that I can tell, at least with SoftSynth. I'm nut sure why just re-entering it worked.

zuill wrote: ↑

Sat May 30, 2020 3:02 am

or if I copied with the option regarding respecting instrument range, then the result is correct

With or without?

Zuill, with the misbehaving partial copy, was "respect instrument ranges" selected? Finale will "consider" (if that word can be applied to such a mess) the notes in the entire range of what you're copying in deciding what to "respect," and you will indeed get different results, depending. If I unche...

Bill Stevens solves the "respect ranges" thing--thanks. I didn't notice the minus signs--what a concept!

It would indeed be useful.

Why not use the normal SmartShape hairpins, which can be exactly the length you want?

And it's by no means the oldest of the bugs! Or the most disastrous. When you upgrade, by the way, Finale doesn't try to replicate your previous settings, but rather gives you a clean install every time. The brain-dead "respect ranges" feature appeared Either in Finale 2012 or Finale 2014 and was tu...

As am I and, I believe, Zuill. It's a mystery, then.

Anyhow, a totally wacky bug. "Respect instrument ranges" may cause the octave to change (often stupidly, see the link above), but I don't know why the fret numbers would run backwards. Been around since 2014.5, as I say.

If you're wanting this for your Brahms (just guessing), I think you need two symbols. It's important where they start and end. The swell may be OK for a single note.

mezza voce, "half voice." It may refer to using the soft pedal here.

I have been to Edit Text Expression Definition... > Playback, and tried everything I can think of. The expression has no playback effect. I don't think Finale will automatically slow down when it sees your expression anyway. Add an expression at the beginning and set the tempo to what you want with...

When this was first posted, I entered the music into a default document and it was fine.

Your bio doesn't say whether you're using a Mac or Windows. Perhaps therein lies the difference.

The bug exists in Finale 2014.5 as well. The culprit indeed seems to be "respect instrument ranges when copying" and gives an erroneous result whether lowest fret is 0 or 4, so I'm surprised it works for jzucker in Finale 25. My guess is this bug was introduced when this feature was added (Finale 20...