Announcing: Dorico Expression Map Editor 1.0!

I’m happy to announce the release of Dorico Expression Map Editor 1.0! Thanks to those who helped test it!

It’s a standalone app which facilitates editing Dorico expression maps, especially larger ones, and works by importing and exporting Dorico libraries. Here are the key features:

  • Filter and sort switches
  • Cut, copy, and paste actions
  • Cut, copy, and paste conditions
  • Automatically add multiple switches with technique combinations
  • Edit multiple switches more robustly
  • Convert switch and action types
  • View switch ID, enabled status, and articulation type in tables
  • View note-on and note-off actions simultaneously

Dorico Expression Map Editor requires macOS Mojave or newer, and can be downloaded free of charge here:


will there be a Windows version eventually?

1 Like

He gave the answer in the other thread.

The first reply to this should have been Congratulations! And thank you!


I’m sorry, but I didn’t see another thread at the time. I only saw this announcement.

I don’t know if your 2nd sentence is a criticism of my question.
I was only asking a question, not complaining or anything. It was a simple question.

That said, I don’ know why “congratulations” would have been in order?
As for a “thank-you”, well, since a Mac version doesn’t do much good to a Windows user, that’s also a questionable response. And I posted that question: “will there be a Windows version eventually?”

Forgive me for asking a simple question and not responding according to your expectations.

1 Like

I’d like to do a Windows version eventually, but it’s not on the list for the near future.


1 Like

If I was Michel_Edward I would take this as an unnecessary slap. People are going to post what they want to post. Michel’s post was not snarky, just an honest question. I had the same initial question.


I will follow the progress of your editor in hopes that you will be able to offer a Windows version. Anything that makes Expression Map creation and editing more manageable is welcome.

Thanks for your work.


Some of the misunderstanding above would have been avoided if this thread had been appended to the earlier one (even if @Eggsalad had changed the thread title in doing so).

1 Like

First I think it’s great you made this App and present it free.

Than I wanted to ask something, that I wasn’t able to do earlier. And I’m afraid it’s hard to explain.

I use the sample Modeling strings N like them very much. Especially because they are relatively small. Many of the articulations are triggered by velocity CC. For example spiccato is triggered, when playing a short note at 127. Also note-transition ist controlled via velocity. If the second (overlapping) note is played loudly, the transition is short. When played very softly, it’s a portamento.

So here is my question: is it possible to map articulations to velocity? So when I notate spiccato, the corresponding note ist played at velocity 127. And when I notate portamento just the opposite?

I hope my question is clear.

There was a thread on this recently that exposed some problems.


Yes, you should be able to create a Base switch for Spiccato, and set Volume dynamic range to velocity 127-127. Apparently though, there might be issues with this which I haven’t seen.

1 Like

Is it possible with this editor to create custom playback techniques that match to add-on switches?
I’m asking because Dorico currently does not seem to be able to do this and it would be great if using your editor was a workaround for this problem.

No, not at the moment. If you import into the editor an expression map which includes playback techniques not found in the library file, it will create techniques to allow you to work with the expression map. But those techniques will not be exported in a way that Dorico can import them.

Exporting playback techniques in a Dorico-importable format is a feature I might add in the future.

You probably know that Dorico will display playback technique IDs in expression maps for any techniques not found. And you can then add the playback techniques manually, naming them strategically to match the IDs.

Well, it’s a great project, maybe at some point someone can give you a hand and help with making a Windows version come to life. It sounds like it would be an amazing tool.

1 Like

Writing a Windows version is as much as starting over, with probably little to save since this is mainly a data model. I’d suggest instead doing what the Dorico team did and rewrite it to use Qt, that way it shouldn’t be too difficult a port, you can stay on your Mac, and if you don’t have a PC somebody else could compile & test on Windows. I’d also suggest putting it up on Github.

Plus, it would look very ‘Dorico Like’ dressed up in Qt. Edit: I’m up to my ears in projects but I could help with Windows and Qt rewrite, I don’t imagine the app is too large so it shouldn’t be a big effort I’d think.

1 Like

Thanks for the offer! I’ll let you know when I go forward with it. Yes, I’d use a cross-platform framework like Qt or .NET.

.NET - I’ve been working in it professionally for 20 years, I don’t know what the licensing is for FOSS but if it works C# is impossible to beat for getting it done.

1 Like


1 Like

Happy to say I’ve just released version 1.1 of Dorico Expression Map Editor, which includes a few new features:

  • Cut, copy, and paste switches as a whole (in addition to actions and conditions)
  • Replace all instances of techniques
  • Export techniques (to facilitate importing into Dorico techniques added by Dorico Expression Map Editor)
  • Edit expression map creator, version, and description
  • Filter techniques by those appearing in switches
  • Techniques table automatically scrolls to first technique of selected switch(es)

There are also a few minor bug fixes and under-the-hood improvements.

To update from within the app, select Dorico Expression Map Editor menu > Check for Updates. Or, you can download a new copy at the link at the top of this thread:


Sorry, what is this about?