I’ve been sent a project with a rather unusual issue: there’s a chord diagram that appears and that is not on the score… I’ve cut down the document to the only bar that causes the problem, and as you can see, there’s a F#7(add4) chord (that is what the user wants) and a C#m11 diagram at the start of the flow (there is no such chord in the whole document).
I’ve noticed that if I ask Dorico to generate chords automatically, it will generate that chord instead of the F#7(add4), what I think is wrong is that this C#m11 is added to the diagram chords while not present at all in the document.
I do not claim to be intimately familiar with how Dorico chooses the chords to put in the “flow header,” but the chord you show could be interpreted as either an F#7(add4) (or I would say an F#7sus) or (given the lowest note of the chord) a version of C#m11.
The reason your one-measure file is 3MB probably results from the sound profile associated with the original file, which persists even when you cut the file down to one measure. Try applying the Silent option in Playback Template and see if the file size immediately goes down to what you likely expect.
It’s what I’ve shown in my post, when I say that using Generate chord from notes gives C#m11. The problem is that the user did not want that chord, and it was specifically written as F#7(add4), and in a file with over 100 bars, it was quite long to find the one chord that would trigger that diagram (and there are other exact same F#7(add4) chords. I mean exactly the same bar).
I could find the culprit, I can find a solution, but I’m using Dorico everyday for almost ten years now. It’s not the case with the Dorician who had the problem and was struggling with it. There is no way to select and delete a diagram that’s in the block at the start of flow. It’s automatically there and it’s not easy to track down the culprit. Just sending this file for the Team to correct something (if it’s correctable).
Good idea. I realize that, when one is engraving someone else’s music, one wants to do what they ask. And I am well aware of your experience with Dorico; I read all your posts with great care.
Strange how Dorico interprets some chords. I would expect an “add 4” chord to include the third, but I realize that chord symbols and interpretations can be widely different in different traditions..
There are somehow two chord symbols here at the same position. If you delete the F#7add4, then save, close and reopen the project, you’ll see the C#m11 there. Exactly how this has happened I don’t know - we’d be interested if you can work it out!
I’d like to know that too… I’ll ask directly our Dorician friend.
[edit] Here’s what he told me. He had two guitars. He started by adding chords with the maj-Q popover. Then he used the generate chords from the context menu (maybe on the second guitar?), and he confessed he used alt-return once. Was it on this chord? No idea… I’m sorry, I don’t have better details.
I think I can reproduce this behaviour in a score:
In writemode select a Chord diagram and change the Chord symbol line to a higher value then 1.
Then make a new Chord diagram on the same chord.
Set the Chord symbol line from the first Chord back to 1. There is an overlap now.
But going to the other layout the overlap is gone and only 1 Chord diagram is there to stay, but in the Chord area both are there.
An other somewhat strange behaviour: select the now visible chord diagram and hit R.
In the Chord area the invisible chord disappears. But hitting Ctrl+Z (undo) and the other Chord diagram pops up in its place and both are back in the Chord area.
