musescore / musescore/MuseScore

Clarinet, Bass Clarinet; using a fall causes "ghosting" past note duration

Open
#17,415 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

MuseSounds
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

On the Clarinet and Bass Clarinet (potentially more; I didn't check), adding the "fall" marking to a note causes it to produce the falling sound even after that note has ended, well into the next few beats.

Steps to reproduce
  1. Create a staff with using the Bb Clarinet
  2. At the default tempo, enter a relatively short note duration (such as an eighth note) and add a "fall" to that note using the "Arpeggios & glissandi" panel.
  3. Enter a note of any duration directly after the first note (if at a higher pitch, the issue can be more easily observed).
  4. Press the play button

image

Screenshots/Screen recordings

https://user-images.githubusercontent.com/114624716/235334743-a7d0d1df-1cfd-46a6-9c84-7cccc2059172.mp4

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

Windows 10

Additional context

No response

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 issue in MuseScore 4.0.2 on Windows with Bb Clarinet or Bass Clarinet, using a short note with a fall followed by another note. Trace the Muse Sounds playback path for fall markings; done means the falling sound stops when the marked note ends and does not continue into later beats.

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.