Skip to content

Fix multiple clarinets sharing the same name in score.#32510

Draft
CubikingChill wants to merge 2 commits intomusescore:masterfrom
CubikingChill:my-new-branch
Draft

Fix multiple clarinets sharing the same name in score.#32510
CubikingChill wants to merge 2 commits intomusescore:masterfrom
CubikingChill:my-new-branch

Conversation

@CubikingChill
Copy link
Contributor

@CubikingChill CubikingChill commented Mar 5, 2026

Resolves: #32511 #23018

  • I signed the CLA
  • The title of the PR describes the problem it addresses
  • Each commit's message describes its purpose and effects, and references the issue it resolves
  • If changes are extensive, there is a sequence of easily reviewable commits
  • The code in the PR follows the coding rules
  • There are no unnecessary changes
  • The code compiles and runs on my machine, preferably after each commit individually
  • I created a unit test or vtest to verify the changes I made (if applicable)

@CubikingChill CubikingChill reopened this Mar 5, 2026
@CubikingChill CubikingChill marked this pull request as draft March 5, 2026 20:10
@CubikingChill
Copy link
Contributor Author

It appears that the value "TrackName" is used extensively, from mixer track name to "select instrument" page and "change instrument" in the score. Although the instrument name in these places should ideally be the same, it appears that they are not. Variant by key is specified in "select instrument" page but not the other 2. Seems we have to fix it by either specifying variant by key in all 3 fields, or simply use longName instead.

Eitherway, this has been vary confusing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Clarinet variants all display the same default name “Clarinet” in the Score and Mixer

1 participant