Changing VSTs and Expression Maps

Hello,
I’ve noticed that pretty much every time I switch away from default vst sounds in horns the playback starts playing this low Drone. This has become very annoying. Sometimes I can fix it by switching sound into another channel of the plugin but this time it didnt work at all. It stops when I press the note in the plugin keyboard overlay. I noticed it mostly with brass instruments but could also apply to other horns I’m not sure.
And I cant really avoid this because a lot of the default sounds especially for horns suck.
I recorded an instance of it here

Is this your VST or Dorico’s (by “Dorico’s”, I meant a different patch to the default patch that is loaded in Halion)? If Dorico’s, you could try resetting the Playback Template.

Dorico uses Expression Maps (multiple of which can form Playback Templates) to interface between Dorico and the relevant VST. Many VSTs use low notes as key switches to tell the VST how to switch between different patches, e.g. one low note could be used for a sustain patch, another for a staccato, another from tremolo etc. This is convenient for live performance of VSTs from a MIDI keyboard, as the left hand can change the sound while the right hand plays the melody.

Expression Maps allow Dorico to do this patch switching automatically when “reading” your music.

However each VST manufacturer uses different keyswitches. If you’re using an instrument that uses one Expression Map, you can’t expect the same Expression Map to work with a different instrument from the same manufacturer, let alone another completely different instrument from another manufacturer. You need to also change the Expression Map.

The low drone that you’re hearing is the result of Dorico sending a key switch to an instrument that can’t understand that key switch; the instrument is then playing it as an audible note.

Hopefully this explanation gives you some guidance as to what to read up on in the manual.

I’ve taken the liberty of editing the title of this thread, as
a) it was unspecific about the actual issue and
b) this isn’t a bug; it’s a lack of understanding on your part

2 Likes