musescore / musescore/MuseScore
Buzzing sound on Clarinet when playing C4 under some circumstances
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
Muse Sounds bug
Bug description
When playing Eb4 and then C4, there can be a noticeable buzzing sound on the C4 note when played at low volume (such as mp or p) when using Musesounds. The buzzing does not appear to be present when coming from higher notes (such as Bb4). I noticed this in a score I was working on, but was able to recreate in a new score (attached). The attached MP3 is an export that shows the buzzing on C4 when preceded by Eb4, but not when preceded by Bb4.
Steps to reproduce
- Open new score, set instrument to Bb Clarinet. Confirm that instrument is using Musesounds
- Change key signature to Concert Eb (not sure if this is required, but this was done for my test)
- Enter half notes as Eb4, D4, Eb4, C4. Set dynamic on first note to mp.
- Play and notice buzzing on C4.
- In a new measure, add Bb4 and C4 as half notes.
- Play and notice no buzzing on C4
Attached score and MP3 give an example of this issue.
Screenshots/Screen recordings
MuseScore Version
OS: Windows 10 Version 2009, Arch.: x86_64, MuseScore version (64-bit): 4.0.2-230651553, revision: github-musescore-musescore-dbe7c6d
Regression
I don't know
Operating system
Win 11
Additional context
No response
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.
Research direction
Open the attached “Buzzing on Clarinet C4.zip” and reproduce the sequence in MuseScore with Muse Sounds enabled: Eb4, D4, Eb4, C4 at low volume, then compare it with Bb4 followed by C4. Use the included MP3 as the reference; done means the buzzing is no longer present in the first sequence while the second remains unaffected.
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