Thanks Charles for the work around. It seems to have resolve the issue.
Martin C.
Thanks Charles for the work around. It seems to have resolve the issue.
Martin C.
Hi Charles, I’m trying to do the trick this morning but I’m afraid I’m lost after creating the tuples (2:1).
You say to enlighten them and turn them back to an 8th note? Are you talking about the sixteen note or also the rests?
I presume the answer is the 16th note. Then I’m left with 2 X 8th note, a 16th note rest and a tuplet (2) indication.
I’m stuck there. If I delete the rest (Édition>supprimer les silences), I have 2 unbeamed 8th notes with a number 2 below. No way I can beam them back together without deleting the number 2, which removes the tuplet.
What ever I try I don’t get the result expected.
What I’m I missing?
Martin
You’re here in Galley View, isn’t it OK in page view?
Same thing in Page View.
In your cut-down file, it was all right in Page View (and not in Galley View), that’s why I was asking. So I’m afraid you’ll have to tweak a bit the note spacing in Engrave Mode, probably in both Score anf Parts.
Thanks for your help Charles.
I will post here if Wallander comes up with an answer.
Having listened to your example, I suspect that Dorico isn’t shortening the last note under the slur as NP expects (85%), due to the glissando, which makes the sounding note too long in NP.
You should then be able to workaround the problem by manually shortening the note in Play View in Dorico.
That’s what I tried, but it looks like it’s impossible:
(I’m not the OP)
There seems to be a quirk with note editing in Dorico with glissandos, so that note snaps to a much greater length.
This problem can be worked around by shortening the note to the smallest possible length. It will snap to an appropriate length:
Wow, very nice, @Wallander!
So, @Martin_Caron, by follwing the suggestion by @Wallander you should be able to keep the written values and to have a correct playback.
Thanks a lot for the solution
Thanks a lot for your help.
It now works as it should.
Martin
Respectfully, this issue does not occur at all with other VSTs , only NP.
I don’t know why that is, unfortunately. I suppose the problem could be linked to certain Expression Map settings.