MuseScore 3.3 Release Timeline
We are nearing the release of MuseScore 3.3!
Thanks to the hard work of the community, we improved already stable release of MuseScore 3.2.3.
- @DLLarson exposed a lot of properties and made fixes for the Plugin API
- @Tantacrul redesigned and @dmitrio95 implemented the redesign of the palettes widget. The goal was to simplify customization of the palettes and get away from the master palette. Check it out in the Beta version and let us know whether we succeeded :)
- @MarcSabatella made a lot of improvements for the accessibility of the editor including navigation
- @lvinken made a lot of improvements for MusicXML export and import
- @Jojo-Schmitz made MuseScore work with the latest version of Qt on Windows which reenabled NVDA support
- @mattmcclinch implemented some of the Tantacrul's ideas related to the Note Input workflow
Many other developers and testers reported and fixed bugs and implemented improvements which have made MuseScore better and more stable.
Updated: 24 October 2019
We have already implemented essential improvements related to the appearance, usability, and customization possibilities of the palettes. We are focusing on new users to let them understand MuseScore's facilities faster and easier, yet keep the workflow for experienced users the same or significantly simplify it.
One more thing we want to see in the upcoming MuseScore 3.3 release is the Tantacrul's Note Input workflow redesign implementation. @mattmcclinch generously helped the project and implemented the most significant part of the usability improvements. The changes were not massive, but significantly improve the UX of the Note Input workflow. It allows users to enter notes right after clicking proper duration without the necessity to enter "Note Input mode." At the same time, nothing is supposed to be changed in the usual workflow.
Meantime, the changes to the Note Input workflow have revealed the problems that the editor had all the time. The editor doesn't always show the currently edited place as it is done in text editors. As a result, the user might add, delete, or edit elements that are not in the current view, and do not even know about it. We are working on the solution to ensure any changes move the viewport properly.
After testing the changes, we will publish MuseScore 3.3 Release Candidate 3, which will contain all the changes that we plan to include in the final release in October.
ETA for RC3 is October 28.
ETA for the final release is October 31.
String Freeze remains valid, which means no new lines will be added until release. Translators have time to complete the translations until October 31, 9:00 UTC.
MuseScore 3.3 Release Candidate 3
MuseScore 3.3 Final release
All dates are realistic estimations which might be changed at any time. There are no guarantees :)