MuseScore 4.1 is now available!

• Jul 12, 2023 - 09:05

We are delighted to announce our first major update to MuseScore 4 since it launched last year.

This update includes a significant upgrade to our playback engine (making the app run more efficiently) plus new features for harp and guitar notation, the ability to customise ornaments, new auxiliary channel strips in the mixer, and hundreds of engraving improvements and bug fixes, plus much more!

A huge thank you to the dedicated MuseScore community for supporting this release with implementation, testing and translating. We hope you enjoy this latest version and are excited to hear your feedback!

All the best from,

The MuseScore team.

How to get MuseScore 4.1

I already use MuseScore

You will receive a notification to update to 4.1 next time you launch the app.

If you have the Muse Hub on your computer, you'll automatically get the latest version when you open MuseScore from within the Hub.

I'm new to MuseScore

Download the latest version from The app can be downloaded with or without installing Muse Hub.

Watch the release video

New features in MuseScore 4.1

  • New engraving and playback support for ornaments, including the ability to set custom alterations for trills, turns and mordents
  • A major improvement to the app's performance
  • A dedicated new default reverb, which can be adjusted for each instrument track as well as globally across the entire mix
  • New auxiliary sends in the mixer, allowing instrument tracks to be routed to dedicated auxiliary channel strips for applying audio effects
  • New engraving and playback support for capos on guitar staves
  • New feature for displaying harp pedal diagrams
  • Dynamics and expression text now automatically combine, plus new controls for scaling and positioning dynamics
  • New live braille feature where the selected measure is displayed in braille music notation in a panel below the score and on connected braille displays*
  • Upload audio directly to, allowing you to build a portfolio of your audio content to share with the world
  • View and open your online scores from directly from the desktop app

Other updates

  • Save to cloud: option to make a score "unlisted"
  • Publish to option to either replace the existing published score, or publish the score as a new file
  • New loading screen when opening multiple instances of the app
  • Fixed syllable-based pasting of lyrics
  • A more reliable VST scanning process
  • Around 100 engraving fixes and improvements (Read this article on for a complete list)
  • Numerous bug fixes

Known incompatibilities


Yay! It does have much better audio. I tried my largest score and it worked with multiple Musescores up and there were no popping noises until I used other apps which is much better than before. Two problems so far though, On the main app, the first one that pops up, the logo isn't there and on the same one a score that I'm trying to save to the cloud is stuck on saving online.

In reply to by beniegenie

Regarding the missing logo on startup, I saw that on one of my Linux systems at first, then it went away. Might have to do with the system caching images or something, not sure. If you continue to see that, best to open a new thread in the Support forum and provide more details.

This is fantastic news. Thank you! I tested the RC and it seemed much more solid than 4.0.2.

Linux Mint user here. The MuseScore update feature downloaded the new version, then I closed the app when prompted, after which my downloads folder displayed containing the .AppImage. I assume this is by design, but because I'm using the Flatpak release I will look forward to updating MuseScore through the Linux Mint Update Manager when available.

In reply to by daveburkevt

This is a a pretty janky way of doing things honestly I was surprised to see an update offered since I’ve installed MS through an official repository. I wasn’t keen to try the update since two-timing your package manager is not usually a good idea.

If it’s just an Appimage, that’s fine, but just downloading it without asking where and then dumping the user in a file manager with potentially a long, random list of files in front of them, is not exactly the acme of user interactions.

Also, for me, out-of-the-box the Appimage doesn’t play any sounds.

In reply to by Moilleadóir

Can you explain what you mean in more detail? If a third party provides their own build of MuseScore in one of their repositories, that’s their right but is out of MuseScore’s control. Indeed often those builds don’t work well and are very often way out of date. Which is the whole reason we started providing AppImage builds in the first place.

But if you’re encountering some sort of issue with the official AppImage, please start a new thread in the support forum and describe the problem in more detail there.

In reply to by Marc Sabatella

