For all that MuseScore 1 was a decent entry-level scorewriter, it wasn’t until 2.0 that MuseScore really started to compete with the biggest names in the industry—especially astounding coming from a free and open-source project that no one had ever heard of five years earlier. It took a few years longer than anticipated, but when MuseScore 2 arrived it was simply massive.
Since then, from March 2015’s release of MuseScore 2.0 through April 2016’s release of MuseScore 2.0.3, some major changes and improvements have been made (among them playback of trills, ornaments, and glissandi, a more platform-independent rendering system, and a significant new notation element that didn’t exist before). But all of those changes have been in patch updates to 2.0.
You can imagine how significant, and how far off, MuseScore 3.0 must be.
I’d like to be clear: The features I’m going to discuss in this post are not, by any means, “coming soon.” This is a work in progress, and that is likely to be the case for quite some time to come.
But work on MuseScore 3.0 has begun! There hasn’t been such an exciting time since the team first started developing MuseScore 2.0—or maybe even MuseScore 1.0. So, it is my pleasure to let you know what’s going on behind the scenes. This is the first in a series of posts over the coming months, tracking development as it happens.
Broadly speaking, the vision is to make MuseScore smarter, faster, and easier to use. Of these, the smarter aspect is probably the most interesting, as well as the most complex to implement. In future posts, we’ll look at the faster and easier improvements; for now, let’s dig into smarter and see what it means for the future of MuseScore.Read more