musescore / musescore/MuseScore
Bug with Realize Chord Symbols
@DmitryArefiev is already working on this.
Since Nov 22, 2024.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Sorry. My main point here was a bum steer. Apologies for that!
But the comments about the Handbook stand. And it's curious that the entry on Generating chord voicings onto a staff doesn't show the dialog, or provide a link to an area that does.
Issue type
Originally I thought this was a UX/Interaction bug (incorrect behaviour), but perhaps it's just a questionable default.
Description with steps to reproduce
- Add a note
- add a chord symbol to the note
- right-click the chord symbol and choose "Realize Chord Symbols"
Or just download the score on .org and follow step 3 above
Result
MuseScore generates a voicing of the chord—either generically or based on properties selected in Custom—BUT the chord lasts through to the end of the score!
UPDATE: This is because I had the Duration option set to Until next Chord Symbol and since there wasn't any other chord symbol the duration was from the Chord symbol to the end of the score. Again, sorry about the bum steer!
Handbook reference
The v4 Handbook provides the necessary instructions, but does not describe the result, and given the context of this post, what's conspicuously missing the matter of timing.
I would expect when the chord symbol is attached to an eighth note MuseScore would replace that eighth note with a particular voicing of the chord. If the chord symbol is attached to a quarter note I'd expect museScore would replace that quarter note with a particular voicing of the chord ...
Am I missing something? (UPDATE: Yes I was! The result I expected is produced with Duration = Chord/Rest duration.)
Also odd in the Handbook: "Generating chord voicings onto a staff" is invoked by the "Realize chord symbols" function. Seems like one terminology would suffice.
Supporting files, videos and screenshots
Please see the video provide by cadiz1
What is the latest version of MuseScore Studio where this issue is present?
MS 4.4.3
Regression
Choose option...
Operating system
MacOS 13.5.2 and Window 11 / 4.4.3
Additional context
No response
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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.