“Often these builds don’t work well”

I have no idea what you base this on. It’s certainly possible for anything to happen when a program is packaged, but if you’re going to make wild generalisations like that you should back them up with some data.

If the Appimage is now the recommended format, that’s fine, but since I don’t have a problem with the version installed by the package manager, but I do with the Appimage (no sound), there’s not much incentive for me to change or to spend time debugging it for you. Appimage only distribution would also further entrench a second-class status for Linux though (due to lack of integration out-of-the-box), but fine.

It is still disconcerting for the user to have something labelled an upgrade when it’s just downloading a file and opening a file manager. That’s not an upgrade. It doesn’t integrate with menus, launchers, panels, etc. or anything in the OS or window manager, it’s just a disconnected file that you can run.

A better distribution-agnostic format for Linux would be flatpak, which does integrate but is probably a little more complicated to set up.

In reply to by Moilleadóir

"if the appimage is now the recommended format"
It has always been the recommended format, in fact it has always been the only provided format by the MuseScore team, therefore the only format for which they can guarantee that the compilation options and the dependencies were correct.
You are of course free to use MuseScore compiled by anybody else, including yourself with potentially your own fixes, but the version on which they can work and fix reported bugs is the appimage.

In reply to by frfancha

Which is a bit self-defeating. E.g. if I don’t use (or have need of) the appimage then I can never report a bug?

The people most likely to report a bug are probably not the ones using the appimage.

I’m still not sure that the update procedure is that great even if you start from an appimage. Does it use AppImageUpdate? Does it update the file in-place? Does it require the user to construct their own scripts/.desktop files to run some changing version-named filename downloaded to some random folder?

AppImage has its virtues, but it’s very messy compared to flatpak, snap or distro packaging. It’s not a guarantee of a good user experience.

In reply to by Moilleadóir

For me I think AppImage is "cleaner" than those other formats (well not the distro package, I guess). Both snap and flat pack require a bunch of dependencies and I always have trouble with them living in their little sandboxes where they can't access certain areas that I actually want them to be able to access sometimes. I still report bugs with the AppImage, what's stopping you?

In reply to by reddiesel41264

As previously explained, I have no need. I’ve always used the distro version and it works fine. I would have to do some extra work to integrate the AppImage.

A difference between AppImage and flatpak (or snap) is that flatpak can share some of those dependencies between programs, making the installed size smaller, but each AppImage has to include everything. Flatpak & snap also have better integration out-of-the-box & easy/automatic upgrades.

This is way off-track anyway. My point is that the upgrade experience is not optimal and makes some assumptions about how the app is installed. Maybe someone will take that feedback onboard, maybe not, but there’s not much value in having a format feud.

In reply to by frfancha

Well, not quite "always"!!!

Musescore did not begin using Appimage for Linux until version 2.0.3 in April of 2016. Before that you could either compile your own or depend upon the distributors for your version of Linux.

The Appimage works quite well and is a huge improvement over the previous method of distribution. A much better choice than Flatpak.

In reply to by Moilleadóir

The statement "Often these builds don’t work well" is based on my 12 years of development experience on the MuseScore project. Virtually every single release of MuseScore, one or more Linux distributions has included a build that simply doesn't work correctly due to things like wrong build flags, incorrect versions of dependencies, missing files, etc. Plus of course, often the repositories are just plain out of date, still delivering years-old versions.

Throughout the early history of MuseScore this made for an unacceptably poor experience for our Linux users (including myself), and that's why we took on the additional work of building and delivering ourselves in AppImage format - sometime during the MuseScore 2 lifecycle as I recall. So there is nothing new about using AppImage - it's been the main supported way of obtaining current and correctly-built versions of MuseScore - including all MuseScore 3.x and 4.x versions.

AppImages do - or can, anyhow - integrate with your desktop environment (menu, etc). Simply run from the command line with the "install" option and it installs normally - creating a desktop file, placing icons in the correct locations, setting up MIME types etc - the whole deal. Run with the "update" option to update, and that works beautifully, automatically downloading the new version and installing in place. Not all AppImages support these features, but MuseScore certainly does.

