musescore / musescore/MuseScore

Playback issue with tie + acciaccatura

Open
#27,920 2 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

P2 playback regression MS4
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

This happens with a note spanning two measures (with a tie) and an acciaccatura on the second note of the tie.
The long note starts playing too early, in the middle of the previous measure.
The preceding measure doesn't have to be empty like in the video, it's just easier to hear this way.
It has to be an acciaccatura, an appoggiatura doesn't seem to trigger the bug.
Shorter durations only present the problem sometimes, and moving the tied notes so they span multiple measures can make a difference sometimes.
The acciaccatura can be put on a different note that's played at the same time as a tied note (though not the first one of the tie), even on a different voice, same bug.

Supporting files, videos and screenshots

https://youtu.be/bGOkx2uns7c
I'm unable to upload the score in the github issue, but I don't think it's necessary in this case...

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.5.2-251141402, revision: github-musescore-musescore-ac9d3bc

Regression

I was unable to check

Operating system

Windows 10

Additional context

This happened to me in a context where the acciaccatura made sense, unlike here...

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

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.