I have followed the tutorials on using the simple drum set associated with Groove Agent Se. After adding the simple drum set, the VST and Midi screen shows that Groove Agent SE is in fact in place. But the Track Inspector doesn’t allow the Groove Agent SE to be selected.
I’ll try this again.
Yes. I followed this protocol:
-
Examine the Mac Activity Monitor - verify that there is no VST Audio Engine.
-
In Dorico, Create New - Empty project.
-
Re-examine Activity Monitor - now there IS a VST Audio Engine process.
-
In Dorico, review VST: - nothing listed yet.
-
On that screen, select “+” on VST Instruments, without any player, the VST Instruments “+” is not active.
-
Back in Setup, add an instrument “Create Empty Kit” to the existing non-player.
-
Examine the Play for VST instruments.
A bunch of non-instantiated entries.
Select the “02” entry, and navigate to Groove Agent SE
And I get a whirling disk showing the program is TRYING to do something.
But nothing gets done.
The Activity Monitor shows VST Audio Engine present and no reported Hangs.
I can sit on the Dorico screen forever, with no result. System is frozen. I can’t even Quit, unless I “force quit” at the system level.
After “Force Quit” Dorico (not responding), the activity monitor still shows an active VST Audio Engine process.
If I restart Dorico at this stage, I get a Warning popup saying the Audio Engine is taking too long to initialize, and either continue to wait, or terminate.
If I select “Terminate”, I get a popup "Dorico cannot connect to the audio engine. The application will now quit - single option “OK”>
There is a log generated, but it is too big for this forum entry.
But the VST Audio Engine process still shows in the activity monitor,
If I terminate the VST Audio Engine process in the activity monitor, I return to the state I started with in step 1 above.
I have tried other versions of this protocol:
e.g. Create an empty project, add a single player, unpitched percussion, Drumset basic. The VST window says that Groove Agent SE is in fact installed.
However, the track for the instrument just shows that VST in greyed out font, and won’t allow it to be selected.
but the Track Inspector refuses to acknowledge the Groove Agent, and the system is frozen.
Now, I don’t HAVE to use the Groove Agent, since other alternatives are available for percussion. But this should not be happening. The protocols I have followed are from the Dorico tutorials.
I have tried reinstalling Dorico 5.1.81 Application Installer, Groove Agent SE 5 - 5.2.20 Instrument (recommended) and Groove Agent SE 5 - Content (recommended), to no avail.
I am lost.
Upload your Diagnostics (Help>Create Diagnostics Report). One of the dev team will hep find out what is happening.
I have a “Dorico Diagnostics..zip” at 1.5 MB.
When I unpack it, I get 4 folders:
Activation Manager
AudioEngine
Crashes
Dorico
The total is 19.7 MB for 136 items.
Dorico Diagnostics.zip (1.5 MB)
I have generated another Diagnostic where the system started up correctly after I had quit the VST Audio Engine using the activity monitor. Here’s that file:
Dorico Diagnostics.zip (1.4 MB)
and here’s a Dorico file I’ve been trying to work with:
MustKnowDrumBeats.dorico (2.1 MB)
And here’s the diagnostics file after loading that file. As I indicated,
the drum set notation works, but the VST will not initialize to Groove.
Dorico Diagnostics.zip (1.5 MB)
I am running Sequoia 15.1.1
Hi @rudkinporter , thanks for the data, but actually in the log files I don’t see that Groove Agent would actually get loaded with you.
Your project file does work for me. I load it and it immediately plays back.
Please also do one more time, i.e. load your project and then create a new diagnostics report while still that project is loaded. Thanks
Loaded “MustKnowDrumbeats”. VSt & Midi shows Groove loaded. Activity Monitor shows a VST Audio Engine instantiated.
Dorico Diagnostics.zip (1.9 MB)
Also, can’t quit, because Dorico is not responding. Can’t quit. Can’t save. All Dorico prompts are inactive. Activity Monitor says “not responding”. Have to Force Quit. And also have to eliminate the VST Audio Engine process using Activity Monitor, otherwise, Dorico will fail in startup as per previous notes.