HSO -- no sound?

I’ve been trying to change the VST used by my orchestral percussion parts, but although I can swap between NotePerformer and GrooveAgent, I can’t seem to convince any HSO-based players to makes sounds. I’ve tried many different percussion maps to no avail & it doesn’t seem like a MIDI mapping issue.

I’ve attached a one-bar sample of what I’m seeing. It contains 3 similar percussion parts that each uses a different sound library – HSO, GASE, and NP. HSO is the only one that doesn’t sound.

Sonatasorta TEST GB.dorico (1.2 MB)

Anybody see anything obvious?

Well, you’ve not got any sounds loaded into HALion Sonic, so that won’t help…

Uh-oh. Well, the NP or GASE players sound correctly, and I didn’t expressly load sounds into either of them.

I think.

Can you point me in the right direction? Apparently I still don’t fully understand all the basics re: loading VSTs into Dorico.

D

Either you apply a default plsyback template, which loads automatically the right VSTInstruments and loads the correct sound patches, or you go to the play mode where you do the same thing manually. On the VST + MIDI tab you can create new instrument instances, then you bring up the editor window and load the wanted sounds into it. After that you connect the players of the score to the appropriate slots in the VSTInstruments

@ulf

If I had the slightest idea how to build a Playback Template from scratch that would resolve this issue – my project is using NotePerformer, GrooveAgent, and, hopefully, HSO – that would be my first choice.

But in terms of finding a “default playback template” that supports all these VSTs, can you suggest one?

Thx.

Play>playback template…

Duplicate the NotePerformer template and add one of the HSO + GASE templates to it. Choose which instruments use which template as described here in the manual

Give it a name, then set that as the default in Preferences>Play>Playback Template.

1 Like

You know, Janus, half the battle with figuring out how to do something new in Dorico is identifying the function that the developers intended to be used to do what you’re looking for. Once you get to that point, the rest is often pretty easy. Usability v. learnability.

The problem, of course, is that you can’t identify the function that solves your problem, and read about it in the docs, until you’ve already figured out which function is the one that will solve it. A classic Catch-22 gotcha.

Anyway, thanks so much for the link. I’ll jump on this right now.

There is also a tutorial video from John Barron on this topic. You can find it here.

1 Like