Crash on Startup - Finale 25 and Sierra – Centro de Ayuda de Finale y Garritan

TIMOTHY ROLLS Posted 9 de enero de 2017 01:43

Hello all,

I am on Finale 25 and OS X Sierra (10.12.2). I went to open Finale on my iMac for the first time in several weeks today and I get an error message when trying to open saying "Unresponsive during engine initialization." It is happening on both of my computers (iMac and MacBook Pro). Is anyone else seeing this? I recently updated my Native Instruments stuff, so it might be that, but I want to check if anyone else is seeing this error before I try disabling all of them.I didn't see anything in the forum about this, but may have missed it.

Regards,

Tim

5 comentarios

Fecha Votos

MIKE HALLORAN Editado 9 de enero de 2017 02:01

I got it after updating my NI stuff, too. Reopening it again, the message went away and I haven't seen it since.

if it doesn't behave, shut down and Boot in Safe mode by holding the Shift key—this will take awhile, especially if booting from a spinner—that's ok. After logging in, shut down and boot normally. This will reset paths and caches to default. One side benefit is that it will also restore alias icons. This should be done once a year anyway.

TIMOTHY ROLLS Posted 9 de enero de 2017 02:04

Thanks for the response. Mine kept happening over and over. I just found on the support site a new script that seems to have fixed it. I'll let you know if the problem pops up again, but for the moment I can get into it.

Regards,

Tim

MIKE HALLORAN Posted 9 de enero de 2017 02:34

Ooooh... please post a link to it.

TIMOTHY ROLLS Posted 9 de enero de 2017 02:39

This is the link I used. It came up when I was trying to send in a ticket and while I wasn't sure it fit my issue, I tried it and it worked. Follow the instructions to the letter, there are FinaleScript folders in 2 places and if you replace the wrong one it won't work and may make things worse.

https://makemusic.zendesk.com/hc/en-us/articles/236222307?input_string=finale+25+won%27t+start

Tim

MIKE HALLORAN Posted 9 de enero de 2017 03:22

Thanks for the link. I'm glad they finally released a fix for the FinaleScript issue.

Glad it worked for you. Perhaps I got lucky. Interesting that we both encountered the problem after updating NI—for me, it was to Komplete 11.

Iniciar sesión para dejar un comentario.