musescore / musescore/MuseScore

"Liturgical Unmetrical" template (preview) is misleading

Open
#24,828 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

needs review
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
  1. Go to Choose Instruments -> Create from Template 2. Click on Liturgical Unmetrical. 3. Expected Behavior: The created score is one as shown in the preview, with no barlines, and supporting the notation of free rhythm phrases. 4. Actual behavior: The created score is an ordinary stave with barlines, which does not support free rhythm phrases.
Supporting files, videos and screenshots

https://github.com/user-attachments/assets/41f24c53-e033-4649-b9a4-2bb1c3bc17eb

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

Version: 4.4.2.242570931 Revision: 3130f97

Regression

I was unable to check

Operating system

Windows 11

Additional context

Liturgical notation should be a standard feature of Musescore, especially Liturgical Unmetrical+Organ. It is indispensable for church music. For a clear example, see Peter M. Kolar's "Kyrie":
image
This example also shows the first system unmetrical, the second system in 4/4, and the third system unmetrical again. So ideally, Musescore should have the option to convert a system into unmetrical notation.

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.

Research direction

No source files, tests, or entry points are named. Reproduce the issue through Choose Instruments -> Create from Template -> Liturgical Unmetrical, then trace how that template is defined and instantiated; done means the created score matches the preview by omitting barlines and supporting free-rhythm phrases.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.