MuseScore 4 is OUT NOW!

• Dec 14, 2022 - 00:17

UPDATE - March 13, 2023: MuseScore 4.0.2 has now been released.

This patch release release fixes loads of issues, and also includes some important usability improvements as well as a ton of engraving enhancements.

All the details about this version can be found here on Github.

UPDATE - January 13, 2023: MuseScore 4.0.1 has now been released (see changelog).

This announcement is available in other languages. See links to translated versions below.

Hey everyone,

Today, we are delighted to announce the release of MuseScore 4 along with our new orchestral playback library Muse Sounds!.

To install:

  1. Visit
  2. Click the main Download button for your operating system
  3. This will download the Muse Hub installer, which allows you to install MuseScore 4 and Muse Sounds

Linux users need to click the "Download AppImage" button to install MuseScore, and also the text link "Muse Hub (for Muse Sounds)" directly below in order to get Muse Sounds.

For those wanting to download a Windows or Mac version of MS4 without the Muse Hub, please use the appropriate text links at

Watch our release video

YouTube video: Announcing MuseScore 4 - a gigantic overhaul!

What's new in MuseScore 4?

  • Our new orchestral plugin, Muse Sounds
  • Saving to cloud on is now working
  • An improved system for publishing to
  • A simple toggle for switching between playback profiles (MS Basic and MuseSounds)

An entirely new interface
- 400 new icons
- customisable colours
- A new Home tab which includes recent scores, plugins and video tutorials
- A new, friendlier onboarding process

An engraving overhaul
- New system for horizontal spacing
- New system for slurs and ties
- New system for beaming and cross-staff beaming
- New, heavily revised version of Leland and Leland text
- System objects can appear on more than one system (although this is currently only available on certain templates)
- Hundreds of other smaller fixes and optimisations for lyrics, articulation placement, tremolo marks and general positioning
- For a more comprehensive explanation of the engraving changes in MS4, please see this document.

Multiple workflow improvements
- The Properties panel (formerly the inspector) is now much more responsive, easier to understand and filled with lots of useful options
- The capabilities of the note input bar have been expanded and the toolbar itself is now much easier to customise
- Customisable 'Tempo Lines', (accel, rit, etc.) that work with playback
- Scrollbars on the score
- Parts are easier to discover, edit and alter (using the new 'Instruments' panel)
- The experience of setting up a new score has been simplified to be more welcoming to new users
- Improved instrument definitions
- A new tuplets toggle
- New articulation buttons
- A new toggle for cross staff beaming

A new mixer


VST instruments and effects support
- Please note that we will be building additional tools, like automation and MIDI mapping in later releases, once MS4 is out

Accessibility improvements
- A new keyboard navigation system that follows best practices to allow users to quickly move around the interface
- Improved screen reader support (in particular, we really need people to test and provide feedback on this)
- An editable high contrast mode

Incompatible features we will re-introduce in later releases

  • There are other features that have not played nicely with our new systems at all, and which will need to be replaced in later releases, namely: the plugin creator (which we want to rewrite completely as a priority), the score comparison tool and the 'Documents side-by-side' feature.

Read this announcement in other languages

These translations have kindly been provided by members of our community:

Or you can use Google Translate to view it in other languages.


In reply to by discarlosrobl1

VST for Linux is listed on GitHub as being a priority for 4.1, and "contributions from the community are very welcome". The effects on Windows and macOS are already based on VST, so presumably that would come for free. But also a new aux send system and native reverb is being worked on, and what's there so far is already working on Linux. LV2 is also listed as being on the roadmap for 4.1. I guess it will come down to how much the community steps in to actually implement this...

In reply to by Marc Sabatella

I can understand the need for community support for LV2, as it isn't a cross platform function of the software. But I think it's unfortunate that the implementation of a foundational cross platform function for VST is essentially being put on the shoulders of the community. Shouldn't the core development team prioritize VST on Linux themselves? As has been conveyed before, it appears that Linux is second class with the team appearing to suggest that the Linux community (many of whom are users and not developers) are on the hook for basic functionality of an incomplete software.

