I just installed Dorico 4 and I noticed that some notes are missing when I opened an older Dorico project (18.104.22.1684). The notes that I noticed are missing (there might very well be more) are in a violin section player with 2 voices where only the top missing. I noticed that there used to be a nested tuplet and a grace note exactly there the notes are beginning to disappear, leaving only rests. I haven’t yet done a complete check on the file, but I guess somebody in the team might know what is causing the issue and what I should do next.
No, there are no known issues where opening a project created in an earlier version will cause notes not to appear. Please attach the original Dorico 3.5 project here, together with details of where you spot the differences between the two versions, and we’ll take a closer look.
I had a similar and strange behaviour today.
I imported a little music.xml file into an existing project. New instruments were generated. One line (actual the singers line with lyrics) came out as generic Flute, which I don’t mind.
But - even if the flute was chosen to be displayed in the score and this flow, the system would not show up in the score, even in Galley view. In the layout of this flute player all music was there. Trying to change to the score from there with „W“ had no effect.
At the end I copied the music from the flute layout, then switched to the score and pasted into my Soprano system.
Just to confirm from the Rite of Spring thread - that issue does indeed seem to be caused by the bassoon grace notes in bar 4, immediately before a nested tuplet.
Just now I tried erasing the the nested tuplets in bar 4 and re-inputting the bassoon part. I can re-enter everything except the two grace notes just before the nested tuplet (other grace notes are fine, and so is the nested tuplet itself). The program doesn’t crash, but when I try to enter the grace notes, or copy-paste them from bar 2, nothing happens. Thanks, and I hope that’s useful info!
We’ve fixed this bug in our internal builds, and we are planning (assuming nothing bad happens in the meantime) for the first maintenance release to be ready at the start of February, so you only have to live with this bug for a week or so longer.