Thanks for your feedback. I guess your issue and mine shall be separated as two cases from now on.
==== UPDATE: I am gonna mark the bug-tracking thread of my case as “temporarily closed”.
Meanwhile, I am waiting for Steinberg to do further tweaks to Dorico, making it unable to prompt for controlling the computer.
I feel that this isn’t an urgent matter. Maybe Steinberg would post an article instead, telling Dorico users to uncheck Dorico from the listed apps under “Security & Privacy → Privacy Tab → Accessibility → Allowing the apps below to control your computer.”
Alex, no new update is imminent; we released the Dorico 2.1.20 compatibility fix for Mojave yesterday, but I doubt that will have any bearing on your issue.
Please do send me the information from the ‘You quit Dorico because of a problem’ window. You can email it to me at d dot spreadbury at steinberg dot de.
So I just tried to open it again this evening, betting that it would work. And no. So there goes my hypothesis about Dorico not being a morning person. It seems there is no pattern, or I mean, I couldn’t detect any causes or reasons for it not working. I will send you the files, thanks Daniel.
There’s a new version? Is it supposed to show up in the Steinberg download assistant? I only see 2.1.10
You only need to download Dorico 2.1.20 if you’re running Mojave; it will in any case almost certainly make no difference to your problem, I’m sorry to say.
Update: After Dorico not launching for 3 days, I downloaded the 2.1.2 update, as I am running Mojave, installed it, and again, no launch window came up. The force quit window said “Dorico not responding” as per usual, and just before I was about to force quit, a window came up asking me to allow Dorico to control “synsopos”. I can’t remember exactly what I said, because I clicked ok, and all of a sudden Dorico launched. I then wanted to see if this synsopos action was related to my problems, (as I’ve never seen an app ask for this before), so I’ve just quit Dorico and now relaunched, and unfortunately, back to no-go.
hmmmm. Damn. Had a glimmer of hope there.
Alex, go to Security & Privacy in System Preferences, and check the ‘Automation’ list: Dorico should appear in that list.
You will see that kind of dialog asking you whether you want to allow an application to control another application a lot more often from now on in Mojave, as it’s part of a new set of security features that Apple has added concerning allowing applications to talk to each other.
In the specific case of Dorico, it’s vital that you click ‘Allow’ when the system asks you if you want to allow it to control the application ‘Synsopos’, because Synsopos is part of the eLicenser system, and if Dorico can’t talk to Synsopos, it can’t communicate with the eLicenser, and therefore it cannot run.
Everything we are seeing in your logs etc. suggests that the problem is that Dorico cannot communicate with the eLicenser, so my suspicion is that Dorico is currently disallowed from communicating with Synsopos by these new security settings on your computer.
Sorry I haven’t been out busy with rehearsals for a couple of days. Daniel thank you, I went into security and privacy and checked the ‘automation’, and it was already ticked. Dorico has started twice in the last few days, since my last post. But I have tried many times, so the percentage, is still not favourable that it will launch.
I have noticed a strange behaviour though when it does launch. Maybe it is related, maybe not: For the past few weeks I have been doing a lot of transcription, and in a previous post I mentioned I use the little app Capo to slow stuff down. Usually I have Capo open when I am working. And if I decide to give Dorico a try, and it actually launches, it changes the audio output of Capo drastically. Like blow-up-my-monitors, kind of drastic. It’s bizarre. What it seems to be doing, is Dorico is either messing with something in Capo, or my computers output. I haven’t got a detailed account of the levels when it happens because usually it’s a giant brutal surprise and I jump and shut everything down.
What else can I tell you about my system? If the signs are pointing to Dorico not talking with the elicenser, how should I proceed? Reinstal?
Sorry anyone paying attention to this this thread, I was away from my computer for about a week playing some music.
This might be some help to developers:
I’ve gotten back to work here at the studio. I just tried a little experiment. This morning Dorico launched, it took a while for the launch screen to appear, but it eventually did. Pleasantly surprised, I decided to quit it, and relaunch to see if it was a just a lucky break. I quit and relaunched, BUT, this time, just by chance, I had my transcribing program ‘Capo’ playing music when I launched Dorico. And this time Dorico would not respond. I thought “ok, I see something here”, and stopped playback, force quit Dorico, and relaunched, and it bam, there’s Dorico ready to go. This of course could be just coincidence. Or not.
Same problem here since Dorico 2.1. The problem persists in 2.2; there’s no telling when Dorico will open or when it will hang on startup. And even when it opens, it takes about 1 minute loading before the startup window appears.
Josue, I suggest you follow the advice that we have been giving to other users affected by this hang on start-up: run the eLicenser Control Center, and leave it running, before you start Dorico.
Thanks Daniel, but the problem persists even when running the eLicenser (updated version, with updated database). I’ve just tried it opening and closing Dorico four consecutive times: the first try it took about 1 minute starting up, but it started. Second try, it took longer to start. Third try, it started up in less than 30 seconds. Fourth try, it didn’t open at all; froze on startup.
Can you please do Help > Create Diagnostic Report next time you’re able to start Dorico, and send me the resulting zip file (which will be saved on your desktop)? Thanks.
First of all, thanks for your persistence in addressing this issue. I’ve had a similar issue of Dorico hanging often on launch in Mojave, and I recently contacted customer support about it …but then got sidetracked by holiday music duties.
Today, I am back on this, and I have:
—disabled my antivirus & web protection software (Sophos Home)
—uninstalled (using the list of four files/folders in Daniel’s helpful post earlier in this topic) and reinstalled Dorico 2.2
—updated the eLicenser Control Center to its latest version and allowed it to do maintenance tasks before launching Dorico)
—tried leaving the eLicenser open when launching Dorico
—confirmed that Dorico 2 has control of both Synsopos and Finder under the Privacy Tab in System Preferences > Security & Privacy
No success so far. Dorico still hangs/freezes some of the time on launch and requires Fore Quit and trying to launch again. I was able to create a diagnostic report when the application did launch, and have attached the zip file.
On an unrelated positive note, I premiered a new work at the end of Advent, just days before Christmas, and my parts and scores have never looked more beautiful or been more functional! The implementation of Cues has been a dream lately, and the latest incremental update with Tap Tempo and other improvements was particularly timely and very much appreciated. Transitioning to Dorico has helped me significantly improve the quality of my finished sheet music output and my drafts during the composition and rehearsal process. For this, I am thankful to and have great admiration for Daniel and the entire dev team and support team.
You should find, Dave, that if you run eLicenser Control Center before you start Dorico, and leave it running, then Dorico starts up reliably. We’re working on this problem and hope to have a solution for it soon.
In the meantime I’m glad that Dorico was a good partner for your premiere before Christmas. Congratulations!
Both eLicenser Control Center and Dorico 2 are asking permission to control “Synsopos” in my Mac. No idea what does it mean, but after I denied, Dorico wouldn’t open. Then, trying to open one more time, it asked for permission again. I accepted. Dorico still doesn’t open. Tried to open one more time… This time, it did open although it took ages. But at least, I could get my work done today.
