Three things control tempo in a Finale document.

They work in a hierarchical fashion:

1. The saved MIDI data (being at the top of the tempo hierarchy).

2. Expressions with playback effect Tempo.

3. The window Playback controls which is at the bottom of the tempo hierarchy.

In Other Words:

The tempo in the Playback Controls is overridden by an Expression that sets a tempo.
This is overridden by the saved MIDI data = the top of the "Tempo Hierarchy".

Did you press enter?

In one of my earlier versions of Finale, if I simply typed a new tempo in the playback controls it wouldn't change. In one, even if I clicked enter, it would SHOW 150, but still play 120. What I had to do was click a different value (like 8th=150) and then back to the original value (1/4=150) and it would then work. Hopefully bugs like that have since been worked out but I know in at least a couple of versions you couldn't just type a new value in then click away. You had to "enter" it in some fashion - watch the enter vs. return key.

Worth a shot.

OK - I've been using Finale for 15 years and have never posted in a forum until now. I've seen so many stupid bugs and things that are broken and nobody has answer for (including Finale tech support) but this one is pissing me off so much that I have to write something! I've searched about 10 threads and NOBODY has an answer to this that seems to really work!! Being able to easily adjust the playback tempo IS A SUPER SUPER IMPORTANT FEATURE!!! Why the hell make it so difficult? This used to work fine in Finale. In addition, even after I've done all the steps/hacks that now are needed to make it happen, it STILL doesn't change the F#%king tempo for me! Finale, this is the last straw for me. As soon as I have a break in my work I'm switching. And how bout sending me back the thousands of $ I've paid you!??

Adam,

Is this all of your files?  Can you send me one that isn't working for you? Send it to wawoodman at aol dot com.

Since you have not given us any information about what you have tried, I have to guess you are just venting. I hope that makes you feel better. If you tell us what you have tried, where your file came from (imported or created from scratch), and your preferred method of entering tempo, then perhaps those of us who like you are users of the software can help.

"If you tell us what you have tried, where your file came from (imported or created from scratch), and your preferred method of entering tempo, then perhaps those of us who like you are users of the software can help."

Puh-leeze.  Should not have to go to all this trouble just to CHANGE THE PLAYBACK TEMPO.  I'm with Adam.  Finale PrintMusic is the most counter-intuitive and nonsensical program I've ever seen.  Stuff to which you shouldn't have to give a thought consumes most of your energy and brainpower.  I dread having to make small changes because I know it's probably going to mean searching forums, etc.  Peter Thomsen was helpful in explaining the "tempo hierarchy," only leaving one thing out...how to change it.

Carl, we're trying to help. We're users, just like you.

Personally, I've never had a problem with changing the playback tempo. I suggested to Adam that he send me a problem file; I never heard from him.

 Mike and J Adrian how to I SEND you the file? https://www.dropbox.com/s/rrw1q1zun3kk7ui/Venus%20De%20Milo%20MNB%20v.1.musx?dl=0 

Does that work?

That works fine. I've got it. Specifically, what are you trying to do?

If it's easier for you, call me at two oh six, five two three, 9628.

I'm having the same problem Adam Theis described.  I created a song from scratch.  When I go to the playback controls and try to change the tempo the tempo never changes.  I have an iMAC running macOS High Sierra, version 10.13.4.  Finale 25.5.0.259

Mike Rosen, did you solve Adam's problem?  Please share.

The playback control wondow only affects the starting tempo. Use expressions to change the tempo. You can create as many as you, and you can even hide them in the score.

Thanks, Mike.  I was able to change the tempo by adding expressions.  Except, the expression would not take effect on the first measure of the song.  The count in was at the desired tempo, then the first measure plays at a much faster tempo, then starting on the second measure it plays at the desired tempo.  I tried over and over to set the expression to work on the first measure, but couldn't make it happen.

I think I need to scrap the song and start from scratch using the correct tempo when I create the song.

Thanks for your help,

Rich

Try this: Select All, Clear Selected Items > MIDI data.

Often, that will fix this sort of thing. You could also try exporting as an XML, and importing it.

Thanks, Mike!  The "Select All,...." didn't work.  But the export to XML and import back in worked.

Much appreciated!

Rich

Glad I could help!

There's another fix I just found - see here:
https://makemusic.zendesk.com/hc/en-us/community/posts/360006873574-Finale-suddenly-not-reading-my-tempo-expression

Set it to "no HP effect" - that should do it. You can change it back afterward and the glitch clears.

Finale 2014.d

Mac OSX Yosemite 10.10.5

OK, I had some success with Edit>Clear Selected Items>clear all midi data

However, on the playback controls, is there a way to 'strip out' all tempo commands? I set the tempo adjustment tool to 0 throughout which had helped before but I still have tempo changes in playback where none are marked in the score. Other times, the score shows a tempo change, which HP ignores.

The Playback control window seems really odd to me. On one hand, you are apparently defining tempos for different sections of your piece. On the other hand, you are telling Finale where to start playback. Why can't you have one without the other.

Here's the file in question:

https://drive.google.com/open?id=1S-r7wY79IvWhTSQ0W9XSQgs6uzuBuvmZ

I'll echo the sentiments of others that for Finale to have multiple and sometimes contradictory ways to control tempo seems pretty messy and frustrating.

The MM setting in the Playback bar sets a tempo for an entire playthrough.

