Today we are pleased to announce the Release Candidate of a significant update, MuseScore 3.1.
This release includes the changes announced in the MuseScore 3.1 Beta release, and it also introduces a few significant improvements related to automatic layout, performance, and fretboard diagrams.
This is a pre-release version of MuseScore 3.1. The final version will be available by the end of the month.
Hello everyone,
We are nearing the release of MuseScore 3.1. Thanks to the recent improvements by Marc (@MarcSabatella), James (@TheOtherJThistle) and many other contributors (we will acknowledge them later) MuseScore 3.1 has become the most stable and full-featured version of MuseScore ever.
We are going to prepare the Release Candidate on May 22. If you know about any regressions in MuseScore 3.1 Beta compared to MuseScore 3.0.5, please let us know so we can quickly prepare a
Read moreToday we are pleased to announce the Beta release of a significant update, MuseScore 3.1.
MuseScore 3.1 Beta can be installed along with the stable release.
Both versions will share the same data directory Documents/MuseScore3. Files created in MuseScore 3.1 are fully compatible with MuseScore 3.0.5.
[inline:announcement31beta.png]
There are a few major features which are requested all the time, e.g. the first
Read moreToday we are pleased to release MuseScore 3.0.5.
The focus of this release was performance and stability. We reached an incredible boost in optimization so MuseScore 3 is now faster than MuseScore 2, but is still powerful with the smart layout feature. The crash reporter facility introduced in MuseScore 3.0.3 lets us concentrate on fixing the most frequent crashes. MuseScore 3.0.5 introduces the patch for the crash on startup on macOS, which was reported dozens of times.
We are glad to announce hotfix MuseScore 3.0.4 release.
MuseScore 3.0.3 introduced some great improvements as well as unfortunate regressions which were addressed in the MuseScore 3.0.4 release.
Read more about the features introduced in MuseScore 3.0.3 Release.
[inline:announcement304.png]
Today we are pleased to announce MuseScore 3.0.3.
The main changes in this release are the performance improvements, the fixes for massively requested functionality like parts playback and the new crash report facility.
Both 32 and 64-bit packages for Windows are now officially supported and based on the current Qt 5.12.1. The Mac build has been upgraded to Qt 5.12.1 too.
[inline:announcement303.png]
This
Read moreToday we are pleased to release MuseScore 3.0.1. This is the first in what we intend to be a regular series of updates to MuseScore 3, the ground-breaking version of the world’s most popular music notation software.
[inline:announcement301.png]
This update fixes dozens of issues that were found in the original 3.0 release, and it adds few improvements as well. For a complete list of
Read moreToday we are excited to announce the release of MuseScore 3, a major step forward for the world's most popular music notation software.
The strengths of MuseScore have long been its ease of use, the large community of creators and wide availability of sheet music on musescore.com, and of course, the fact that it is free. We are also proud of how powerful MuseScore is and the quality of the engraving that it can produce. With the release of MuseScore
Read moreToday we are pleased to announce the release candidate for MuseScore 3. Since the first beta release less than a month ago, we have resolved over 200 issues. Now, with all the most critical bugs fixed, we have produced one final pre-release build for testing. If no additional critical issues are confirmed, we will release MuseScore 3 on December 24!
[inline:splash.png]
Today we are pleased to announce the release of MuseScore 3 Beta Update (December 14, 2018). Users have continued providing valuable feedback, and we have continued our torrid pace of fixing bugs with over 70 issues resolved in the past 7 days since the previous update! This release also brings some significant improvements to the automatic placement algorithms that should greatly reduce the number of times you need to override its decisions.