Community Blog

In the future it should be possible to have parts for every single voice in your score, so the idea is, that you can have a main score with SATB and piano with S, A, T and B in one stave and one excerpt with SA-TB, S and A in one staff and T and B in another and another excerpt with every voice in a single excerpt.

To achieve this, a new layout for the excerptsdialog is needed. So

Hi! My name is Peter, and I have been selected to work with MuseScore for this year’s Google Summer of Code. My project is titled “Semi-Realtime MIDI”, and the aim is to create a new mode of note entry for MuseScore - or actually a few different modes - that would basically allow users to enter notes by performing the piece on a MIDI keyboard and having MuseScore translate the performance into the correct musical notation.

You can keep up

Hello everyone! I'm very pleased to announce that I have been selected to work on the Annotation Support project for MuseScore as part of Google Summer of Code 2016.

I will be working on implementing support for annotations in MuseScore, whereby users will be able to mark/highlights sections of their scores, add comments, and so on.

I'm starting work early due to a short workshop coming up later in May.
To get started, I've made a list of features that

Hello everyone,
first of all thank you for your helpful comments and thanks for all the help and patience from MuseScore people on IRC! You guys rock!

I got a little update on the CC11 (de)crescendo. I thought writing some code would help and will bring me to the actual problems - and so it did. First things first - here is my branch in which I'm working on CC11.

What does CC11 do in SF?

The main "problem"

In this blog post I want to outline some general ideas of an improved Implode and Explode tool.

Recently there have been several problems with these tools. The actual implementation was done by Marc Sabatella out of a plugin he has written before.

Implode

To use Implode, you have to select complete measures, if you have just selected one staff, it will merge the notes in each voice of the staff to the first voice. If you have selected more

Finding out about the CC11 capability of Fluidsynth in MuseScore is nice. But what would be interesting is - when was it integrated and what happened since then to upstream?

By browsing the musescore-old repository I found that Fluidsynth got integrated with this commit on Feb-13th in 2007. At this time the last commit on fluidsynth side was this one from January 2007.

By looking at the synth.cpp file here and comparing it to this addition in fluidsynth we see

Good news everyone,
today I discovered that MuseScore's internal variant of fluidsynth supports midi CC11 (aka expression pedal). I did this by adding this line to mscore/musescore.cpp:

 void MuseScore::midiCtrlReceived(int controller, int value)
       {
       seq->setController(0, controller, value);
       if (!midiinEnabled())
             return;
       ...

Now every midi CC gets send to the synth (on channel one - have a look at the implementation).

In last week’s post, “Discovering MuseScore,” I wrote about how I first started using MuseScore 1.1 at the age of thirteen, how I very gradually became involved with the project, and how much I came to love and appreciate MuseScore. Now, I’m going to look at the other side of things: how terribly limited MuseScore still is in some areas.

Last week, I mentioned re-extracting parts using MuseScore 1 and having to go through them all again to

I’ve been using MuseScore since I was thirteen, when MuseScore was at version 1.1. I wanted to write music on a computer, and spending money was not an option. I used a different free program called Finale Notepad at first, but it was insanely limited (deliberately: the makers wanted users to become frustrated so they would buy other versions of Finale). MuseScore, by comparison, seemed to have no limits at all—at least, it completely satisfied my needs at the time.