Hi all,
just tried to alt+shift+arrow a slur and it increases by 8-note instead of note:
Latest update. I never encountered this before, the slur usually augments/diminishes by note.
Is your rhythmic grid set to the eighth note, by chance? (Not entirely sure that matters in this case.)
It is, but it can be set to anything – it does not influence this.
Also, it does not happen all the time, just randomly.
1 Like
This seems to be working for me. If it is ‘random’, then maybe there’s some other factor at play?
Probably. I have not been able to find the culprit yet…
Possibly that particular slur is linked to one in another instrument that doesn’t have a note at that position?
No, just added at that spot.
I’ve now tested this with 16th notes in a fresh file, with a 16th grace note and even a double barline before, changing the grid to different values, and I’m not reproducing it. So if it’s still happening for you, I think we’ll have to see a project.
1 Like
It has been happening to me, too, today. (One of the routine tasks with photoscore imports is the adjustment of slurs)
The infuriating thing is that it is not reliably reproducible. But once it occurs, the only solution is delete to the slur and re-enter.
So far, I ‘think’ it only occurs on XML imported slurs.
3 Likes
As soon as it happens again, I will try to see if I can post something.
1 Like
My colleague Richard spotted something last week that might be related, though it’s not new. If you drag the selected item with the mouse to lengthen or shorten it, then without deselecting it, continue to edit its duration with the key commands, then you will find that the key commands don’t lengthen or shorten by the expected amount. Once you deselect and reselect the item, it will start to work as expected again. I’m curious to know whether you think this could explain what you’re seeing.
1 Like
Yes. If I deselect/reselect a misbehaving slur it starts behaving properly (though these misbehaving slurs have never been dragged, they are just apparently normal slurs in an xml import).
This issue is resolved in this morning’s Dorico 5.1.51 update.
5 Likes
Nice to know, as this behavior stroke me too last week on a heavy loaded Dorico week! 