Thanks Martin 
When it happens here -from an audible point of view- Cubase is selecting the first slot in the Expression Map, which for me is legato (long) samples. So the problem is easier to audibly detect if pizzicato or spiccato or short samples are playing.
Hi everyone,
I’m also having the same problem, random changes of articulations, articulations sometimes not switching and following an expression map change, it happens during playback as well as during exports. This really messes things up as i will need to export Vsti’s one by one and check if every note is played correctly.
I use Cubase Pro 10.5.20 and only use Spitfire Audio BBCSO Core Vsti with articulations.
Hope there will be a fix soon and wish you all the best!
This! I have to render each track and then go back and render the sections that didn’t work - sometimes moving just that articulation to another track to get it to work. Such a workflow killer.
Interesting that it’s not fixed on .20.
C’mon steinberg…a lot of us use this professionally and it’s costing us time and money!
Same is still happening here, Cubase has become completely unreliable!, i have long, big orchestral sessions, where each export takes ages, and I don’t even know if they are gonna export fine. Not only i have to re-listen to them and try and spot any issues, but I’ve had to re-render tracks multiple times, many times!, and I still keep replaying things over and over…
It’s very unfortunate that this hasn’t been addressed in 10.5.20, and that we’ll have to wait months? just to see if they care to fix it 
I’m sorry for the negativity, but this is extremely frustrating, it’s such a basic workflow killer!
This was working fine in Cubase 10!,
Please check out my report here Expression map articulation still held after part ends - Cubase - Steinberg Forums on my attempt at a EM issue repro, and see if you can repro it. ty
Yeah that’s perfectly normal behaviour.
Re: Issue. Today I had to change a Portato to a Legato because the next note that was meant to be a Crescendo kept being played as a Portato.
@Steinberg, Please fix this before November/December 2020. Thanks.
Please help me understand, does no one use instruments with no articulation with no keypress? How can that be normal? Is it possible that you are just accepting this ‘bug’ as normal, or? because it’s has been around for a long time?
So you would like it to go back to the first slot when there is no articulation data?. You are probably right, it should. I have never really thought about it. Maybe put in a feature request, 'cause I think Martin thinks this is normal as well. The whole thing needs an overhaul. They said they may take a look at it in 2037. 
Going back to the first slot is what it does currently, see this old thread 2014
What I’m saying here is that no articulation should be sent when none is used. This seems so absurd to me because the current ‘normal’ suggests I should go back to using keyroll for my articulations because expression maps is working normal.
Having midi data (EM) sent after a midi part ends is recipe for disaster with any midi instrument.
I have many instruments which are setup like this. Shreddage 1, Musiclab Realstrat, etc… Some of my instruments do have normal sustains on a dedicated keyswitch but these are more rare to find.
thanks for checking
I’m not sure it is sending MIDI after the note or part as you say. In this video you can see that after the MIDI notes end, I manually select a note thus changing the articulation. If what you were saying happens, happens, then I would not be able to change the articulation manually because there would be EM data being sent. But this does not seem to be the case. 2014…Wow
I’ve attached a video file showing all the f@^*$$$in audio bounces I had to do just to get expression maps to work properly.
This project works fine in Cubase 10 but in Cubase 10.5 it’s a lottery as to what articulation will play. Each time I play it, it does something different.
Fix please!!!
Cubase expression map bug.zip (1.03 MB)
Ok yes that makes sense. I am still learning but that looks like manually changing overrides the articulation.
Yes this has been happening to me - what a pathetic showing by Steinberg.
This software cannot be used professionally if it continually takes two steps back with stability and functionality.
I have noted a rise on facebook groups with dissatisfied Cubase users of late.
Get your sh*t together
I hate to agree because I’ve been a steinberg user for 17 years professionally including running an education suite with 15 copies…but …yep I feel there needs to be a little bit of a socks being pulled up…
I’ve actually just bought a licence for Reaper and although it’s a pain getting it to have something similar to all the wonderful features of Cubase, I’m happy to do it for the reliability and quick fixes they provide…
This issue is completely random. That is the clue.
Cubase is not reading EM data correctly during playback.
It is always during playback, never when auditioning articulations or just jamming on sounds.
And only when playing back multiple (6+) tracks that use EM’s.
Found a solution - go back to Cubase 10 (and start learning a new DAW)
Funny you should say that…
I’ve been on Cubase professionally for 17 years and have just started moving over to reaper to try and get a more reliable / bug free DAW However, damn!!! Cubase (when it works) just has such an amazing workflow for composing…
Hi,
From my experience of using Cubase, Pro Tools, Logic, Digital Performer, Studio One, Sonar, Live, Reaper, there is no bug-free DAW. The level of bugs is more or less the same.
Thanks Martin. Agreed there is no DAW that is issue free. However I completely disagree with “The level of bugs is more or less the same.”
I was studio manager / technical manager in a big London college for a number of years. I managed a suite of 15 macs with Cubase and Logic on them. By far, Cubase caused us more issues than Logic.
I also worked as a technician for a number of big name UK media composers and I found a similar situation both across mac and pcs. Cubase always caused more headaches than any other DAW I worked with
In my view, there are a number of issues at play here.
The first is: it’s the severity and impact of the issues rather than the quantity.
The second is the regression problem - updates from Steinberg invariably break things that were working before. Look at the issue we are discussing here as an example.
The third is that Steinberg seemingly use a waterfall rather than Agile / C.I methodology. This means regressions, which can often be showstoppers for some users, hang around for too long. Look at reapers methodology. Yes there are bugs but they get attention rapidly. Agile works! and is much more satisfying for both the company and the end user.
I don’t know how Steinberg operate their dev and testing cycles but my feeling is that they do not have a suitably robust QA in place or the ability to respond and release quickly.