MuseScore 3.0 alpha Release

• Sep 12, 2018 - 11:35

We are pleased to announce the current state of MuseScore 3.0 via specially prepared builds with "alpha" label.

30alphaIcon.png icon301.png

Packages are available here

Elements autoplacement

The most significant improvement of 3.0 version is collision-detection engine which allows autoplacement for all elements in the score.
Starting from now, you don't need to adjust elements position manually, everything is done using smart algorithms.
Read more


TimeWise Insert/Delete

MuseScore 3.0 alpha introduces a new concept of writing timeless sheet music.
TimeWise Insert/Delete allows note input not depending on the current time signature of the measure.
We are improving user experience of this feature. For now, you can use it by following next steps:

  • Start Note Input ("N")
  • Hold "Ctrl" while input notes


Many additional improvements

Isaac Weiss highlighted scheduled improvements for 3.0 we continue improving day by day.
Read more

File version

3.0 alpha saves scores with the version which will be opened correctly in official MuseScore 3.0 Release.
Feel free to start working in the alpha version on a daily basis. Using common user scenarios and filing bug reports help us to improve MuseScore 3.0 even more. support

Scores created in MuseScore 3.0 alpha are not supported on right now.
You won't be able to use "Save Online" functionality in MuseScore 3.0 alpha as well as uploading the scores won't work until we support the scores created in MuseScore 3.0 on

Full support of MuseScore 2.3.2 features

Recent 2.3.X updates include significant fixes and improvements which are fully supported in MuseScore 3.0.
Read more about changes made in 2.3.1
Read more about changes made in 2.3.2

Upcoming changes

Filing bug reports

MuseScore 3.0 alpha is just a special build of 3.0 development builds, prepared specially for sharing with wide community.
It means the package you use will ask you to update once new builds are ready.
It is highly recommended to follow the last available version, because we deliver a lot of fixes every day.

Should you find bugs, crashes or any inconveniences , please, create an issue in the tracker.


Thanks to all the code contributors, testers, translators, and documentation writers!
Special thanks to GSoC students and mentors who did great work to make MuseScore better.

Follow us in MuseScore Development Blog


A small further clarification about the File Version: Some planned features may extend the file format with some new entries.

While 3.0 alpha saves scores with the version which will be opened correctly in official MuseScore 3.0 Release it may be that scores created in a later alpha/beta/final version of MuseScore 3 might not open (correctly) in the current alpha release.

For those new features, compatibility with the current format shall be ensured and sensible defaults for the new elements must be included.

Very cool! If I had known this was coming today, I'd have planned to make it the subject of my weekly MuseScore Cafe, but I'll plan on that next week.

In reply to by Anatoly-os

Touché! Yeah, I haven't wanted to make a nuisance of myself posting a lot about my outreach activities here, but I do plan to starting ramping that up a bit soon.

Anyhow, yeah, some time to explore more and get a sense of what makes to highlight will be good. I've been building my own versions to make the occasional bug fix but there is much that I haven't checked out yet, and I look forward to it!

Version 3.0 (when released) shall provide autoplacement of elements of the score by using smart algorithms, as shown in the first picture above, and that's a very significant improvement.
I wish to put a question: in scores written with previous versions of Musescore, users (or most of them) have already adjusted manually the position of the various elements of scores. When 3.0 will be released, these new algorithms will work only on new scores written with version 3.0, or will they work also on the scores written with previous versions of Musescore? (where the elements are already correctly placed manually). This could modify those previous scores?
Thanks for your attention.

In reply to by Roberto Fabris

I'm going to create special post describing auto placement in details.
Speaking generally, when you open 2.X scores, there are two types of placement. First one is manually adjusted elements, which don't participate in auto placement calculations. Second one is the elements which position has not been adjusted. Such elements will be automatically placed.
It is highly recommended to select all elements and apply autoplacement to them, then verify the score. If something is placed wrong, create an issue describing the inconsistency.
In future prereleases we will introduce special UI which allows users to apply autoplacement to all elements in the score.

Just wanted to echo jeetee's comments.

Alpha builds are useful, but I think there should be more warning/emphasis that these are still fundamentally unstable (especially if someone has invested their work), and I'm skeptical about being able to open such files later because I sense there might be (format?) changes to come.

In reply to by chen lung

Hey, please don't embarrass the community. Builds are stable enough comparing to ever existed 3.0 builds. Files format will be kept as it is now with possible changes, but for sure files created in alpha build will work in official release.
Please, stop disinforming people. If you want to discuss something and clarify things for yourself, please contact me.

In reply to by chen lung

What you describe is indeed true for development builds, however this here us about a 3.0alpha, there never was a 2.0alpha. So just take Anatoly's word that the file format won't change in any incompatible way for 3.0final. Layout certainly will though

In reply to by Jojo-Schmitz

We did have at least one beta for 2.0. Regardless though, it didn't stop people using either this or development builds for real work.

I was thinking about certain issues that may yet require format changes (non-5-line drumsets was one).

We have all commented when there is a problem, or a potential one (especially when things are new), but like anyone else I stand open to correction with an explanation. Given my investment in the project for years, such comment is unfair.

In reply to by chen lung

Yes, there was a 2.0beta, but no 2.0alpha. What comment exactly do you deem unfair?
jeetee's reply (which was written with Anatoly's consend on IRC) to the initial post states:
While 3.0 alpha saves scores with the version which will be opened correctly in official MuseScore 3.0 Release it may be that scores created in a later alpha/beta/final version of MuseScore 3 might not open (correctly) in the current alpha release.

In reply to by Anatoly-os

FWIW, I apologize if I have been off-message as well when I have expressed caution about using the alpha release. I do understand the goal is that scores created in the alpha will open in the final release. Would it be fair to say, though, that there may be layout changes, so that if you put a lot of work into customizing the appearance of your score, you might need to redo some of that work? That has been my assumption and is the main basis for the caution I continue to express when the subject of using the alpha for that particular purpose comes up.

Do you guys plan to give the musescore 3 more freedom to chose key signatures? I'd love to use key signatures with double flats and double sharps, but it doesn't work in any current version. And in musescore 1 at least I could chose different key signatures for different instruments, I don't understand why musescore 2 doesn't feature that.

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