Finale Forum

Looks like in the first example layer 2 plays back on channel 10, general MIDI percussion. Where do you tell it to send whatever code makes the triangle sound for that space above the staff?

You should be able to just copy the passage one measure to the left.

As I say, JWChange will fix this, and I confirmed that the canonic utilities won't remove parenthesized cautionaries, so I think there's no mystery and no need to upload your file.

That will remove a multimeasure rest, not split one in two. "Break" is perhaps misleading.

Hey Motet, In the Measure tool, I tried adding "Create MM Rest-> Break" to the top line of the score. Then did Edit->Create MM rests->[all parts and not the score]. This did not break the MM rest in the parts. Did I misunderstand your suggestion? I guess so--I'm not sure what "Create MM Rest-> Brea...

That keeps the reduced note size from affecting it, anyway. The reduction due to scaling the staff, evidently not. I've seen people suggest adding a zero-line staff above for tempo marks to avoid that.

Right-click on the dynamic, pick "edit assignment," and uncheck "scale with attached note."

N, slipped in, but here was my reply: I don't know why you're not getting rests in the parts. You can create them manually by selecting everything (or the measures where you want rests) from the Selection tool, right-clicking, and selecting Multimeasure rests/Create. If you have put "real" whole res...

That seems to be gone, at least in 2014.5. Fortunately, it looks like JW Change will fix this. Look at Accidentals/Parenthesize/Hide. I tried the canonic utilities, and indeed it doesn't remove the accidental if parenthesized. Using "edit frame," I see there's an "accidental" flag, an "(accidental)"...

I wonder why the canonic utilities didn't work. Can you attach your file or a snippet thereof for us to play around with?

You can create a custom smart line in which a character is replicated. Read up on it in the manual.

"The score appears too long" doesn't seem like a very good reason to break with tradition.

Window/menu/toolbar layouts are not stored in finale.ini but rather in the Windows registry. I have successfully transferred such settings, and keep a copy of them for the occasions when the toolbars get messed up due to poor Finale programming (it seems to happen occasionally when Finale loses focu...

In Document / Page format / Score, check "Landscape." Then go to the Page Layout tool and pick "Redefine pages" from the menu.

Ferneyhough should have looked up "irrational" before coming up with this term.

I leave it on, too--big time saver over having to manually trigger it.

With the Window pull-down menu. I believe it just remembers which were last open and where. There are also a couple of palette options in Preferences.

To amplify what michelp says, you need to double-click-drag to draw a hairpin. that is, double-click where you want it to start, and keep the mouse button down after the second click and drag to the end point. If this doesn't work, investigate the double-click speed in your computer's settings.

I'm guessing it's the crash-reporting file. It sounds from the previous discussion that you didn't take the following advice I gave above. If you haven't, please try that. Quit Finale. In Windows Explorer, go to the C: drive and type CrashReporting (all one word) in the Search box. Delete any direct...

It should be something like

C:\Users\Djard\AppData\Roaming\MakeMusic\Finale 2012\finale.ini

Windows Explorer, not File Manager. Go to the C drive, then type finale.ini in the search box.

Not in the temp folder. Use Windows to search for finale.ini - that's it. It will be in your user directory tree, something like

C:\Users\Hokestra\AppData\Roaming\MakeMusic\Finale 2014.5\finale.ini

I wonder what the problem is. I can delete a G below the staff. Make sure you're in the right layer.

Try using Tools/Advanced Tools/Special Tools/Note Position Tool.

Could be an artifact of the display (try zooming in and out). If not, attach your file and someone will take a look; you've probably changed some setting.