We are pleased to announce the release of MuseScore 3.0 Beta.
We have been working on MuseScore 3 ever since the release of MuseScore 2 back in 2015, and with this Beta version, we are one big step closer to a final release. Meanwhile, we have fixed all the critical issues reported against the previous Alpha versions. We want to make sure MuseScore 3 is as bug-free as possible, so please help us test this Beta release.
Next public version of MuseScore 3.0 will be MuseScore 3.0 Beta. It comes with a lot of fixes made after Alpha 2 release.
[inline:ms_splash_beta.png]
We are going to push new strings from MuseScore 3.0 to Transifex. It means there will be a lot of new strings to translate. We need your help to finish translations.
You can find all the instructions on this page. While you are translating, you can test your changes directly in a MuseScore
Read moreWe are pleased to announce the MuseScore 3.0 Alpha 2 release. This release shows the current state of MuseScore editor development. We fixed a lot of issues found after the first alpha release as well as others that existed before.
[inline:mu blog_upd.png]
Loading and displaying scores created in MuseScore 2 versions was improved. Custom
Hello everyone.
We are pleased to announce upcoming changes going to happen with the Issue Tracker.
Current categories describing the issues lead to misunderstanding in terms of priority and importance. Lack of predefined categories led to creating separate hit lists for particular versions summing up the most important issues to fix.
Taking the best practices from existing bug trackers, I prepared an update for the categories we have in the issue tracker. The most important goal here is
We are pleased to announce the current state of MuseScore 3.0 via specially prepared builds with "alpha" label.
[inline:30alphaIcon.png] [inline:icon301.png]
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
[inline:autoplacement300.PNG]
MuseScore 3.0 alpha introduces a new concept of writing timeless
Read moreWelcome to MuseScore development news and digest blog.
We decided to revert the changes to the MuseScore_General soundfont due to the regressions.
Current soundfont version is 0.1.6.
To collect artifacts from AppVeyor, add "collect_artifacts" to the commit message title. Read more
Fixed.
We do have a known issue related to last 64-bit builds: https://musescore.org/en/node/275547.
Applying solution is in progress. We will update this topic once it is fixed.
IMPORTANT NOTES:
We are pleased to announce a big step forward in compilation under Visual Studio and MSVC respectively. Compilation under Visual Studio Community is now available and fully supported.
[inline:Frame2.png]
MuseScore 3.0 is based on the latest Qt version. Unfortunately, QtWebKit which is used for MuseScore Connect is not presented in QT since version 5.4. So we migrated from QtWebKit (QWebView in particular) to QtWebEngine. Unfortunately, QtWebEngine team doesn’t maintain libs for MinGW due to the
Read moreWe are pleased to announce the release of MuseScore 2.3.2 which resolves several significant pending bugs, as well as a few regressions.
Among the fixes in this release is the “Upload Score Audio” issue. Now, If you use custom soundfonts or the MDL extension and share your score to Musescore.com using Save Online with the upload score audio feature, the score upload process should just work and playback should be as intended.
Another improvement is increased volume of Zerberus
Read moreWe are glad to announce upcoming MuseScore 2.3.2 minor release which brings fixes for several significant bugs:
The issues have been fixed, but require additional thorough testing to prevent regressions.
We are