MuseScore update available for MacOS

MuseScore update is now available for download and fixes one bug for MacOS Sierra.

This "emergency" release was triggered by several reports about "black screen" or "black page" on Mac OS 10.12 Sierra. You can see the whole discussion and process to fix this bug in the issue tracker.

The release for MacOS is exactly like MuseScore 2.0.3 but it contains 2 fixes:Read more

    Wrapping up Google Summer of Code 2016

    On August 30, it was the end of Google Summer of Code 2016. Google announced over a thousand successful projects and for MuseScore’s third participation, we are extremely happy with the results. We had four students working on several exciting projects for three months. Read further to learn about the results of their summer coding.Read more

    GSoC 2016 - Project Demo Videos - Semi-Realtime MIDI

    Semi-Realtime MIDI Demo Part 1: New note entry modes

    YouTube video: GSoC with MuseScore - Semi-Realtime MIDI Demo Part 1: New note entry modesRead more

    Semi-Realtime MIDI Demo Part 2: Rhythmic Groupings and Voice Separation

    Developing MuseScore 3.0: Making things easier

    Part 3 of 3

    MuseScore 3.0, currently under development, is on track to be smarter, faster, and easier than any MuseScore you’ve seen before.Read more

    Developing MuseScore 3.0: MuseScore gets faster

    Part 2 of 3

    MuseScore 3.0 is currently under development, getting ready to be smarter, faster, and easier than any previous version of the world’s most popular, powerful, and easy-to-use free and open-source scorewriter.Read more

    MuseScore 3.0 under development: MuseScore gets smart

    Part 1 of 3

    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—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 we're 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.

    One of the more important changes introduced in MuseScore 2 was a set of improvements to the note/accidental layout algorithms. Basically, it was all too common for MuseScore 1 to position notes from multiple voices halfway overlapping each other, and accidentals were often in the wrong order, leading either to bad sheet music or a regrettable amount of manual adjustments. MuseScore 2 delivered an outstandingly improved system, with default positioning adhering to the highest standards in engraving, and manual adjustments to notes and accidentals essentially never called for. Now, the next level is everything else.

    Introducing: Smart Layout.

    How often do you have to drag a tempo marking off the rehearsal mark it was overlapping? Or reshape a slur to avoid crossing through the notes in its midst? Or use a staff spacer to make room for some high notes? The frequency of problems of this sort is undoubtedly MuseScore’s biggest limitation currently, and it’s come up again and again.

    With the new layout system, MuseScore will be smart enough to automatically avoid these sorts of collisions (though not all of the specific examples mentioned above are solved yet). Below you can watch Smart Layout in action:


    That’s not even all. While the current layout algorithms unnecessarily prevent notes and accidentals from overlapping the same linear space (based on a theoretical boundary rectangle the height of the system surrounding each element), the Smart Layout system will allow them to nestle under or over each other as needed (based on a boundary the exact shape of each element), for a more condensed and evenly spaced layout. Like this:

    3.0 image.png

    And that is only the beginning of what's going to be coming in MuseScore 3.

    As I hope I made clear at the outset, this set of improvements is not anywhere close to ready. However, the very haziest outlines of what MuseScore 3 will be like are available for testing in the nightly builds. There is no guarantee anything will work. Let Werner Schweer warn you:

      “It crashes very often currently, and does other bad things.”

    So let’s fix that! You can help us develop MuseScore 3.0 by testing the latest features in the nightly builds, and reporting the problems you encounter. Your feedback is very welcome in the Technology Preview forum, and precise bug reports can be directly posted in the Issue tracker. If you’re a programmer as well as a musician, we would appreciate your help fixing the bugs—as MuseScore is free and open source, anyone can get the source and share code contributions on GitHub. You can also support the MuseScore 3 effort in the simplest way with a donation.

    Next time
    MuseScore gets fasterRead more

    Students Announced for Google Summer of Code 2016

    The list of students selected for Google Summer of Code 2014 has been announced by Google. Among the 1206 students selected, 4 of them will be working on MuseScore this summer!

    GSoC2016Logo.jpgRead more

    MuseScore 2.0.3 is released

    Since the release of MuseScore 2.0.2 last July, MuseScore development has been continuous. New contributors alongside old friends have been fixing bugs and adding enhancements. We are therefore very pleased to release MuseScore 2.0.3, the stablest and most powerful MuseScore yet.Read more

    Download MuseScore 2.0.3

    New features

    Join MuseScore for Google Summer of Code 2016

    MuseScore is part of Google Summer of Code 2016 (GSoC)! If you are a student and you have aspirations to help improve the open source MuseScore notation software during the summertime, this is a unique opportunity to work together with the MuseScore developers and get paid for it. Learn how GSoC works and read through the student manual.

    Read more

    New features in the nightly builds

    As the result of a quick reunion in Germany together with Werner and Thomas, several new features have been merged into master and so now appears in nightly builds. First, a selfie or it didn't happen.

    Team meetup in Germany

    There were 67 open pull requests two days ago. We merged 29, and closed or sorted for later several others. Most of the PR were about bug fixes but some implements new features. While we are into numbers, MuseScore has been written by 64 contributors as of today. Thanks to all of them!Read more

    Syndicate content