It is overridden by any other form of tempo setting, whether by embedded MIDI commands or by expressions with tempo settings attached.

If you want to change tempo partway through a playback, I suggest you set tempo expressions at the appropriate measures and indicate/(customize) their MM settings.

Dear Community Experts,

Your various work-arounds on tempo playback are appreciated, but they are inefficient and unacceptable (in 2018!) to professional workflow. Consider how sequencing programs (Logic, Performer, etc.) allow you to *effortlessly* toggle between performance tempo and editing tempo (usually slower). So...

1) Is there a *straightforward* way for the PLAYBACK Tempo to override the MIDI and EXPRESSION tempos? This is very helpful when editing, and you need to toggle back and forth between the editing tempo and the final (actual) desired tempo.

2) Is there a way to custom-select the PLAYBACK click's duration-- again, even to override the MIDI or Expression metronome's duration? For example, your EXPRESSION tempo is quarter = 140, but for editing purposes, you'd prefer to hear half note = 70. This would help aurally chunk events that you're working with.

David,

Not that I know. But it's a good idea. Why not post it as a feature request, in the appropriate subforum?

Hi Mike, I have. Thx.

I'm with David on this one. I'd like to temporarily override the expression tempo to hear sections more slowly when editing. It makes sense to have this in the playback controls, and not have to switch tools to edit the real expressions or create new ones that you'll just have to go back and delete. It's counterintuitive to include playback tempo in the playback controls if it only works if there aren't any tempo expressions in the piece.

Do you know about Finale's scrubbing ability?

• While pressing CTRL and SPACEBAR, drag the cursor across your score. As the cursor strikes each note, you hear it played on your MIDI keyboard. You can drag in any direction, and at any speed, and from one staff to another. You might use this trick for checking chord voicings, scanning small sections for wrong notes, or just for fun.

Thanks, I didn't know about that. It seems useful but it doesn't seem to be working. I use Finale 2014.5 on a Mac/Sierra. I've tried CTRL and SPACEBAR, OPTION and SPACEBAR, and all sorts of variations of my SHIFT, CTRL, OPTION, COMMAND and SPACEBAR keys. It only works if I do OPTION+SHIFT+SPACEBAR, but that just scrubs back one staff. I'd love to hear the whole score. Tutorial 3 describes it, but it doesn't seem to function as stated. Are these directions just for Finale 25? (Also the video example in the tutorial is missing). 

J Adrian, Score scrubbing (not individual staff scrubbing) could use an important refinement: If a staff/track is muted, you should hear ONLY what is play-enabled when score-scrubbing. At present, Finale will play all tracks/staves, regardless of their play/mute status. Same with Staff Sets.

I figured out why score scrubbing wasn't working - I had to turn off the key command for Siri, which was also OPTION+SHIFT. (To do this, go to System Preferences/Siri/Keyboard Shortcut to change the setting). Now the score scrubbing works. Glad to know about it! Hope this helps someone else who tries to use it.

>While pressing CTRL and SPACEBAR, drag the cursor across your score. As the cursor strikes each note, you hear it played on your MIDI keyboard. You can drag in any direction, and at any speed, and from one staff to another. You might use this trick for checking chord voicings, scanning small sections for wrong notes, or just for fun.<

On my Mac, Option Spacebar does the same. Although a cool feature, it would be nice if there was a way that doesn't involve two hands (only one of my arms works).

>I use Finale 2014.5 on a Mac/Sierra<

Finale has to be in playback mode first. So hit playback, let it load the instruments and start. Hit the Spacebar to stop. Now, Option Spacebar lets you scrub.

I just tested it in Finale 2014.5 and PrintMusic 2014.5 over High Sierra. Although they will not install over 10.13 and aren't supported, I find that they work the same over OS 10.13 as they did over 10.12 (with the same limitations) if installed before the OS upgrade.

Well, everyone... I figured it out.

The problem is that if you create a tempo marking using the wizard when you first create the file (or any other time), the tempo marking itself sets the tempo for playback.

Here's how to fix the problem...

1. Select the Expressions tool...
2. Click on the first measure of your piece to activate the Expressions in that measure.
3. Double-click the Text Expression giving the Tempo for the piece.
4. Click "Edit..." for the tempo marking created by the wizard.
5. Click the "Playback" tab.
6. Under the "Effect" section, change "Set to Value" to zero.

Now, you can change the tempo using the playback controls on the main screen.

You're welcome.

David

David,

There's no problem that needs to be figured out. Finale is a notation program first and foremost. It's logical for the playback speed to be the same as the metronome marking, which is in the form of an expression. It's working as designed.

I suggest that you read this entire thread again. The various methods of controlling tempo are discussed including expressions.

Jeffrey, I didn't read every post, but I read enough to see that no one had identified THE place that controlled the tempo when the tempo marking was set.

And I have to disagree that there wasn't something to be "figured out." In fact, the only reason I found this thread was because I couldn't get the playback tempo to change no matter what I set the tempo to right there on screen in the playback controls.

Yes, it does make sense that playback should play at the marked tempo, but it certainly does NOT make sense that the playback controls' tempo setting would do absolutely nothing. My question was not "why does it play at 120?" But rather "why doesn't the tempo change when I enter 144?"

So, yes, I had to figure it out... And the solution I found was not articulated by anyone else. That's why I posted it.

David