musescore / musescore/MuseScore
D.C. (or D.S.) al Fine marking right before a section break causes the pause between sections to happen at the wrong time (4.42)
@zacjansheski is already working on this.
Since Sep 20, 2024.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
General playback bug
Description with steps to reproduce
- Create a new score with any instrumentation.
- Add a section break at any given measure. Make sure it is set to pause for some duration between sections.
- On the same measure as the section break, add a D.S. al Fine or D.C. al Fine.
- If using D.S. al Fine, add a segno in an earlier measure.
Expected behavior: On reaching the D.S. or D.C. marking, it should immediately jump to the capo or segno and begin playing back from there. Then, on reaching the Fine, it should pause as set in the section break properties before starting the next section.
Actual behavior: On reaching the D.S. or D.C. marking, the cursor jumps to the appropriate place, but then unexpectedly pauses as though it's about to start the next section. After the pause, it plays from the capo or segno as originally intended. Finally, when it reaches the Fine, it immediately begins playing the next section without a pause.
Supporting files, videos and screenshots
What is the latest version of MuseScore Studio where this issue is present?
OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.2-242570931, revision: github-musescore-musescore-3130f97
Regression
I was unable to check
Operating system
Windows 10 Pro, 64-bit
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.