musescore / musescore/MuseScore

Beam grouping options too small on "Create time signature" dialog

Open
#28,079 3 comments 0 reactions 1 assignee View on GitHub

@cbjeukendrup is already working on this.

Since May 20, 2025.

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

Description

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce
  1. Open a new project
  2. Open the "time signatures" dropdown menu in the "palettes" tab on the left.
  3. Click "more" and then "create time signature".
  4. Observe "beam groups" section in the following menu.
    Expected behaviour: Note display in sections labelled "1/8", "1/16", "1/32" appear at the same size as shown in documentation (note the "Beams" section of the handbook)
    Actual behaviour: The note display appears far smaller, meaning it is difficult to use.
Supporting files, videos and screenshots

https://github.com/user-attachments/assets/a7732d35-a92e-4340-aa3c-048dc34b5b73

Image

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

OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.5.2-251141402, revision: github-musescore-musescore-ac9d3bc

Regression

I was unable to check

Operating system

Windows 10

Additional context

Bug is found on 4.5.2 as well as the latest nightly build. A forum user appears to have had the same issue in August 2023 on 4.1.1 on a Linux system.

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.