It does this in fresh as well as old files and only for this combination of notes, and only in the upper staff. It must be some slur setting of mine, but I can’t imagine which since it only happens in the upper staff… And there are no offsets set for the slur in the Properties Panel.
Apart from wondering why you want the slurs above (default is around the noteheads, which is below the staff in this case), I get this result, in a fresh 1-bar piano project, which doesn’t look too bad:
Thanks for checking that and for looking over the attached file, @PjotrB The problem occurred where there was another voice present, so the slur had to be on the beam side. Here is the sample file. Untitled Project 1.dorico (2.7 MB)
Hi @John_Ruggero , going through your settings in the Library manager, it seems that the abnormal distance (in that particular beaming position*, the first group in the example) is caused by your increased Vertical offset from beamed stem (you have 1/4, being the default 1/2).
If I reset all other values to factory, though, that setting can stay at 1/4 without causing issues: so there is some other setting combination in your file, that is influencing this one, in an abnormal way.
EDIT: I think I found the correlated option that causes the unwanted distance: Minimum distance between slur endpoint and staff line: you have 1/2, being the default 1/4. So this is the option that you need to change:
I have no idea why the lower staff is not affected, though. Maybe someone of the Team will add some information…
I noticed, thought, that just adding another staff above, flute for example, (and resetting the G clef, in Music Symbols, and deactivating hide staves in Layout Options), reestablish the correct position of the slur. So this has something to do with the thresholds of the upper staff spacings…:
Your experiment bears out what I thought @Christian_R The setting seems to affect only the topmost staff in a system. (You might test that in your example.) But this can’t be the intention of the setting.
And why the setting should produce such an exaggerated result is also puzzling to me.