musescore/MuseScore

Customise time signature appearance (using cut/common time symbol) directly in "Add custom time signature" dialog

Open

#25704 opened on Dec 3, 2024

View on GitHub
 (7 comments) (0 reactions) (1 assignee)C++ (11,122 stars) (2,432 forks)batch import
UIcommunitygood first issue

Description

Issue type

UI bug (incorrect info or interface appearance)

Description with steps to reproduce

Many renaissance works alternate between some kind of 2/1 and 3/1 meter, usually written with cut time 𝄵 or common time 𝄴 symbols and a single digit 3 or 3/2 time signature. Therefore it would be nice to be able to make a user-defined 2/1 or 4/2 time signature that shows as cut/common time. However this is currently not possible.

Steps to reproduce:

  1. Go to time signature palette and see that the existing pre-defined time signatures don’t include what you want. → No problem.
  2. Add custom time signature 4/2 to palette. → See that you could change the displayed time signature to another fraction or a single digit but not to cut/common time symbol. Bildschirmfoto vom 2024-12-03 08-04-58
  3. Apply the custom time signature to score.
  4. Change the displayed time signature via context menu. → See that you can change the displayed time signature to cut/common time or another special symbol but is changed only on one staff. Bildschirmfoto vom 2024-12-03 08-05-11

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/2a4440ac-5abf-43e4-adb0-c3a6da8982cd

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

4.4.3

Regression

I was unable to check

Operating system

Linux but it should be OS-independent

Additional context

IIUC step 4 shows an example of bug #16406. Step 2 might be related to #12980 but I think the renaissance scenario is a special case that could be easily treated by adding the possibility of display cut/common time to the “create time signature” dialog.

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