Segno & Coda, etc. Auto Placement

• Jul 21, 2018 - 16:25
Reported version
3.0
Type
Functional
Severity
S5 - Suggestion
Status
closed
Project

Auto Placement
auto_placement.png
Preferred
preferred.png
(X: 4.00sp; Y: 0.00sp)
preferred2.png
(X: 6.00sp; Y: 0.00sp)
Sorry for images being too big.
Test in:
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (32-bit): 3.0.0, revision: 206532b


Comments

Status (old) active by design
Status active by design

update: this is not an issue, the segno marker etc. all are automatically placed above the bar line, so this is the expected behaviour. Closing this issue.

Status (old) by design active
Status by design active

Rehearsal marks too are placed above barlines, but not at the beginning of a system
(corrected stupid autocorrect errors)

I'm struggling to work out how far right you want it. There are multiple options:

  • To the right of all clefs, key sigs and time sigs (which is what my fix does)
  • To the right of only the clef
  • To the right of the clef and key signature
  • An arbitrary number to the right

What do you think would be the best option?

@Jojo-Schmitz here is the behaviour of the new autoplacement. It looks a lot more natural with notes, I think. If it still looks odd, let me know, I'm very happy to change it to fit how you think it should be :)

newscrshot.png

Oops. Still right of clef looks good to me, like the predwrrwd example in the initial post. Guess we need some authoritative sources, what does Gould say in Behind Bars?

On page 240 of Behind Bars, Elaine Gould writes:
gould excerpt.png

----------------- End of excerpt -------------------------

She doesn't seem to mention a special case for when the symbol is at the beginning of a system.

Edit: In fact, further down the page, she says this:
It is helpful if sections to be returned to or skipped to can begin on a new system. This visually demarcates them.

So it would seem she considers a segno at the beginning of a system to be the preferred case. And again, not deserving of any special treatment.

This is hardly the only case where Autoplace bunches objects too close together. I would say leave it for now until a plan is in place to correct this problem at a global level. But that is just my opinion.