Garritan does not appear in Virtual Instruments

I have Garritan Personal Orchestra 5 and Garritan World Instruments installed in my PC, they work in Sibelius 7, but in DORICO they do not appear under VST instruments, only my other libraries appear listed, Steinberg, VSL and Willander. I want to use GPO5 and GWI in a new project. Hope one of you can help. Thank you so much.

A few notes about Garritan.

A VST3 version of ARIA exists (The Mac VST3 version is fine) but the VST3 version for Windows is pretty broken and useless at this point. So much is wrong with it that you’d be better to opt for the Sforzando player if you really want a VST3 player for the Garritan libraries. The drawback to Sforzando is that it can only host one instrument per instance (where ARIA can host 16). Otherwise, Sforzando is fully compatible with properly registered Garritan libraries, including the reverb effects.

Windows users can still use the 64bit VST2 versions of ARIA in Dorico for now. You might need to add a path (wherever the ARIA dll plugins are installed on your system) and unblock them in the Dorico settings.

In the main Dorico menu, go to Edit/Preferences .
In the left column find the VST Plug-ins tab.

Find the ARIA Player Multi VST_x64 and ARIA Player VST_x64 plugins listed in the Blocked Plug-ins: column and move them over to the Allowed Plug-ins: column.

If you don’t see ARIA plugins listed, then you probably need to add a scan path, apply, and restart Dorico.

Common places ARIA might get installed include:
C:\Program Files\Vstplugins
C:\Program Files\Steinberg\Vstplugins
C:\Program Files\Common Files\VST2

Apply the changes, quit Dorico, and restart it.

Personally, I’m still able to run the VST2 versions of ARIA without issue in all of my Steinberg hosts (Dorico Pro 5 and Cubase Pro 13).

Typically I’ll use Sforzando VST3 unless I ‘need’ the ability to ‘channel bounce’ through sounds for complicated articulation scenarios (sometimes the key-switched versions of an instrument aren’t quite enough on their own, and Dorico allows expression maps that can bounce to new MIDI channels within the same plugin instance or MIDI port on demand).

It’s optional, but here lately I like to future proof my projects a bit by sub hosting ARIA instances inside something like a fully registered instance of bidule, or the free Kushview Elements.

A side benefit of experimenting with something like bidule or Elements is that you can bridge VST3 stuff into VST2 only hosts as well. I.E. Get your HALion Sonic and Groove Agent sounds working in stuff like Band In A Box, Sibelius, and Finale.

Don’t underestimate HALion Sonic! It takes a little practice to learn of its potential, but it really is a good sounding engine (yep, even just the basic General MIDI content) once you learn your way around it and master a few concepts on how to ‘mix and layer’ the content. Sonic can be configured into a General MIDI player that holds its own with some of the best fully automated GM player plugins on the market. Oh, a sidenote. Kushview Elements seems to intercept program change events for its own purposes…so another free option to get Sonic working in your VST2 only hosts is VST3shell. VST3shell bridges VST3 plugins into VST2 hosts. Elements and bidule can bridge plugins ‘both ways’.

2 Likes

Short answer: make sure you have the latest version of ARIA installed.

For Windows, it’s this one:

For Mac, it’s a newer version:

(Finale 27.4 installs a slightly even high version for Mac.)

Dorico uses VST3 by default: Sibelius uses the older VST2 format.

To my surprise everything is blocked, yet VSL Synchron and Steinberg work.
I am tempted to unblock everything.
The last one is Vienna Synchron Player Surround.

Because they have VST3 plug-ins as well.

Are VST3 Plug-ins not listed anywhere?

They are always whitelisted.

I have unblocked the Aria Players, they now appear and load but no sound, quite honestly, I am tempted to follow your advice for now “Don’t underestimate HALion Sonic” and just use Garritan in Sibelius 7.

In the Play Tab:

Have you connected a stave’s endpoint to an ARIA instance?

If the loaded sound is arco strings, wood winds, or brass, is the mod wheel icon in ARIA ‘all the way down’ where it’d be silenced?

For wood winds, brass, and arco strings you’ll usually want to choose a CC1/Mod Wheel dynamics based expression map to begin with. You can add more to it as needed.

For keyboards, mallets, percussion, plucked strings, you’ll want the default/velocity based expression map.

Try doing some searches here in this forum for the Garritan libraries. You should be able to find some good tutorials, and perhaps even some example expression maps to help you get started.

I see where benwiggy shared these very useful documents and expression maps some time ago:

P.S. I’m not positive the project will play straight away for you, but it’s worth a try…

In theory, since we are both on Windows, the project should load right up for you and play with ARIA right away.

Here I’ve set up a very basic GPO5 instance for the Hewitt Jones Dorico Overture demo that ships with Dorico. It uses the ‘multi’ output version of ARIA in order to isolate each instrument slot to a unique fader on the Dorico mixing map.

Hewitt Jones - DORICOverture MyMix GPO1.dorico (1.4 MB)

The project includes slightly modified (by myself) expression maps for the specific instruments used.

Here’s an mp3 rendering of the project you can hear through your browser:

Over the years I’ve learned that each score can require different approaches and adaptations to the expression maps. Typically I begin with an empty map that designates the correct dynamics style (CC, velocity, or both), and just add keyswitches or channel bounces as I require them. Initially I don’t attempt to invoke fancy legato, tremolo, or portamento features right away. Instead I simply allow Dorico to treat it more or less like a general MIDI instrument and ‘overlap’ legato phrases on his own.

Once I’m done sketching out a composition, I can go back and evaluate the features and abilities of various libraries and implement more of it.

With each new project you’ll learn more about Dorico, as well as the ‘strengths and weaknesses’ of your instrument libraries. Some things might work well at fast tempos, and sound pretty bad at slower ones. Some things can sound really bad at first, but then shape up nicely if you tweak out the max and min dynamic ranges in the expression map, and so much more. EACH SCORE you make will be pretty unique, so don’t try to overthink and build a ‘one super expression map fits all scores’ approach. I’ve tried before, and it’s just more trouble than it’s worth (plus I don’t have thousands of scores at hand to run tests with).

For what it’s worth, I sometimes even bounce off to a new stave (player) with a part in order to get a fresh new expression map for a specific passage (yep, even for the same ‘library’). I.E. A piece might have a lush largo section, and some bars later need a lively vivace sautille like sound. Sometimes it’s easier to just bounce things off to an entirely different instance with new expression map to get the desired change in score ‘interpretation’.

Keep it simple, and build gradually as you go, one project at a time.