Cubase 10.5 randomly changes expression maps articulations on playback.

Cubase
,
#1

Hi there!

Cubase 10.5 randomly changes expression maps articulation on playback.
It’s happening all the time!, it’s diving me crazy!!

Sometimes when re-playing again, it plays properly a few notes and then it gets all messed up again until I play the whole phrase.
I keep re-playing things all the time, the amount of time lost just replaying things is absurd at this point.

Does anyone knows of a fix or at least a workaround?

#2

Hi,

Try to unplug all your connected MIDI Devices (to make sure no device sent any MIDI Note). Add MIDI Monitor MIDI Insert and check, if the Key Switch MIDI has been sent.

#3

Hi Martin, thanks for the reply!.

I’ll surely try that!, though, it seems strange, i’ve been using same controllers for ages without problems and it all worked fine with Cubase 10.

Anyway, I really hope that’s the problem, thanks for the suggestion!.

#4

Hi once again,

So I added a global midi monitor and there are no message being sent when these problems happen…just normal playback.
Also, when these problems occurs, the channels are not even being monitored or selected, and definitely not receiving midi messages, so I’m not sure the controllers have anything to do with this.

I also noticed that it’s not randomly changing to any articulation, is more of a not triggering the right articulation and playing whatever is the default one situation…which makes me think, Cubase is not triggering these at appropriate times.

The expression map on itself is rather simple, just triggering key switches, and it’s set as attribute instead of direction.

Does anyone else have similar issues?, anything else I should be looking into?
Any help (or even confirmation of a bug) would be highly appreciated.

#5

Hi

Could you provide s project snipped, where you can observe this, please?

#6

Hi arieln, I might be having the same issue -

  • Expression Maps will sporadically switch articulations in 10.5 during playback for no apparent reason
  • Direction changes are sometimes ignored and do not trigger an articulation during playback, but then start working again after a stop/start.
  • The issue is inconsistent, it seems to happen randomly, a few times a day
  • The same Articulation Maps work without the issue in version 10
  • Nothing going on in Midi Monitor, no other messages sending to the tracks…

for what it’s worth, I’m using only Direction type, and my switches are via CC

NB this is not the same issue as the classic ‘My Expression Map Resets on Stop’ discussion.

thanks

#7

This is a bug in Cubase 10.5 that anyone can reproduce. If the next patch doesn’t fix this problem, I’ll have to use 10.

#8

Hi,

I cannot reproduce it so far (so not anyone can). Therefore I asked you for a project snipped, please.

#9

Hi,
I’m having the same problem, and I may have found something.
I noticed that when I’m listening to playback then click elsewhere for playback to move to that location, it messes up the articulation/expression playback. BUT, if I press stop then move the cursor to a new location then start again, it seems to work ok.
However, there are still occasional glitches where it will just play the wrong articulation for seemingly no reason…hope this helps.

#10

Btw, I’m experiencing this using Iconica Sections and players…I will try to include a sample if its still desired. I would REALLY like to see this addressed in a future update…

#11

Hi,

When you press Stop and move the cursor, the Chase MIDI Events is applied. So the previous (last before the position, where do you jump to) values of the MIDI CCs are sent out. Probably this will be it.

#12

There’s no problem when I press stop and move the cursor, the problem is when I move the cursor DURING playback…then Iconica seems to get stuck on the articulation I was on before the jump. HALion Symphonic Orchestra has this problem too.
One workaround I found is to create a separate track for each type of articulation…which I might end up doing

#13

Hi,

Yes, this is what I tried to explain.

When you stop and move, all “last MIDI CCs” has been sent out (thanks to the Chase MIDI events enabled). So all articulation switchers MIDI CCs has been sent. If you don’t stop, these “last MIDI CCs” had not been sent out, so the audition doesn’t switch. And you have to wait for the next switchers.

Unfortunately if the instrument combines multiple switchers (to make a matrix, as it is with some VSL libraries), then it could be even more tricky and messy.

#14

Hi,

I have tested this with MIDI Monitor. Actually I was wrong. Even when jumping while playback the chase MIDI events has been sent to the out. So the Note Expression data has been sent out. So it should behave exactly the same way when Stop + Jump or Jump while playback.

#15

+1

Midi articulations are still misbehaving in 10.5.10.

