Finale Forum

Okay, I am stumped...

I'm working on a new arrangement in Finale, a Big band version of "Music to Watch Girls By".. Notes are in, articulations added, and all it well.

Then I go to add in the expressions (FF, pp, etc) and it crashes, comes up with a crash dump list and tries to send it off to MM.

Okay, I say to myself, maybe there`s something amiss with the setup of this one file, so I go off to a tried and true document (with articulations and all in place) and try to change a p to an mp... crashes, not after I delete the existing, but as soon as I try to add the new articulation! In this case, it`s anything but a new piece, it`s one I`ve been using as a backing track for my guitar set for about nine months and it`s been played with dozens of times up to this week.

I've shut down Finale, cleaned up the temp files, and rebooted the PC. Nope. no help. Something has crept in while I wasn't looking, and now I need to find it and get rid of it!

I am also worried that all my pieces are in this kind of trouble, not to mention the small issue that I can`t put any articulations into newly-created ones.

Anyone else had this kind of crash?

I will likely open a ticket with MM about it if I can't work it out fairly soon... but it's Sunday. so if I can get it worked out before tomorrow, I may be able to add the fix to it.

Update- went in to C:\Users\username\app date\local\temp and found there are about 70 empty folders under FINALE... nothing in 'em at all. No crash dump info to be had, unfortunately.

Sounds like a job for the folks in Tech Support at MakeMusic.

By The Way:
You tell that you are using Finale 2014.5 - but according to your user profile you are still using Finale 2012c.
Perhaps it is time that you update your user profile.

Peter Thomsen wrote:Sounds like a job for the folks in Tech Support at MakeMusic.

By The Way:
You tell that you are using Finale 2014.5 - but according to your user profile you are still using Finale 2012c.
Perhaps it is time that you update your user profile.

Wups- updated sig.. forgot profile.

Will open a ticket.

I heard from Support and their second take on a fix seems to have worked. Two potentially corrupted ini files were removed. Here's the process. Note it's for Win7, but I am sure it can adapted to other versions if needed:

1. Exit Finale 2014.5.
2. Hold down your Windows key and press the letter R to open the Run dialog box.
3. Type "%appdata%" (without quotation marks) and click OK.
4. Navigate to MakeMusic\Finale 2014.5
5. Find and delete these two files:
FINALE.ini
FINMIDI.ini
6. Empty your Recycle Bin.
7. Restart your computer.
8. Relaunch Finale 2014.5 and repeat steps 1-3 above. Have the results changed?

And in my case, they did. I've opened and closed more than a dozen new and older files with mus and musx extensions, adding or deleting an expression or two. No crash.

If it makes it through tonight, I'll call it fixed.

Kevin

My Mac is crashing when I am entering Accent marks. I am assuming this may be the same problem. Any Idea how to fix on a Mac?

It may or may not be the same thing, but to delete the preferences on a Mac, look here:
https://makemusic.zendesk.com/hc/en-us/ ... inale-etc-

This happened to me last week, and I was given the same advice. What I did instead was rename the file with the extension .in_, and then restarted Finale. It created a new version, then I opened both in Notepad and compared. I was able to find the offending lines from the old file, excise them, and rename. Once Finale restarted with the corrected .ini file, everything worked and with all my pallets and tweaks still in place.

clancyweeks wrote:This happened to me last week, and I was given the same advice. What I did instead was rename the file with the extension .in_, and then restarted Finale. It created a new version, then I opened both in Notepad and compared. I was able to find the offending lines from the old file, excise them, and rename. Once Finale restarted with the corrected .ini file, everything worked and with all my pallets and tweaks still in place.

Out of curiosity, what did the offending lines say?

N.

In my case, things worked again when I deleted these:

SelExprZoom=0
SelExprWinpos=19 751 964 925
SelExprCatID=4

One of those numbers probably is out of range somehow and killed the function.

Not a programmer, so that's just a best guess.