-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[MU4 Issue] Engraving of two-note tremolos is not ideal #15470
Comments
Also reported on .org Issue Tracker https://musescore.org/en/node/339387 |
In an ideal world, tremolos would have been implemented as a flavour of beam, and so all the new beam placement code would apply to them to. Sadly this didn't turn out to be the case (they were a thing all unto themselves), and changing this required a refactoring effort that we didn't have time for for 4.0, so their current placement is, sadly, pretty gruesome. ('Not ideal' is an understatement.) Rest assured that this is one of my highest prioirities for 4.1, though. (Yes, there will be options for symmetrical placement on unstemmed notes, and for going between them rather than above/below, etc) |
@oktophonie That's glad to hear! I would totally support treating two-note tremolos like beams. But meanwhile, does the current "gruesomeness" deserve a quick patch fix for minor releases? |
Not really interested in quick hacks to cover up larger problems; that's precisely what we're trying to get away from. |
Exactly. When we do it right, we can then build upon that work. A hack has to be eventually removed, which then messes up people's scores. |
Describe the bug
It is reported in this issue thread that the layout of two-note tremolos is not as good as in 3.6.
See these images for comparison:
(MuseScore 3.6)
(MuseScore 4.0 - the other one is not possible to achieve)
The second problem was fixed by me in #5619 I think (specifically 7450cbf), but the related code was probably removed and the behaviour was reverted to before the fix. @oktophonie Was this intended?
Platform information
The text was updated successfully, but these errors were encountered: