MuseScore 4.1 beta is now ready for testing
I am pleased to announce that the beta version of MuseScore 4.1 is now available for testing.
This version includes all the new features we have planned to release in version 4.1.
How to get the beta (Updated with new builds: 28 June 2023)
N.B. These builds are also available from this page (click on “Beta” for your required operating system): https://ftp.osuosl.org/pub/musescore-nightlies/
Important – do this first before testing!
In order to test the major changes we’ve made to the playback engine, you’ll need to have Muse Hub BETA installed:
- Uninstall MuseHub from the settings menu within MuseHub
- Download MuseHub beta from here: https://www.musehub.com/ (scroll to the bottom of the page)
- Install and open MuseHub beta
You’ll now be ready to open and test MuseScore 4.1 beta.
New features to test
- Adding ornaments (trills, turns, mordents) and applying chromatic alterations via the Properties panel
- Applying capos via the new “capo” palette element (look in the "guitar" palette)
- Applying harp pedal diagrams from the new “harp notation” palette
- New auxiliary channel strips and sends in the mixer (note you’ll need to expose the new aux channels via the “three dots” menu icon to the right of the mixer).
- As a result of various changes we’ve made throughout the app that affect playback, please thoroughly test anything playback related, including loading VSTs (there’s a new VST scanning system that should prevent hangs and crashes much more effectively).
- Opening your cloud scores from the new “my online scores” tab (Home > Scores) and saving/publishing scores to the cloud.
- Uploading audio to audio.com: this can be done directly from the Publish tab or the File menu, and allows you to share your score audio for others to stream or download, as well as build an audio portfolio of your work online.
- Adding expression text to notes with dynamics
A note on engraving changes
MuseScore 4.1 includes a large number of engraving fixes and improvements. Read this article to learn more about them (for those who want to look out for these in your testing!).
Some known issues
All of our current bugs prioritised for fixing are listed here on GitHub. Please be aware we are now only prioritising for 4.1 fixes for issues that are:
- Regressions from 4.0.2
- Stability problems (crashes)
- Issues with new features in 4.1
A note about backward score compatibility
It is currently still possible to open a score created in 4.1 in a previous version of 4.0. Doing so may cause your scores to become janky, however, so we’d encourage you not to try this (at least on scores that are particularly precious to you).
As usual, be sure to double check whether an issue has already been raised before logging anything in GitHub. If we can’t fix something for 4.1, we’ll make sure it gets assigned to 4.2 or an appropriate project.
Thanks, and happy testing!