News

Today we are pleased to announce the release of MuseScore 3 Beta Update, the third in our series of beta releases. Thanks to the fantastic feedback from users and their assistance in filing bug reports, we have maintained an incredible pace and have fixed over 100 issues since the first beta release last week! Most notably, this update should be much more stable and experience fewer crashes, plus scores imported from 2.3.2 or previous versions will work much better. So

For a third consecutive year, we are organising a MuseScore developer meetup in Brussels at FOSDEM, the largest European open source developer conference. During the weekend of Feb 2 and 3, more than 8000 open source users and developers gather to talk about free and open source software. You can get the unique experience of meeting the developers behind some of the software you are using already, including MuseScore. So you are all invited to come and meet us

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.

Download MuseScore 3.0

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]

Translating MuseScore

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

We 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]

Packages are available here

• Windows 64-bit
• MacOSX

Recent improvements

• The autoplacement engine was reworked. It now requires less space and works significantly faster.
  [inline:screencast 2018-10-31 11-39-11.gif]

• 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.

Abstract

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]

Packages are available here

• Windows 64-bit
• MacOSX

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

[inline:autoplacement300.PNG]

TimeWise Insert/Delete

MuseScore 3.0 alpha introduces a new concept of writing timeless

Welcome to MuseScore development news and digest blog.

[2018-11-23]

We again exceeded maximum allowed artifact storage size on AppVeyor. Sent the request to AppVeyor's support.
This is the reason of failed AppVeyor checks.

FIXED at UTC 12:22

[2018-10-30]

Alpha 2 is very close to its release state.
We applied new categories in the issue tracker (see https://musescore.org/en/node/277397).

GSoC 2018 Project "Score Diff Tool" was merged to master. Welcome testing!

[2018-08-24 00:00 GMT+2]

Fixed.

[2018-08-23 16:00 GMT+2]

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.

[2018-08-23 13:30 GMT+2]

• Migration completed successfully.
• AppVeyor builds MuseScore 3.0 64-bit version.
• Instructions have been updated respectively.

IMPORTANT NOTES:

• Everyone who already works with Visual Studio has to update dependencies folder content:
  • Downloading actual dependencies.zip archive
  • Delete dependencies folder in your MuseScore workspace
  • Unpack the archive

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]

Why do we need it?

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