First notes in bars are too close to start repeat, key signature
Reported version
3.0
Priority
P0 - Critical
Type
Development
Frequency
Many
Severity
S4 - Minor
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
No
Project
OS: macOS High Sierra (10.13),
Arch.: x86_64, MuseScore version (64-bit): 3.0.0.19874,
revision: 59a11cd
I’m not sure if someone mentioned it already..
Very first notes in every system are fine,
But except from these, first notes in every bars on TAB are too close to Start Repeat.
Attachment | Size |
---|---|
ex_TAB.jpg | 134.35 KB |
Comments
Not just tab, it's equally wrong for standard staff, if the first note is above or below the staff, as shown.
As I recall, there was a similar issue for notes too close to time signatures that was fixed by extending the "shape" for the time signature beyond the staff. Maybe the same approach works here.
Same for key signatures - normal handling does fine with the header at the beginning of the system, but for mid-system key changes, the first note can overlap. This is not good at all:
Hopefully the same quick fix can apply.
The keysig issue was as easy to fix - see https://github.com/musescore/MuseScore/pull/4421. Barlines, not so much. Apparently, we don't actually use the barline shape during layout (?) so extending it above and below the staff didn't help. Another approach will be needed I guess.
In reply to The keysig issue was as easy… by Marc Sabatella
Hi Marc
Great you so quickly fixed the keying issue, I didn't notice that though !
Seems barlines are not that easy..
See https://github.com/musescore/MuseScore/pull/4445.
Extending barlines shapes could also help, I think, as shapes collisions are calculated for them. Not sure about other possible side effects though.
Fixed in branch master, commit 72af67444a
fix #280140: fix distance between notes and start repeat barlines
Fixed in branch master, commit 1256be53c2
Merge pull request #4445 from dmitrio95/start-repeat-collide
fix #280140: fix distance between notes and start repeat barlines
Automatically closed -- issue fixed for 2 weeks with no activity.