musescore / musescore/MuseScore
Tie fails when entering grace notes in this order
Nobody has claimed this yet.
- 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
I have found a bug. I have discussed this in the Facebook group where I was recommended to report this.
I have attached a screenshot showing two examples. The one to the left is the error, the one to the right is how it should look.
I want a grace note before a main note. Those have the same pitch. I want do write like that to show that the trill should start on that pitch and not on the note above. If I want to start the trill on the note above, I write the grace note one step up, and use a slur instead. But this example is about a tie.
Everything looks correct if I enter the notes in normal order, which is:
I add the main note.
I add the grace note before.
I add the tie from that grace note to the main note.
I add the two grace notes after.
But the tie looks wrong if I add the grace notes in reversed order, like this:
I add the main note.
I add the two grace notes after.
I add the grace note before.
I add the tie from the grace note before to the main note. Now the tie looks wrong.
Supporting files, videos and screenshots
In which versions of MuseScore Studio is this issue present?
4.6.5.253511702
Regression
I was unable to check
Operating system
MacOS
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.