Announcing: Dorico Expression Map Editor & Seeking Testers

Hi Dorico Community-

I’m excited to announce the Dorico Expression Map Editor, a 3rd-party (me) app which provides several features helpful for editing expression maps, especially large ones:

  • 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 types
  • Convert action types
  • View switch ID, enabled status, and articulation type in tables
  • View switch on events and switch off events simultaneously

See screenshot below.

I’m planning to offer it free of charge some time in February. It’s for macOS Mojave or newer.

I’m currently looking for volunteers to help test it. If you’re interested, please message me.

Many thanks!


I’ve decided to pin this thread to help David get a bit more visibility and hopefully recruit some testers.


And they’ll be a Windows version?


Would you consider using a cross platform framework such as Qt like Dorico uses to make it available to Windows users as well as Mac users?


Hi @Eggsalad,
That’s great idea to create 3rd party Dorico Expression Map Creator. Congratulations! :slight_smile:
@Andro is right about using the Qt Framework and make it cross platform.
I would recommend something very useful as an option:

  1. Since most of people are using existing Expression Maps sets as base for the new ones, would be nice if the Tool has a Comparison View option where the base Expression Maps set can be load (even more than one) and settings could be copied and pasted to one we are working on.
  • Here panel where we can see our saved sets at Steinberg\Dorico 4\DefaultLibraryAdditions folder will be needed with included search bar. Of course the path should be user definable in the Preferences of the Tool in order to fit different versions of Dorico.
  • Most probably the saving path will be the same, but should be should be available as different option. Personally I prefer to create Folders by Vendor inside the \DefaultLibraryAdditions
  1. Most of the people here, who create Expression Maps (I’m one of them) would prefer most of the settings to be organized as they are in Dorico’s Expression Maps Editor.
  • I really like that the Techniques panel is always visible on the Left.
  • The rest of the interface is a bit “unfamiliar” (looks way too different than the one in Dorico)
  • Don’t move too far away from what is familiar! :slight_smile: Just make it more User Friendly and make the workflow faster. :slight_smile:
  1. I would like to see a search bar for the “Techniques” panel, too. This is something I’m missing in the native Expression Maps editor in Dorico.

  2. Some good ideas for the organization and functionality of the Expression Maps editor, of yours, could be taken from Visual Studio Code Editor, too:

  • it’s very flexible and the appearance of the windows, panels… etc could arranged to the user’s preferences.

I’m wishing you success with the project! :slight_smile:

Best regards,
Thurisaz :slight_smile:

1 Like

@dspreadbury, thanks for pinning!

@wcreed & @Andro, I don’t have plans for a Windows version, but never say never. If I did at some point, I probably would look into Qt.

@Thurisaz, thanks for the good ideas! I’ll consider them for future versions. And thanks for the feedback on the layout. I’m still working with it. My preference is to see more info at once without expanding, tabbing, opening dialogs, etc. But I understand that means a busier UI substantially different from Dorico. Maybe I can find a better balance with it.


One thing I really miss in the Dorico editor is an Apply button, so changes could be previewed without constantly closing and re-opening the editor.


I agree. This app works as a standalone editor of library files and doesn’t have an audition feature, so unfortunately won’t improve that in particular. If Dorico implements a plugin API at some point, I’d look into it.

1 Like

I am happy to be a tester.

1 Like

Isn’t there some sort of plugin API used for the Stream Deck integration?

I believe there is a remote control API specifically for external devices. From what I’ve read, a more general plugin API is on the list for the longterm.

1 Like

Thank you! Will be in touch.

Hi @Eggsalad,

The problem isn’t about that the interface looks busy, but about the options ordering. :slight_smile:
I would like to have instant access to as much, as possible options on the UI, too.
My point was the options that are constantly visible in the Dorico’s E.M. editor, should
be placed at the exact same positions in the editor you are working on. Or at least similar ordering.
It would be easier for everyone who has experience with this function in Dorico to start from something that looks very familiar, and then explore the rest.
I have experience with the Expression Maps function in Dorico, Cubase, Overture 5 and Studio One.
I find the best one when it comes to organization is the one in Dorico. The best one for flexibility - Overture 5, allows you to create expression maps on fly while you are working on project. Probably the one in Cubase is the most advanced, but also the worst, of the 4 mentioned above, as organization and workflow while creating expression maps… :slight_smile:

Best wishes,

@Thurisaz, thanks for clarifying! The column layout is generally similar, but I’ll take a look at what might be too unfamiliar – what might be rearranged/removed. Thanks again!

as a Windows user, I can’t participate in this but I must say, the sort of features being offered are exactly the sort of thing I was hoping for in Dorico 5 and the effort is certainly to be applauded. Perhaps it will even give the team ideas!


G’day Eggsalad, I’d love to assist with testing. Please let me know what you’d like me to do.

1 Like

Thanks! I’ll message you.

I had message you… I’ll be glad to be a tester.
I’m using Mac OS Ventura.

1 Like

If cross-platform, now I recommend dotNet 6 in lieu of Qt.
Qt is made for C++ which is much harder to learn and maintain comparing to C# and Swift.

I personally prefer Swift, but its dev environment is hard to be set up on Windows.