musescore / musescore/MuseScore

"Melisma" / extender line for Roman numerals analysis

Open
#23,266 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Your idea

Add a similar mechanism for the Roman Numeral Analysis(RNA) as for the lyrics where consecutive "_" will be transformed into a continuous melisma line.

For the RNA, this should be applied to the "-" and "=" signs.

Typing this:
Roman_analysis_melisma--ASIS

Would be transformed into this:
Roman_analysis_melisma

Problem to be solved

In RNA, the following analysis, although apparently correct, doesn't make sense.
Roman_analysis_melisma__Non functional

This leads to confusion, because a IV usually belongs to the the Sub-Dominant domain while in the measure 3, the IV belongs to the Tonic domain, as a Neighbour chord between to I's.

The same applies for the I64 in measure 5. It does not belong to the Tonic domain but to the Domibant domain as a Arpegiating Dominant chord (or Cadential64).

According to different sources, the correct notation for those cases is the following one (*):

Roman_analysis_melisma

Today, this is not possible to enter this notation.

This proposition will make this notation possible and easy to write.


(*) according (a.o.) to Clendinning/Marvin's "The Musician's Guide To Theory and Analysis" book:

example006
example005

Prior art

/

Additional context

/

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

Start by tracing the existing lyrics melisma mechanism and the Roman Numeral Analysis input path. Confirm how consecutive '-' and '=' signs are handled, then verify against the issue examples that each run becomes a continuous extender line without changing the analysis semantics.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.