I'm just not comfortable with the implication that the Linux distribution doesn't fully work and it's the community's fault.

In reply to by cfirwin3

I can't speak for anyone on the core team or speak to the question of what policy might be going forward. But I've been part of the MuseScore development community for over ten years now, and I have to say, I'm kind of perplexed by the attitude that the development of MuseScore has ever been anything but the responsibility of the entire community. I mean, sure, there has always been a core team developing important functionality, and we're eternally grateful for them, but huge chunks of the code have pretty much always come from the community. The core team does what they can, everyone else pitches in to tackle what they can - this is how it's been since the very first release.

In reply to by Marc Sabatella

I suppose the question is, what puts VST for Linux outside of "important functionality" while VST in Mac/Win is apparently critical? The only differentiating element is Linux itself. As I said in the previous post, I can completely understand why LV2 is pitched to the community. I don't think that it's fair to paint my comments as an 'attitude' that is somehow out of touch with the history of development. The effects rack is a placeholder in Linux with no concrete promise for implementation. Doesn't that bother you? It's a completely fair criticism, and it is independently shared by users.

In reply to by cfirwin3

Again, I can't answer in any official capacity - only as a community developer who has been involved with the project since the first release and has been in the computer industry for close to half a century at this point.

My answer is, same as how any other such decisions are made and always have been made in MuseScore or anywhere else - a pretty straightforward matter of cost/benefit. Features used by 95% of users have always gotten more attention than features used by only 5%. That doesn't mean lesser-used features aren't important at all, but sometimes when decisions need to be made because it turns out supporting the feature turns out to be more unexpectedly difficult (as was the case for VST on Linux), that's a deciding factor in how the features are prioritized.

Decisions like this are not about singling out Linux specifically; they are about trying to quantify the number of users who might rely on a particular feature. The number of Linux users is much less than Windows, but not negligible either, so it's not like support for Linux in general would ever just be dropped. On the other hand, the percentage of users who rely on VST is also not huge on any OS, and is very likely smaller for Linux than for Windows, simply because VST support on Linux is much less than on Windows across the board (most major vendors don't provide Linux versions of their VST libraries). So you end up with a smaller percentage of a smaller percentage of users, and a higher-than-expected development effort needed to support it.

Again, it's not about singling out Linux - other features that were temporarily sidetracked affect Windows users disproportionately, others disproportionately affect Mac users. But the majority of things that were temporarily de-prioritized affect all OS's equally . Again, it's not about singling out an OS, it's just a simple matter of cost/benefit, same as virtually every similar decision made throughout the history of MsueSocre, or indeed about virtually any software, or pretty much any product period.

I'd like to address the issue of the playback - long notes, that are connected with a tie (I hope I use the correct term. it's the one connecting two notes of the same hight together to make them longer) are played twice for some reason. It should enlong the note, but it just plays the two notes as if they weren't connected. This problem is new to MS4. Am I doing something wrong or is it a known issue?

In reply to by Kurpaph

Be sure you are adding a tie, not a slur - they look similar and have adjacent buttons on the toolbar, but very different meanings. Shortctus are T for tie, S for slur. If you continue to have trouble, please ask for help on the Support forum and attach your score there so we can check it out.

Musescore 4 a été mis-à-jour il y déjà plus de 5 mois et il a apporté des améliorations indéniables par rapport à musescore 3. Pourtant, je ne l'utilise pas car il est touujours impossible de lire les partitions sur iPad (pas de problème sur PC et Win 10) .
Pour être plus précis lors de mon dernier essai (hier) , j'ai pu lire une partition dans "Mes partitions" sur l'iPad mais dès que j'ai demandé de l'enregistrer dans le "Songbook", la page est devenue blanche non seulement dans le "Songbook" mais aussi dans "Mes Enregistrements" même après l'avoir effacé du "Songbook".
NB: Dans "Mes enregistrements" la page est blanche mais le fichier reste enregistré et es infos restent accessibles.

Travaillez-vous sur ce bug? Merci.

Attachment Size
MS4_Erreur.PNG 311.45 KB

Do you still have an unanswered question? Please log in first to post your question.