MuseScore 3.1 Release Timeline

• May 20, 2019 - 16:41

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.


May, 22

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

May, 22-26

It's time to test the Release Candidate thoroughly and report any regressions found . We plan to address regressions asap. New Pull requests, except for ones fixing regressions, won't be merged.

May, 28

Release date. All translations will be grabbed as they are around 9:00 (UTC).

All dates are realistic estimations which might be changed at any time. There are no guarantees :)

Will be included in the RC


In reply to by Anatoly-os

You have removed it from the list, but the problem persists.

I made two video demonstrations to show the Error/Bug better.

The first score was played with Musescore 2: Bends Normal
The second score was played with the latest nightly of MS3: the Bends are Out of tune.

Videos are of high quality. You can watch it in full screen.

Playing with Latest Nightly:
OS: Windows 10 (10.0),
Arch.: x86_64,
MuseScore version (64-bit):,
revision: 624b90d:

In reply to by Ziya Mete Demircan

Thanks for the good presentation of the bug. The last entry in the list is the PR which is supposed to fix this. @MichaelFroelich is not around to discuss details and make small changes to the PR. Which means that we will revert the changes you referred to above or wait for Michael's response and finalise the fix.

Do you still have an unanswered question? Please log in first to post your question.