So anyhow, if the version from your package manager happens to be current and to work correctly for the current release, great! But in general, if you encounter problems that don't seem to occur for other people, know that this is indeed a possible cause. And that the AppImage is a likely fix.

Good afternoon,
after several attemps it is not possible to load Musescore on my computer. The announcment tells me that the type of processor dose not fit. The same problem with loading the Muse-hub.
This app cannot be loaded on my computer with the windows-10 Home program version 22H2.
Please tell me wat I have to do because this program is very important for me.

With kind regards.
N.S.J. Hoogland the Netherlands
mail to:

In reply to by mrmjb

Excuse my ignorance, aren't all the major distros moving to pipewire these days anyway? And then if they are implementing VST support in linux, where does JACK fit in I wonder? I guess what I am curious of is how do you find jack useful for musescore? Speaking for myself, JACK always seemed like a real neat thing for what it's designed to do (I.E orchestrating many inputs at low latency in a live audio setting), but for Musescore terms I never could find a practical use for it that I couldn't already simply do with ALSA Midi. But I always figured someone must have a use for it, I was always curious what that was.

In reply to by graffesmusic

I don't think anyone can definitely say that the core team would never choose to do it, but clearly it can get done a lot sooner if someone in the broader community volunteers. And to be clear, that is precisely how MuseScore has always worked. There has always been a tiny core of programmers implementing the overall framework (for many years it was literally two people) and then hundreds of community volunteers adding features, fixing bugs, and generally keeping things running smoothly. The same is true of most open source software in fact. It's indeed what open source software is all about.

In reply to by alextone

Genuinely curious, what is the importance of JACK for MuseScore? Most of the professional audio engineers I know use Macs, and never even heard of it. The protocols they use are Apple AU or VST. JACK seems to be a very niche product even among audio people.

Hot take perhaps: we Linux users are always very vocal about our tech, but we are a tiny fraction of the wider world. I can't say we always advocate to push our small resources in a way that is the most effective for the most people.

In reply to by Joshua Pettus

JACK is pretty flexible and can be used for multiple purposes that involve connecting applications, but in particular, on Linux, it's the primary way one might take MIDI output of MuseScore and route it to the input of a DAW, or sync with a video player, etc. It is or has been available on WIndows and macOS but it's indeed not as well-known.

As far as I personally am concerned, JACK is more a means to an end than something I care about in itself. I'm personally more concerned with seeing those sorts of connections made equally simple on all platforms than I am about which specific protocol is used on any one given platform. But perhaps others have other uses for JACK they'd like to clarify.

And yes, it's true that because MuseScore originally ran on Linux only and was forked from a Linux-only sequencer, it of course relied on Linux-only MIDI and audio protocols from day one. On the other hand, it had zero support whatsoever for Windows or macOS until the user community became involved and ported it. And even after the original core team was in place, without the contributions from the community, MuseScore would not have had support for tablature, accessibility, chord symbol parsing and playback, customizable fretboard diagrams, slash notation, single note dynamics, MusicXML import or export, or dozens of other features we all take for granted. This was all done by the community.

Again, the involvement of the community is a huge part of what has made MuseScore what it is over the past 20 years. Expecting the core team to implement every single feature anyone might possibly want just isn't reasonable - it isn't how open source software works. And that's a good thing, as it allows us all to take some ownership and play a role in shaping MuseScore, and frees the core team to do more.

In reply to by Joshua Pettus

No problem. I will answer under my own experience. I really need Jack MIDI for musescore (i use 3.6) because is the Audio system I use. Simply. I dont want bridges. I dont want to enable/disable the server. AND I WANT ALL MY JACK AUDIO APPS RUNNING WHEN I WRITE SHEET MUSIC. (Reaper, Audacious, Carla, etc.). We love Routing. We love programming. We love Music. We love Recording. We love producing. And we love Linux. So JACK is the answer. Pipewire?? No I have no time. Maybe someday.

