MuseScore icon indicating copy to clipboard operation
MuseScore copied to clipboard

[MU4 Issue] Engraving of two-note tremolos is not ideal

Open Harmoniker1 opened this issue 2 years ago • 5 comments

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.

  • In 3.6, the two chords that share a two-note tremolo can have different stem directions, which is not allowed in 4.0.
  • The layout in 3.6 is also better when they have the same stem direction.

See these images for comparison: image (MuseScore 3.6) image (MuseScore 4.0 - the other one is not possible to achieve)

The second problem was fixed by me in #5619 I think (specifically 7450cbff1636e41bc5eedd943b130b907fa824ab), but the related code was probably removed and the behaviour was reverted to before the fix. @oktophonie Was this intended?

Platform information

  • OS: Windows 11

Harmoniker1 avatar Dec 21 '22 10:12 Harmoniker1

Also reported on .org Issue Tracker https://musescore.org/en/node/339387

SteveBlower avatar Dec 21 '22 10:12 SteveBlower

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 avatar Dec 21 '22 11:12 oktophonie

@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?

Harmoniker1 avatar Dec 21 '22 11:12 Harmoniker1

Not really interested in quick hacks to cover up larger problems; that's precisely what we're trying to get away from.

oktophonie avatar Dec 21 '22 11:12 oktophonie

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.

Tantacrul avatar Dec 21 '22 11:12 Tantacrul