Notehead bracket collides with elements before notehead

• Jun 3, 2013 - 14:52
Reported version
3.0
Priority
P2 - Medium
Type
Functional
Severity
S4 - Minor
Reproducibility
Always
Status
active
Regression
No
Workaround
No
Project

1. Open attached score (produced in 1.3).
2. Apply bracket to notehead.

Result: The bracket collides with the accidental.

Notehead bracket collides with elements before notehead.png

Note: Applies to other elements such as arpeggio and glissando.

Using MuseScore 2.0 Nightly Build (cbef515) - Mac 10.7.5.


Comments

What else should it do, should the accidental be inside or outside the bracket?
IMHO they should be inside (as the whole note is marked being 'optional'), but I'm not sure whether that looks right?
Esp. with arpeggio and glissanod it would look rather strange

I can't confirm, but from the images I've seen, accidentals have been inside the parentheses.

I'm not very good at it, but I tried LilyPond and the accidental was outside it.

Upon a quick search, I'm not sure if I could find anything in the book 'Behind Bars'.

How do you apply These brackts in the first place? I noticed that one could set a shortcut for this, but haven't figured out how to make this work, with or without shortcut

While I would agree it seems to make sense to place the accidental inside the bracket, that only makes sense for simple one-note chords. As soon as you get chords with multiple notes and hence the possibility for multiple accidentals, this no longer makes sense - the accidental may be buried in a stack and be nowhere near the note it applies to.

It would I guess be possible to special case one-note chords to automate this. You'd also have to check to make sure there is nothing else in any other voice at that tick position on that staff, though, since those too can affect the accidental stacking. For any situations where multiple accidentals could be involved, it might make more sense to simply push the whole accidental stack to the left to clear the brackets.

In the end, I'm not convinced any of this is worth it. I think I prefer a consistent set of of defaults. And then I as a user can choose in which cases I want to move the bracket to accommodate the accidental, and in which cases I want to move the accidental(s) to accommodate the bracket(s).

Regression No
Reproducibility Always
Reported version 2.3
Workaround No

Hi, just wanted to add that I'm using 2.3.2 and when adding brackets around one note within a bichord of two dotted notes, the bracket touches the dot and almost the other note head:

note_bracket_original.png

Here I manually edited each bracket horizontal offset for better readability:

note_bracket_modified.png

I would have reduced the brackets vertical height too (that could be of help in chords with more notes), but I didn't find a control for that - maybe that's a font-related property?

Severity S4 - Minor S3 - Major
Priority P1 - High

and even in current master the notehead brackets don't include the augmentation dot(s).
And they still collide with accidentals, unless there are legder lines.

Priority P1 - High P2 - Medium
Severity S3 - Major S4 - Minor

Unless I'm missing something, my comments from five years ago still apply - https://musescore.org/en/node/21421#comment-100921. It remains the case that it's not clear what the expected behavior is in any but the simplest case - one note chord with a single accidental and/or dot, no arpeggio, no fall/scoop, no grace note. In any other case it's going to be extremely subjective. I still think it's probably just as well to apply consistent defaults. That said, I certainly wouldn't oppose it if someone wanted to implement some special-casing.