musescore / musescore/MuseScore

[MU4 Issue] Solo cello sound has very slow attack

Open
#13,168 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

playback regression MS4
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Describe the bug
When comparing the solo cello sound to the other solo violin family sounds, the attack is noticeably slower and reduces its effective relative volume
To Reproduce
Steps to reproduce the behavior:

  1. Create a new string quartet score, tempo ~80 bpm
  2. Add some 1/4 notes low in the range in the violin part (e.g. a G major scale starting on the bottom string)
  3. In a later measure, add some 1/4 notes low in the range in the cello part (e.g. C major scale starting on the bottom string)
  4. Play back score
  5. Observe that violin sound envelope has reasonably quick attack and a smooth legato sound, but each cello note seems to "fade in" gradually due to a slow attack. In faster passages this makes the cello noticeably quieter than other parts as it never has time to reach the peak level in the envelope.

Expected behavior
Attack for solo cello should match violin & viola, as it does in MuseScore 3.

Screenshots
If applicable, add screenshots to help explain your problem.

Platform information
Windows 11

Additional context
Add any other context about the problem here.

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.

Research direction

Start by reproducing the playback comparison in MuseScore on Windows 11 using a string quartet at about 80 bpm, as described in the reproduction steps. Compare the solo cello attack with the violin and viola, and consider the issue done when low-register cello quarter notes reach their intended attack and relative volume without fading in during faster passages.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.