MuseScore 3.4 Release

• Jan 24, 2020 - 16:24

Today we are pleased to announce another significant update, MuseScore 3.4. In addition to dozens of bug fixes, it introduces UX improvements when working with score elements and telemetry.

Download MuseScore 3.4 Release

Windows 64-bit Windows 32-bit macOS 10.10 or higher Linux AppImage
(64-bit only)

MuseScore 3.3 announcement

Single click improvements

We all know that MuseScore is a powerful notation software that can do almost everything in terms of music notation. We conducted a dozen of user testing activities with the ones who never used MuseScore and found that "double click" is an interaction pattern that is hidden for newbies. Respondents could not edit slurs and hairpins to adjust their positions; they couldn't even apply elements from the palettes. Double click is rarely used in touch interfaces as well (that's why the young audience isn't familiar with the double click interaction pattern.)

We aim to improve usability and make MuseScore as easy as possible for newcomers keeping all the fine-tuning features for professionals. We are glad to introduce the single click concept designed by Martin Keary (Tantacrul). The new approach provides an easy way to edit elements with a single click and makes double click unnecessary.

Check out the new approach and let us know what you think! We are always here to listen to your feedback and support.


We introduce Telemetry as a framework that allows collecting anonymous data of the app usage. The goal is to know our users better and make better design decisions. We want to know whether new releases perform better than the previous one. We want to understand why many people download MuseScore, run it once, and never use it again. We want to be sure that the changes we make don't harm the user experience. Another advantage of introducing a telemetry framework is the ability to track the Crash rate. It allows us to track regressions and make updates faster.

We respect your privacy and never collect any personal information (read more in our Privacy Policy). We are transparent in all senses. You can audit the codebase that is always open and available on GitHub and be sure that we never collect personal data. We also prepared up to date list of the events we track in MuseScore. We will keep the list up to date in case of any changes.

A full list of changes is available here.

Known issues:


This is the first version of MuseScore 3.x that I can launch without a sudden crash happening within just a few seconds, which is good.

In reply to by kuwitt

I'm happy that the program is working in both versions, I'm (a little little bit) annoyed for the 100MB of bandwidth I just wasted (my web traffic is limited, on a monthly basis). I'm an amateur software developer of some sort, though, so I understand the many, many problems that can make software development a joy and a pain.

In reply to by BarnieSnyman

Every version STARTING FROM 3.0. Never ever had any problem with the 2.x series, which I keep on regarding as GREAT and I think I will go on using for quite a while along with version 3.4.x (I have to get used to so many changes, and there are situations in which I can't afford being slow in transcribing the scores I need).
I think that the crashes could be due to the particular configuration of my old netbook PC running a 32 bit version of Windows 7 Starter since 2012.

In reply to by Aldo

That's believable, we didn't even have a 32-bit build of MuseScore 3 until quite a while into it, then I think only an unofficial one, and even the official one we provide now is certainly not tested nearly as well.

2.x was great for its day indeed, and still often the best choice for working with 2.x scores.

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