New post
Avatar
0

After installing MacOS Sierra 10.12.1, Finale v25.1 now immediately crashes (unexpectedly quits) when trying to select any input tool (Simple Note, Speedy Note, etc) for me. Anyone else experiencing this?

13 comments

Date Votes
Avatar
0

No. Working fine here.

Comment actions Permalink
Avatar
0

Darn - although good for you. I was hoping that was the problem. I've tried removing then reinstalling Finale as well...same problem.

Comment actions Permalink
Avatar
0

Just to double check - you installed the MacOS Sierra 10.12.1 update that came out yesterday and you can select the Speedy Note entry Tool, for example, without crashing? All other tools except for the input tools work fine for me.

Comment actions Permalink
Avatar
0

Yes.

 

I don't know how to put a signature here but you will see it on the other forum where you posted.

Comment actions Permalink
Avatar
0

Just tried starting in "safe" mode - still crashing. Glad I didn't delete Finale 14.5...

Comment actions Permalink
Avatar
0

Of course it crashes in Safe mode. Only apps supplied by Apple can be expected not to.

 

Is there a crash log? If so, you need to attach it to a support request so that someone can figure this out.

 

I expect that the culprit will be a non-compliant plugin that is trying to load. I use Console logs and crash logs to isolate them on my system. These can be hell till you figure it out.

Comment actions Permalink
Avatar
0

MakeMusic has my crash logs, and a host of other diagnostics they had me send them. Are you savvy enough with crash logs to perhaps look through mine? I'd be happy to send it (don't see a way to attach a file here).

Comment actions Permalink
Avatar
0

Copy only about the first 15 lines and paste. Sometimes I get lucky.

Comment actions Permalink
Avatar
0

Date/Time:             2016-10-24 18:03:32.388 -0400

OS Version:            Mac OS X 10.12.1 (16B2555)

Report Version:        12

Anonymous UUID:        3EE7548B-D8BF-E6E8-1340-71C776096E15

 

 

Time Awake Since Boot: 840 seconds

 

System Integrity Protection: enabled

 

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

 

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)

Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000

Exception Note:        EXC_CORPSE_NOTIFY

 

Termination Signal:    Segmentation fault: 11

Termination Reason:    Namespace SIGNAL, Code 0xb

Terminating Process:   exc handler [0]

 

VM Regions Near 0:

-->

    __TEXT                 000000010c18d000-000000010e5d8000 [ 36.3M] r-x/rwx SM=COW  /Applications/Finale.app/Contents/MacOS/Finale

 

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0   com.apple.CoreFoundation           0x00007fff8895abf6 CFGetTypeID + 6

1   com.makemusic.finale.AIOLib.Bundle      0x00000001177419f2 ahLib::CharString::CharString(__CFString const*, unsigned int) + 50

2   com.makemusic.finale.AIOLib.Bundle      0x000000011773e7d6 ahLib::SoundOutMacX::EnumSoundDevices(std::__1::vector<ahLib::ahSoundOutDevice, std::__1::allocator<ahLib::ahSoundOutDevice> >*) + 486

3   com.makemusic.finale.AIOLib.Bundle      0x000000011773e44f ahLib::SoundOutMacX::SoundOutMacX(long) + 367

4   com.makemusic.finale.AIOLib.Bundle      0x000000011770aa9c AIOLIB_InitSoftSynth + 560

5   com.makemusic.Finale                 0x000000010cad5111 SmartMusic::AIOLIB::InitSoftSynth() + 239

6   com.makemusic.Finale                 0x000000010c1af137 SOFTSYNTH_DEV::ISOFTSYNTH_DEV() + 21

7   com.makemusic.Finale                 0x000000010c1b72f9 INTERNALSOUND_SOFTSYNTH_OUT_DEV::Alloc() + 21

8   com.makemusic.Finale                 0x000000010c1b6de5 AllocInternalSound(bool*) + 188

9   com.makemusic.Finale                 0x000000010cb2b18a UEnigmaMidiPlayer::Init() + 62

10  com.makemusic.Finale                0x000000010cb2b143 UEnigmaMidiPlayer::GetInstance() + 51

11  com.makemusic.Finale                0x000000010cb2b34f UEnigmaMidiPlayer::ReinitInstance() + 31

12  com.makemusic.Finale                0x000000010c7e0b9c MidiPlayer_MessageHandler(FINTOOLMSG, long) + 211

13  com.makemusic.Finale                0x000000010c940b6a ftool::SpeedyEntryToolProc(FINTOOLMSG, long) + 30

14  com.makemusic.Finale                0x000000010c4049ae ftool::SpeedyEntryToolHandler(FINTOOLMSG, long) + 513

15  com.makemusic.Finale                0x000000010c30f635 DispatchMessage(ftool::FINTOOLID, FINTOOLMSG, long) + 147

Comment actions Permalink
Avatar
0

Hi Paul,

 

I took a look at your support ticket in our system, and it looks like you were on the right track for clearing preferences, but I do want to confirm that this occurred since it could very well fix the issue and I did not see the specific file that contains Finale's preferences mentioned in your response.

 

If you save your work, choose Finale > Preferences, click the Reset All Preferences button, and then restart your computer and relaunch Finale, do you get the same behavior?

 

If so, I can update your ticket with that information and we can move forward from there!

Comment actions Permalink
Avatar
0

Resetting the preferences was the first thing I tried, and unfortunately it didn't work.

Comment actions Permalink
Avatar
0

FOUND IT!!!

 
I looked through the crash log again and saw some MIDI reports - I saw that after resetting the prefs, Finale defaults back to Play Finale Through MIDI. I changed it to Play Finale Through Audio Units and NO CRASH! I can use Finale v25 again! Can you/anyone confirm if this is a bug? I do not have a midi keyboard connected.
 
Whew!
Comment actions Permalink
Avatar
0

Finale defaults to the General MIDI sounds that are part of the Mac OS. I have a number of files that play through those sounds without a problem. 

 

It's possible that you were trying to access a MIDI controller that doesn't exist. It it's trying to load drivers that aren't there—or loading obsolete drivers, that can crash many apps. Normally, one uses Console.app to verify this.

 

The important thing is that you are going again. I learned a long time ago to stop diagnosing when the problem is solved. 

Comment actions Permalink

Please sign in to leave a comment.