News

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

We 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

We are glad to announce upcoming MuseScore 2.3.2 minor release which brings fixes for several significant bugs:

• pending issue with uploading score audio
• Same note in different voices and lengths plays only the length of the shortest note
• Zerberus: add support for "global_volume=" opcode
• Zerberus (SFZ) instruments are too quiet compared to SoundFont instruments
• "Regroup Rhythms" crashes the program if measures contain Measure repeat symbols

The issues have been fixed, but require additional thorough testing to prevent regressions.
We are

Edit: After the release of MuseScore 2.3 on June 29th 2018, we found a couple of regressions that we addressed in MuseScore 2.3.1 released on July 6th 2018. We also updated all languages to latest translations. Check out the 2.3.1 Release Notes.

We are pleased to announce the release of MuseScore 2.3

MuseScore 2.3 is a unique release. Though a large number of improvements have been focused on percussion, this release contains bug fixes and other improvements that make

UPD (28.06.2018): the current version of MuseScore is 2.2.12 and is published as Release Candidate. The links below have been updated accordingly. Check out almost complete Release Notes.

UPD (25.06.2018): the current version of MuseScore 2.3 Beta is 2.2.11, the links below have been updated accordingly. Check out last changes and fixes.

UPD (20.06.2018): the current version of Beta is 2.2.10, the links below have been updated accordingly.

Today, we are announcing the public release of the MuseScore

My name is Marc Sabatella, and if you're reading this on the forums at musescore.org, you probably already know me as one of the developers of the software and a (very) frequent contributor here. You may also know me as the author of the comprehensive guide Mastering MuseScore, and if you've been around long enough, you may remember me as the composer of the song Reunion that was long used as the demo for MuseScore.

Today, I am excited

On April 3rd we released MuseScore 2.2.1. As stated in the announcement, the next major version of MuseScore, version 3.0, is still in the works. It’s big endeavor to make MuseScore smarter, faster and easier to use.

In the meantime, we are continuing to further develop the new MuseScore_General SoundFont and quality of playback based on the input and insights of the community.

One area of playback where there has been considerable feedback has been percussion (especially

MuseScore user interface is available in 64 languages. Right now only 18 translations are 90% or more complete. We want to make sure that as many translations are completed for the release.

To give translators a head start, a "Strings Freeze" for MuseScore 2.2 is now on. Starting from now, we will not change or add any string in the code. Any string you translate now, will end up in MuseScore 2.2!

If you want to know how complete the

Hello fellow MuseScorers! This is S. Christian Collins, virtual instrument designer and creator of the GeneralUser GS SoundFont. I have been asked by MuseScore to make some major upgrades to the default SoundFont for the next version of MuseScore (and beyond).

My goals for the new SoundFont include:
1. Improve the quality of the instrument sounds, starting with those most frequently used in scoring.
2. Address known issues with the current SoundFont, including notes that are out of tune, and

Cross post from the MuseScore blog.

Dear all,

Today we’d like to share important news with you concerning MuseScore.

Ten years ago we (Werner, Nicolas and Thomas) started working on MuseScore with the mission to democratise access to sheet music. The plan came in two steps. First by developing free music notation software for everyone, then followed by a platform to upload and share sheet music. The latter is a commercial service which sustained the development of the free