News

Today, we are announcing the release of the MuseScore 2.0 "Release Candidate". A release candidate means that we have done everything we plan to do for the 2.0 release, but we are welcoming one final round of testing to be sure we have not forgotten anything. Assuming all goes well, there will be a final official release of MuseScore 2.0 on March 24 that will be identical to this release candidate except for updated translations (see below). At that point,

From our first MuseScore users survey back in 2013, we learnt that the number one request was more and better documentation. In the meantime, as we were packing great new features into MuseScore 2.0, the need for good documentation would become even more necessary. So with the 2.0 release nearing, let's check what the state is of the documentation and what we can still do in the weeks to come.

Written documentation

First there is the 2.0 handbook which

With all the blocking issues being addressed and the plethora of other bugs fixed since beta 2, we have now set a release date for MuseScore 2.0!

* March 12th 13th: 2.0 Release Candidate (RC) for Windows and Mac
* March 24th: Final MuseScore 2.0 release for all platforms

So what will happen between now and the release date:
* Translating the MuseScore interface
* Reviewing and improving the 2.0 handbook
* Create a press release and prepare for

We are calling up everyone to help us translate the coming release of MuseScore 2.0 in your own language. Currently 2.0 is being translated in 53 languages but if your language is missing, please leave a comment so we can add it.

How to translate MuseScore 2.0

Step 1: Use MuseScore 2.0 RC.
Step 2: Register and login on Transifex, select your language in the MuseScore project, click on the Join team button and start

Just in time for Christmas, we are happy to present to you MuseScore 2.0 Beta 2. This beta release includes hundreds of bug fixes and other improvements made as a result of feedback from users of the Beta 1 release and subsequently nightly builds. There are even a few new features that have been added during these last few months. See below for more information on what’s changed.

[inline:MuseScore-2.0-beta2-christmas.png]

The official release of MuseScore 2.0 is still yet to

To wrap up this GSoC season, Google traditionally invites 2 mentors per project for a Google Summer of Code Summit in Mountain View. This year, it was the 10th anniversary so it was special. Google invited mentors and students, even organising a lottery to get more people in. The event was not taking place at the Google Headquarters in Mountain View but at the Marriott San José, spanning over 3 days. The reunion schedule was packed.

Meeting IRL

I

The MuseScore team is excited to announce the first Beta release of MuseScore 2.0! This is your opportunity to try out the new features, see if your "favorite" bugs have been fixed, and provide feedback that we can use to make sure the final MuseScore 2.0 release is as stable as the well-established 1.X series of releases have proven to be. This first Beta release is our way of saying we think we're done adding features for 2.0 and everything

The list of students selected for Google Summer of Code 2014 has been announced by Google. Among the 1307 students selected, 5 of them will be working on MuseScore this summer!

Now the community bonding period officially starts. Students will get to know their mentors and prepare for the program by reading documentation, hanging out in the IRC channel (#musescore on freenode.net), and familiarizing themselves with MuseScore. They will also introduce themselves to the community on the forum or

The most basic feature of a music notation program is note layout and rendering. In MuseScore, layout of notes - including chords, augmentation dots, ties, and accidentals - has not changed appreciably for years. But while MuseScore has always done a good job in the simple cases, there are a number of not uncommon situations where MuseScore made surprisingly poor decisions. This requires the user to adjust things manually - assuming he can even figure out what the correct layout

The submission deadline for students who wanted to participate in Google Summer of Code 2014 was today on March 21st. In total, we got 35 proposals! In the past 3 weeks, we got in contact with over 20+ students on IRC and on the developer mailing list. Last year, there were 21 proposals

Here is the number of new proposals per day. As expected, this year again it went a bit crazy at the end of the period!

[inline:shot_140321_201927.png]