Excuse also my ignorance, aren´t Musescore seed on the Linux Pro Audio community? I dont know any musician friend using Linux, and all of them (windows and Mac) Uses SIBELIUS. (I think I'd probably use also because some useful features like adding staffs just in some parts of the sheet). But anyway, It seems the deveolpers target are the Sibelius market and had forget the basis that represents JACK MIDI musicians, but again, Excuse my ignorance

In reply to by mrmjb

Really appreciate the replies and history lesson folks. Personally I would like to see JACK support back firstly because I use it with JACK all the time and secondly just ideologically it seems a backward step for music production on Linux. Unfortunately the contributions I can make to open source projects are limited to advocacy and financial - I'm not the person to be trying to implement this feature.

My own use case is that I like to compose by recording stuff and then transcribe it later - I do a lot of writing backing vocals in particular like this. So I'll have JACK and Ardour running and record into that then have MS3 open connected via jack sharing plugins and midi keyboards so that I can quickly switch into MS3 to transcribe as I go.

In terms of the wider music production on linux - this is not something I know a lot about and I'm happy to be told I'm wrong - I believe that to be considered a professional production ready environment for film (multimedia I guess) there are a number of tools that the environment must have and they must be able to connect to one another and linux was able to tick every box but no longer because now the scoring software is unable to connect with the other bits.

As regards Pipewire - again not something I know lots about and again please let me know where I'm getting things wrong - my understanding is that it will solve a lot of audio problems and remove a lot of the need for JACK but I don't think it's production ready yet and I'm also pretty sure I remember Paul Davies saying that there'll still be some niche use cases that pipewire won't solve and which JACK will still be necessary for - I don't think he elaborated on that but he does know his stuff and I'm inclined to believe what he says.

I do think it's a real shame that JACK support is gone but MS is great software and this release is smashing and I still advocate strongly for MuseScore over anything else - I always recommend it to my students and colleagues.

Hooray! So happy that MuseScore is progressing so wonderfully with so much support behind it!

I did notice that when adding articulations, the system has gone back to the "On or Off", rather than the new three-stage "Some, All, or None" method that was introduced in 4.0. Is this a permanent change? If so, is there room to add the ability to switch that input mode back on? I found it to be super useful, and it'd be a shame to see it go.

In reply to by Dionne Hendricks

Can you explain what you mean in more detail? The only change I am aware of to how articulations are added has to do with how combined articulations like tenuto-staccato are handled - they can now be positioned independently with improved automatic layout. I don't know what "some" means in this context, though.

In reply to by Dionne Hendricks

Hmm, sounds like 4.0 - 4.0.2 had a bug that is fixed now as the command was always meant to toggle, but maybe there was a specific exception made on purpose? There was a different change made to how the articulation commands work and maybe this was just a side effect - that I'm not sure of.

Anyhow, the usual way to remove all the articulations from a selection would be to first select them (eg, click the first, Shift+click the last) then press Delete. Or use Select / More to make more complex selections. This also has the advantage of being the same method you'd use to delete other types of markings as well (eg, dynamics, chord symbols, etc).

For further questions about how to use MuseScore, best to ask on the Support forum.

Hello there!!! I just want to know what to do because in my laptop musescore crashes all time. It doesn't run correctly, so I can't work on it. When I try to work it freezes alomost evey 5 min, and then 20 seconds later it beguins to work. What should I do? Do I have to download another thing to make it work correctly? I downloaded 4.1 hopping it would be fixed but it is still that problem. Any help, please. Thanx.

I hope this 4.1 update fixes the playback selection problem where it plays only the track selected instead of the whole score. This poorly thought out change has kept me at Musescore 3.6.2.

In reply to by reddiesel41264

There’s never a time when it’s not useful to have this ability, so instead of disabling it, what makes sense to me is to simply to have two playback commands, one that solos the selection and the other that doesn’t. Then at any moment you choose the one you want rather than needing to constantly enabling and disable something. Or something like that.

Good morning! I've been using Musescore 3. Everything works fine. I'm very happy with the results. So I installed Musescore 4. But the sound is dragged, broken, fragmented. I have 64 bit AMD. Could someone evaluate the reason for the fragmented sound?

In reply to by likemat496

I'm very much looking forward to this! Meanwhile, though, note you can still select individual sounds as long as the soundfont is packaged as separate files for each sound rather than one "monolithic" file. I have provided a ZIP file for MS Basic that does exactly this - see…. There are also free tools you can download to split any other "monolithic" soundfont into separate files for similarly easy use. And on Windows and macOS. you can use the free Sforzando VST to access sounds.

Wow, love to see all these new updates! Just some quick comments:
-Musescore won't open after the update because is trying to open the Waves vst3s, i have to manually remove them every time i use the app and and reinsert them if i wanna use them in my daw. (in b4, yes, the license is up to date)
-I was trying the partial capos feature, im amazed to finally see it in musescore and im looking forward to using it a ton, BUT, it bothers me that i can't put a full capo AND a partial one, as in full capo in 2nd fret and partial capo in 4th fret (if i can, i haven't figured out how). I know i could just transpose the score up to match the full capo and then use the partial capo funtion, but this is one of the things that make guitar pro more comfortable to use when writing weird guitar parts.

