Do you restart the computer on a fairly regular basis? Maybe it’s some cache not being emptied.

If I restart Finale (not the computer) it Undo works for a while. Other than that I usually shut my computer down over night.

In Preferences, have you tried changing the maximum level of undo to unlimited?

Are you running Big Sur?

There is a known problem where dragging a tuplet can break undo under Big Sur.............if you opened the doc with certain tools active (handle based tools like tuplet, expression, articulation, chord etc.)

Are you running Big Sur?

For that matter, what else don't we know?

https://makemusic.zendesk.com/hc/en-us/community/posts/215729367-General-Discussion-House-Rules 

Really, we don't read minds.

Yes, I am running latest version of Big Sur.

Setting Undo Levels to unlimited doesn't have an effect.

And I am sorry to have broken any protocol.

2017 iMac and Undo is important to my work - even though "Do" is more important.

Peter

Hi, Peter,

It's not so much a protocol as it is you telling us everything you can to help us help you. This is a Users board and we all have different levels of experience. Sometimes a person might list things thought unimportant and one of us will recognize it as the source of the problem.

If you haven't used the Submit a request link at the top of the page to submit this to Tech Support, you want to do so. If they get back with a solution, please post it in this thread. The object is to solve problems and help others.

Hi Peter,

I, like you am also using Big Sur and am finding that the Undo function does not always work. This is incredibly frustrating. To have to remember that dragging a tuplet can break the undo chain is not a solution. [And while on the topic of tuplets, I've noticed that the responsiveness of the tuplet to placement adjustments is very sluggish/clumsy.]

I wish Finale would solve this problem. I have already lost quite a bit of work (and time!) trying to recreate what I thought the Undo function would have been able to do. And while this problem may not occur in Mac OS Monterey, for those of you who use other music-related software will know, updating to the latest Mac OS sometimes means losing functionality and/or the ability to use your other software. 

Please Finale, fix this. 

Something you can try: When it stops working, open Terminal and type the following:

sudo purge    

then hit the Enter or Return key. This clears unused RAM and does nothing else—not as completely as a reboot but better than not doing it.

Terminal will ask for your Admin password. Type it in—will not show when you do so—then Enter or Return again. You can Quit Terminal when done.

It cannot hurt anything and will likely do nothing but, if the process comes back to life, you have a memory leak in some app (especially Office) or plugin or browser window. It does not have to be anything to do with Finale. In that case, time to use the Activity Monitor to diagnose the issue. 

If you don’t reboot daily, try that and see if it has an effect.

Hi Mike,

Thanks for taking the time to respond. Btw, Iike Peter, I'm also using a 2017 iMac (Big Sur with Finale 27)) and my machine is barely 3 years old.

I tried what you suggested but this had no effect. Furthermore, I typically boot up my machine 1 or more times every day and have the Undo limit set to unlimited in the Preferences. 

As was mentioned by Greg in an earlier thread, using the tuplet tool is definitely causing problems and I can't help but think the unresponsive nature of the tuplet to attempts at repositioning it on a page is related to the the non-functioning Undo. Undo works as long as I have not tried to reposition a tuplet. However, once I do reposition a tuplet, which I can only do accurately using the keyboard arrow keys (it is impossible with the mouse) Undo no longer works. Furthermore, if I then close the file and re-open it, Undo still doesn't work. I need to close the Finale program and then re-open it for Undo to start responding again. 

I still have Finale 25 on my machine and I don't experience any of these problems when using it. So there is definitely something in the Finale 27 +  2017 iMacs + OS Big Sur mix that is causing problems.

Ideally, I would like to resolve this matter without having to return to Finale 25 or upgrade to Monterey. Not being able to rely on the Undo function is not viable. 

Any advice would be greatly appreciated. Thanks

Hi,

I upgraded my 2017 iMac to Monterey. Still getting extremely sluggish triplet editing response in Finale 27. Undo so far seems to work fine. 

Peter

Hi Peter,

Thanks for pointing that out. I'm not completely comfortable upgrading to Monterey just yet because some of my plugins in other music software programs aren't ready for it yet. 

However, one work around solution that appears in the Finale Knowledge Base is to open your file, select the Simple Entry tool, save the file and then re-open it again.

This seems to be working for me so far.

Honestly, though, I'm not sure if this  problem is due to Finale V27, OS Big Sur or the 2017 iMac.  

Thanks for the tip with Simple Entry tool. What bugs me most is how long it takes to address these issues. At the same time, when Finale was my only notation tool it would drive me crazy. I have been slowly transitioning to another application. It also has its flaws but I can work faster in it.