Weird behavior of Glissandos in Dorico 6.1 using NotePerformer

Dorico
1

I’ve noticed a strange behavior after updating to Dorico 6.1. I am working on a project with multiple glissandi for string instruments. In version 6.0 they played back correctly, but after updating, some work as intended, others don’t play at all, and many are playing backwards or producing unexpected results.

So far, I have tried adding new glissandi and adjusting the “delayed start” property (most of them have this property enabled), but nothing changes—the playback remains incorrect.

I’m using NotePerformer 5 with Dorico 6.1 on Mac.

Any help or advice will be greatly appreciated.

2

If you could attach a small example that demonstrates the problem we can take a look.

3

Actually I see there’s another report here, from which I’ve been able to reproduce the issue: Delayed Start Continuous Glissando: weird behaviour - #5 by Richard_Lanyon

4

Thank you, I tried to find before posting but I couldn’t find any info related to this issue. I’ll take a look at that post and I will post a small dorico file here in the next few minutes!

5

SAMPLE File Gliss.dorico (1.9 MB) Here’s a little excerpt of my project with different gliss. I hope this helps.

6

Same here, NotePerformer 4.5.1, Dorico 6.1 on Mac Sequoia, glissandi are a bit off.

7

Same problem here, acutal NP-Version, Dorico Pro 6.1. No glissandi audible.

8

Here’s your file. All the solo cello gliss work for me — I’ve had to delete the ones that did not work and input them again (shift-O, gliss). I’ve also added some delay for this gliss, to make them sound to my taste, but of course you can modify that in the properties !!!

SAMPLE File Gliss.dorico (1,8 Mo)

1 Like
9

I’ve also encountered this issue and sent Steinberg my project file.

Fingers crossed!

10

Hi Marc, thank you. So, the current solution is to manually delete all the gliss in previous projects and rewrite them? For what I’ve seen so far, the issue is more related to files created in older versions of Dorico and then opened in 6.1.

11

Well, I have not definitive answer to this. But I simply discovered that deleting the gliss and reinputting it did solve the problem.

1 Like
12

6.1.10 Has a fix for this issue. No need to re-input your previous gliss. with Delay Start.

13

6.1.10 Has a fixed this issue. No need to re-input your previous gliss with Delay Start.

1 Like