Just a shot in the dark, but have you played with this setting in midi chase events
I can confirm that Expression maps are not working as tehy should here and sometimes do not work at all, even after 15.0. 10.
I believe that Cubase 15 maps are not chasing events correctly.
I have a habit of looping small sections in key editor and changing the articulations. I have snap on and know how to do this, but it does not work as expected and there comes a point when it simply downs tools and does not work. It’s hard to replicate.
Sometimes, clicking in hte inspector to change an articulation, means when I return to Key Editor, things do not work correctly.
For avoidence of doubt I think my prefs are set up corrrectly. I am on PC
Unfortunately not fixed in 15.0.21 build 252 
Hi,
How do you send the Expression Map triggers? Do you use Metagrid by any chance? Do you send Note On and Note Off? It’s necessary to send both.
Hi Martin,
I draw them in the keyeditor with the mouse. No Metagrid etc.
The only thing that works is if I unload the VST and load it again.
I don’t know what you mean by sending a note off ? -I can put a note-on into the “off-events” in the output mapping section, but that just gives me notes hanging .
The issue was fixed in the update a while back, it hasn’t been a problem in some time. So whatever problem you are having must be different.
Well - it is here
I’ve only tried with BBCSO. It seems like it loses connection with the EM. If I unload/reload the VST, it works for a while, but it gets stuck after a few slotchanges.
You mean that you’re somehow disabling or re-enabling the VST but leaving the track alone and not reassigning the map? If the expression map is being left alone attached to the track and all you’re doing is reloading the instrument then it implies that whatever is getting stuck is not the map but the instrument. I know BBCSO itself has had some rather serious bugs recently so I would try to be certain that you’re not running into that.
I just talked with Spitfire. It turns out that I had an old buggy version of the plugin.
I’ve updated and hopefully it should work now.
Thank’s for helping 
It did it again so I had another chat with spitfire audio’s chatbot - he’s quite intelligent
They wrote:
the current VST3 regression affecting BBC Symphony Orchestra: saved sessions can become unreliable, so one instance can stop responding to articulation changes while others still work.
Best workaround for now is to use the plugin’s Refresh button:
-
Click it to refresh the instrument.
-
Alt + click to refresh the entire plugin instance (same as “Refresh Plugin Instance”).
Hope this helps others with the same problem.
