musescore / musescore/MuseScore

Arco marking ineffective on acoustic bass instrument

Open
#30,207 0 comments 0 reactions 1 assignee View on GitHub

@RomanPudashkin is already working on this.

Since Oct 1, 2025.

P2 playback regression MS3
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 is not a recent regression (goes back to 4.3 at least), but I only just noticed it while testing some other things around reported arco/pizz issues.

  1. Create score for "acoustic bass"
  2. Add notes
  3. Add "arco" from the Text palette at some point
  4. Play

Result: the "arco" is ignored

Interestingly, it works if you add Contrabass as the instrument (and set "pizz" at the beginning). In both cases, it is using MS Basic, but apparently different sounds are being used by "Choose automatically" (I think the "contrabass" sound was added to MS Basic just a few years back). But aside from the different presets, the main difference between acoustic bass and contrabass was whether it defaulted to pizz or arco. Now, it seems that acoustic bass doesn't just default to pizz - it forces it.

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/b6eb50e6-3b5f-47d1-b377-6c35a3b0750e

What is the latest version of MuseScore Studio where this issue is present?

OS: Debian GNU/Linux 12 (bookworm), Arch.: x86_64, MuseScore Studio version (64-bit): 4.6.0-252730944, revision: github-musescore-musescore-7829779

Regression

Yes, this used to work in MuseScore 3.x and now is broken

Operating system

Debian 12

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

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.