Anyways, nitpicks aside, great work and thanks for everything!

Hello, I must say I love MuseScore as it is an amazing and clean notation software, and with MuseScore 4, the sound library has expanded greatly, as if there is an actual live orchestra playing your projects. I would like to ask something about the sounds - I myself am an accordionist, and I see that the sound library for free reed instruments has not been updated in MuseScore 4. I understand that getting a better sound for free reed instruments such as the accordion may be difficult, but do you have any plans on adding a better sound, complete with working registers? Cheers

Actually, it's cool, of course. I was happy to take advantage of the reverb. And you can finally choose where to upload the file (to an existing file or create a new one)
But compared to the previous version I now have bad midi export. I exported midi before 4.1 and everything was fine. But now I do it and the following happens. The synthesizer notes disappear altogether. And the piano notes get changed. The program FULLY ignores strokes, tremolo, fills (plays as normal eighth notes), accents and so on.
So I'll have to somehow roll back to the old version now to try to export midi again.

In reply to by RaptorTV

I checked and really on the previous MuseScore version (4.0.2.) the MIDI is exported normally. All fills, tremolos, etc. work as they should. The program takes them into account when exporting. (I remind you that in 4.1. Musescore bail on it / give up on it).
Please, correct the flaw! :(

i found an issue on mac with this update: it’s crashing when i open my online score(s) and, when i change the playback to musesounds it’s crashing. the device is mbp 2018 with ventura 13.4
when i tried on my lenovo windows laptop it is fine (used the same mscz). tried re-installing musescore via musehub and without musehub doesn’t seem fix the issue. does anyone facing this issue? how to fix this?

Possible bug? Is anyone else having a weird playback issue with appoggiaturas (grace note slurred to the main note?) since upgrading from v.4 to 4.1? The issue I have, since the upgrade, is that both notes will hold on for the entire bar - see screenshot attached. In the screenshot, the notation for Tpt.1 is what I want to hear (and was hearing before the upgrade), but Tpt.2 is showing an example of what I'm actually hearing from Trt.1. Is this the same for everyone??

Attachment Size
Screenshot.png 13.68 KB

Only reason I don’t used musescore 4 and I still use 3.6 is cuz it lags. If you guys could make a feature so note input was faster or manually set how much ram and CPU it can use that would be nice so it is less laggy. Also more drumline features. I use MdL and idk if muse. 4 has it also.

In reply to by jamsch5188

MDL works well in MU4 (on Windows) but requires a slight work-around. Here is how you can use MDL in MU4:

  1. Download and install Plogue's "Sforzando". It is free and works on Windows, Mac, and Linux.
  2. Download and install MDL in MU3.

  3. Run MU4. On the Home or StartUp page, select "Open other..."

  4. Navigate to "C:/Document/Musescore3/Extensions/MDL/1.3.1/templates" and select the MDL template that you wish to use.
  5. With your template open, open the MU4 mixer. For each instrument in your template, under the VST dropdown select Plogue's Sforzano as the instrument.
  6. When the Sforzando window opens, in the top right hand corner you will see the word "empty". Click on that word and a dropdown will open.
  7. Select "import" from the dropdown.
  8. Navigate to the MDL folder (C:/Documents/Musescore3/Extensions/MDL/1.3.1/sfzs) and choose the appropriate sfz file for each of your instruments.

That is all there is to it! It takes longer to type it out than it does to actually do it.

At what point will the Version 4 compatible scores open in the ipad app please? It's a pain having to go back to a PC just to open and export stuff back to the ipad again


I use Musescore to write scores, a lot of the time! Version 4.1 is very cool, stable, ok !!! I would like to know how to use it with tabs and a single instance. Current version appimage 4.11...
Thank you for your help!


when the f is there even gonna be a new update?? unless the so-called "staff" at Musescore have just been vacationing this whole time (I wouldn't be surprised), it's been almost 4 or 5 months already.

In reply to by PianXtremeYT

Um, have you not been actually following this Announcements forum? 4.2 is in beta, probably will be releasing any day now. But also, 4-5 months between release is not at all unusual. In the past releases have rarely come faster than that. MuseScore 4 is actually pretty unusual in how many updates there have been in only a year. And you can always follow the progress on a daily basis by checking out the nightly builds, and the history on GitHub.

In reply to by Marc Sabatella

mm, yes, and yet even with the update :

Any Muse sounds are still delayed when hitting the play button

Invisible engravings cant just be clicked on and made visible again, you have to move the page a little, THEN click on it, but you have to move around again to make something else visible again

there is not even a "pedal without line" thing, so I'm forced to use a rosetta which is unprofessional in different circumstances in music,

Dynamics are still awful when using two, ie MF in bass and P in Treble

The piano keyboard setting doesn't play like MS3 does, flashing when nots are changed.

Arpegios still fckd when trying to use them in more than one voice in the same stave

There isn't even a fucking soft pedal feature

Using muse sounds limits you to ONLY play as loud as whatever dynamic you choose, and the velocity of that dynamic can't be changed and is stuck to 64.

Need I go on, no.

Go ahead and run you guys' software, site, and nonsense however y'all want; I quite frankly just find it sad that after 4 months very little has been done, and the issues that are most common like these STILL haven't been fixed.

These are common issues, and all I get is literally as if I am still using MS 4.1
So whatever...idc

In reply to by PianXtremeYT

I think you need to calm down a bit. This is free software that’s primarily for scoring/printing music. The fact that you can also play that music is an added extra. I’m sure we’d all like it to be better, but if you’re not involved in development you can’t judge how difficult or how long these things take to implement.

Even paid software is not guaranteed to fix everything you want in four months.

If you want total control over MIDI you should be using a MIDI program, not one for musical notation.

In reply to by PianXtremeYT

Invisible elements can be selected directly if you haven't turned off the option to show invisible elements.

If you prefer the pedal symbol with no line and also no rosette, just clear the end text for the version with the rosette. You can also customize the text and symbols to notate una corda.

Muse Sounds is still new and improving steadily, but be aware you can get more customization (eg, for velocity) if you switch to a soundfont if you should need it.

Improvements to arpeggio and dynamics playback and other features are in the works. Profanity won't speed the process. Meanwhile, should you have other questions about how to use MuseScore, feel free to start new threads in the Support forum.

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