musescore / musescore/MuseScore

Add ability to switch sample rate in MSS. Bit Size does not follow audio Driver.

Open
#33,237 5 comments 1 reaction 2 assignees View on GitHub

@IIINekoIII is already working on this.

Since May 6, 2026.

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

Description

Issue type

Other type of issue

Description with steps to reproduce

By opening Musescore 4.7 Beta 2 and selecting ASIO, there is no sample rate selection. Most Audio software is made to slave to whatever the current windows (or system) driver settings are set too. Musescore seems to try to take control and change the driver to match Musescore's rather then slave to system settings. I would recommend something akin to what the Daw (Digital Audio Workstation) Reaper does. By default, it should slave to the installed driver or systems current settings.

Also, give us a tick box to request a specific sample rate and another box to input that number. Also wouldn't hurt to be able to request buffer size in such a way besides a drop down menu. That way all edge cases can be met by flexibility. And of course Audio interfaces are meant to run at specific sample rates and buffer sizes. Most of the time. Another reason to add the check box and place to type the sample rate or buffer is because not all audio interface drivers (at least on windows and typically cheaper interfaces) let you select the sample rate and bit depth directly in the driver. Typically do to bad designed drivers. They can typically switch but requires the program (aka Musescore in this case) to call for one.

All of this is said and good, but the default of relying on the systems drivers which is standard in so many other programs with the option to call for something else as backup tends to be standard and I propose that Musescore follows the aforementioned above.

Note, while 44.1k is CD quality and not in itself a bad sample rate, it is outdated and many professional projects will run at 48k, 96k, 88.2k, 96k, 176.4k, and 192k. These serve various purposes but ideally should all be accessible at a minimum. In a daw, the general philosophy for recording is too record at the highest sample rate, lowest bit depth (buffer size) for the most amount of information recorded at the fastest latency (PC Specs and interface/driver determine what can actually be ran).

Supporting files, videos and screenshots
Image
In which versions of MuseScore Studio is this issue present?

Tested in Musescore 4.7 Beta 2

Regression

No.

Operating system

Windows 10 latest release as of 5/3/2026 (US Date System)

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.