When I add a second group and try to move articulations to the second group by right clicking on the articulation the clicking on “move to Group” I am not getting the option of group lists most of the time! I have to try multiple times or long left click on “ move to Group” to get it appear. Anyone can duplicate that?
Vicken,
Yes, I have had the same issue on Win 11. Discovered that it is easier to press the arrow button below to move articulation to the chosen group.
cheers,
JDTune
we’ve improved reliability of that particular context menu in an upcoming patch release, sorry for the inconvenience. As JDTune mentions, the button below will work.
Thank you everyone
It seems the vst expression maps have to be improved, look at this video made by Cubase team on Youtube, there is a tricky pizz marcato then marcato ….The articulations should be simple to take place one after other…
Why on the video the staccatos are on the map as “Direction” it is not the way it should be but “Attribute” with this articulation ‘ on top of head note….
This situation isn’t ideal, but there are circumstances where it can occur, and it’s hard to think of a set of rules that will satisfy all situations. If you have a plugin which has a separate sample for pizz + marcato then the expression map will have pizz and marcato in different groups.
The attributes are properties of a note, and the attributes themselves don’t know which group they are in – that is a property of the expression map. So if I have (eg) a VSL violin which can play pizz+marcato then and I add those attributes then they will be shown in different groups. Now I copy this part to a track which doesn’t have pizz+marcato. What should Cubase do? If it deletes either the pizz or the marcato then that is bad because it’s deleting data. If the user wants to change this back to VSL then the data is lost.
Cubase does show you in this instance which slot gets chosen in the lane above.
It shouldn’t be the case that the staccatos are Directions. It’s certainly possible and the way that some users prefer to work, but it’s not the recommended way. Which video is this?
direction but attribute
Previous feedback we have had is that spiccato isn’t always notated like this. Sometimes it is, sometimes a text indication is used and sometimes it’s implicit and not updated at all. So it could be an attribute or a direction. This is why it isn’t automatically mapped.
Spiccato is typically best notated with the direction text “spiccato” in addition to staccato dots. The staccatissimo wedges are not a standard way of notating spiccato, as Paul says. They can be used for staccatissimo, but even for a staccatissimo they can be potentially ambiguous, meaning either a short staccato or an accented staccato (halfway to marcato) depending on the time period and the region the score comes from, so I don’t usually see them used in modern scores for this reason (and if used you’d probably have to have something at the beginning of the score explaining how it is to be played). Also, what sample libraries call “spiccato” is not always so, there are sometimes a few different techniques involved depending on various factors like how fast/loud the passage is, and only one of those is actual spiccato proper.
The spiccato text indication is often hidden as it is redundant - in most situations the spiccato will be so obvious that it doesn’t have to be marked. But the spicc. text together with the staccato dots is the best way in the cases where it should be. The “spicc.” text is a direction by default, as it should be.
1 Like
Thank You, Paul , it will be nice to have both way to write it 
Thank You Mr Ducharme, I have been trained by my Master to write with the accent on top of the note 