Dorico Expression Map Import from plugins

It would be great if Dorico could implement the import of keyswitches via expression maps from the plugins that currently allow it (EastWest’s Opus VST3 for example) just like you can with Cubase/Nuendo.

While companies could make/create expression maps for the way an instrument loads up by default, it doesn’t really account for all the ways users enable/disable and move articulations from their default to a custom setup on any given instrument, so it would be more advantageous to utilize VST3’s ability to import those settings from the plugin directly.

Welcome to the forum, @pluebellify. I understand you’ve also been in touch with our support team in the US to make this suggestion, and that you might have an undeclared interest in doing so :slight_smile:

It would of course be useful to be able to extract information from the patches loaded in the current plug-in, but that will still not be sufficient to make an expression map automatically, as the subtleties of things like which note lengths should be mapped, which switches should be base switches versus which should be add-ons, etc., will still require detailed knowledge of the way the instrument works and how to best map that onto the capabilities of Dorico’s playback.

Certainly! Was just asked to also post the request to the forum (not trying to be sneaky - I do work for EastWest/get customers requesting this on occasion).

Definitely understand there’s more detailed knowledge required/more details to set in Dorico. An import to ‘base’ switches to at least a keyswitch note would at cut some of the build effort for custom expression maps (where you might still need to then edit add-ons and playback techniques to trigger elements) for at least the most common articulations that are already pre-mapped.

I guess the problems here are multi-layered.

  1. End-users struggle because there is no consistency between each Library as to how their products are controlled. (Here I applaud Spitfire for UACC, it is useful, but by no means perfect)
  2. In the real world, there is rarely any correspondence between the notation on a score and any particular library’s available patches, regarding how the composer/arranger wants the sonic outcome to be.
  3. There are fundamental problems relating to the articulation of legatos (specifically the attack of the first note of a legato phrase)
  4. There are huge problems relating to the relative dynamics of short and long patches.
  5. … (many others)

It’s an intriguing idea that Notation might become commercially more important than DAW for sound library vendors.