musescore / musescore/MuseScore

Impossible to flip cross-staff tremolos

Open
#29,361 0 comments 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

engraving P2
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

Engraving bug (incorrect score rendering)

Description with steps to reproduce

The following image should be pretty self-explanatory:

Image

Any beaming in cross-staff notation has three ways to be rendered in MS: beaming between the staves, beaming over the upper staff, beaming below the lower staff (all reachable by simply pressing X).

As you can you see, tremolo only allows the beaming between staves; pressing X results in the stems vanishing and tremolo dashes shortening.

This happens with all durations. With whole notes, of course flipping only results in the tremolo dashes to shorten:

Image
Supporting files, videos and screenshots

For reference, this is what you can easily find in published scores:

Image

[This is an old edition which is far from perfect, and in this specific case the cross-staff is definitely not necessary... but that's not the point, clearly.]

What is the latest version of MuseScore Studio where this issue is present?

4.5.2 and 4.6 alpha

Regression

I was unable to check

Operating system

Windows 11

Additional context

Could it be related to https://github.com/musescore/MuseScore/issues/26112?

Checklist
  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.