Feature Request: Sending control change messages without the need for expression maps

Hi,

Background:
In Sibelius, it is possible to send a control change message by simply adding a text item in the format ~C<controller #>,

My use case:
I am using the virtual pipe organ software Hauptwerk in a notation software context. I have a lot of different sample sets of different organs and for controlling the stops, couplers, swellers etc. of these organs, I am using control change messages. These control change messages follow a logical, well-defined system. However, since organs are vastly different, a certain control change message, in numerous instances, does different things for different organs and, thus, cannot be given a specific label that fits for all labels.

The problem:
To recreate this system in Dorico, I would have to manually create an expression map with entries for around 20 controller numbers with 128 values (0-127) each, which are 2560 entries to create. Yes, I am aware that this has to be done once only, but still, it is an enormous overhead that is only needed to make things work in Dorico.

My request:
There should be a way to add MIDI messages, mainly patch and controller changes, independently from expression maps. These could be either hideable text messages or a special popover.

See MIDI trigger regions:

Unfortunately MIDI regions do not allow CC messages.
For those you could use the CC tracks in the key editor…


Not ideal, but should work for your purpose.

Better, but still very tedious, as I would need at maximum 20 lanes and input it graphicallly.

well that’s a bummer … never used them but thought they would be perfect for OP.

As I said, not ideal, but I doubt any individual flow uses more than a few of your many possible settings.

I don’t own Hauptwerk, but have you considered trying to use Claude for something like this? I’ve had some mixed success with Claude and Dorico. With Percussion Maps, Claude hasn’t gotten it exactly correct, but it was way faster to edit Claude’s output than to create it from scratch. I would think Claude could be helpful with something repetitive like this if the VST is well-documented.

I don’t think there is. I use Hauptwerk daily and I tend to use only one sample set most of the time. I use a separate custom staff (designed however one might want) to which I had an automation (controller) in the key editor. I also had to define a specific channel in HW for this “instrument” staff. For example, I use CC90 for general pistons and sending a value 1 for General Piston 1, etc.

If you set up global CC values in Hauptwerk’s MIDI mapping that will match what you want to input (CC# and value(s)), it’s fairly easy to only send what you want to send to the virtual pipe organ. I use whatever controllers do not have a default assignment.

Does this help? I would love to be able to do as you do in Sibelius but I haven’t found a way to do that in Dorico.