musescore / musescore/MuseScore

Grainy Sound When using 192k Plus Newest MuseSampler

Open
#25,550 0 comments 0 reactions 1 assignee View on GitHub

@RomanPudashkin is already working on this.

Since Nov 18, 2024.

P3 playback
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
  1. Set audio settings to 24bit 192k
  2. Open MuseScore, create a new score with MuseSounds flute
  3. Note preview will sound "grainy"
Supporting files, videos and screenshots

https://github.com/user-attachments/assets/de957a37-dbf6-4555-baf8-e0519512e520

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

MuseScore Studio version (64-bit): 4.5.0-243230312, revision: github-musescore-musescore-9ef26b8

Regression

I was unable to check

Operating system

Windows 11

Additional context

Only reproducible with MuseSampler build >= 0.100.6.383

The reason for the grainy sound is because on first try MuseSampler is reported a max buffer size that is actually too low.
Example:

  • Buffer Size in MuseScore pref's: 2048
  • MuseSampler gets a buffer size of 1024
  • Actual Processing calls are at 2048
  • MuseSampler's resampler does not have enough buffer prepared

The way to fix this is to enter MuseScore's preferences again and re-select the correct buffer size

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.