This bug can be “reproduced” easily:

  1. Have an event with a defined articulation (i.e Sustain) and another with a different articulation (i.e Spicatto).
  2. Stop the playback at either of the events.
  3. Expression of the event where playback was stopped will temporarily “override” the othesr present in different events.

Sometimes it is almost impossible to get the right expression back. Number 3 is what I’ve found what triggers it, but it is not necessarily a 100% chance, since doing it to “revert” the expressions back doesn’t always fix it.

Sorry for grammar. English is my 2nd language.

#16

I’ve the same problem.

It is driving me crazy on some projects for which I have very little production time! :angry:

I can’t believe that an update brings so many problems in essential cubase functions! :question: :exclamation:

Expression maps were a feature that made me choose to switch to Cubase but if the updates are so full of bugs I’m afraid I’ll have to go back to the DAW I came from. :cry:

#17

Hi,

I’m sorry, I really try my best to reproduce it, but it does work as expected to me here. I’m trying with MIDI Monitor, so I do observe the real data which has been sent out. And from my point of view, this is always correct. So the only idea I have is that the sound library doesn’t handle the articulation switch correctly. Could you test with the MIDI Monitor and double-check, what data has been sent out, please?

I even tried to trick a Cubase and I set the articulation switch as High Pitch (C7, D7). Knowing MIDI sends the MIDI data from Pitch 0 to Pitch 127, I was thinking that maybe if the Articulation change is at the very same position, as the MIDI Note, the Articulation change will be sent after the Note (because of higher Pitch then the Note). But even this works as expected here, so the Articulation switch comes before the MIDI Note.

My test project is very simple (to be able to read the result).

  • 1 MIDI Track with Expression Map.
  • The Expression Map contains 2 expressions:
  • Legato: C7
    • Spiccato: D7
  • The MIDI Track contains two MIDI Parts.
  • Part 1 in time 3.1.1
    • Part 2 in time 9.1.1
  • Every single MIDI Part contains 1 MIDI Note at the very beginning of the MIDI Part and the Articulation switch at the very beginning of the MIDI Part.

Test

  1. Cursor at bar 2.
  2. Playback.
    -> The Articulation (Note C7, volume 120) and the original MIDI Note has been sent out at 3.1.1.
  3. Stop at 4.1.1
  4. Jump to 8.1.1
    -> No articulation data has been sent out.
  5. Start Playback.
    -> The Articulation (Note C7, volume 0 and Note D7, volume 120) and the original MIDI Note has been sent out at 9.1.1.
  6. Stop Playback.
  7. Jump to 2.1.1
    -> The Articulation (Note D7, volume 0 and Note C7, volume 120) has been sent out.
  8. Repeat the steps 2-3.
  9. Jump to 9.1.1 (where the 2nd MIDI Part starts).
    -> Nothing has been sent out yet.
  10. Start Playback.
    -> The Articulation (Note C7, volume 0 and Note D7, volume 120) and the original MIDI Note has been sent out at 9.1.1.
  11. Stop Playback.
  12. Jump to 2.1.1
    -> The Articulation (Note D7, volume 0 and Note C7, volume 120) has been sent out.
  13. Repeat the steps 2-3.
  14. Jump to 10.1.1 (in to the 2nd MIDI Part).
    -> The Articulation (Note C7, volume 0 and Note D7, volume 120) has been sent out at 9.1.1.

Could you attach your project, with the Markers, where should I stop, where should I jump, please? Could you try with the MIDI Monitor, to verify, what has been sent out, really, please?

#18

The problem may not occur with just one small instrument. Problems often arise in large projects.
In version 10.5.12, there are still problems with tracks using expression maps, such as the notes breaking during playback. So I’m still using 10.0 and no problems.
This is not just a problem with iconica. I use kontakt libraries.

#19

I am having this issue as well. I would like to send a project file but every time it happens it somehow fixes itself when I hit stop and start a few times.
Sometimes I go to the output mapping and move the order of the controllers around and this fixes it. I thought that it was a VI Pro issue. Now I am beginning to suspect that the problem lies with Cubase. :neutral_face:

#20

Hi,

Do you have the issue with a project without Vienna? How often does it happen. How high is the chance that if I would open the project, I could get into the state too? Is it like 5 of 10 Playback Starts or less or more?