Top Groups


Score taken down for infringement of rights

I received the following email from MuseScore:
"Your score has been taken down
Hello Papibois,
We received a report that your score "Ecce quomodo moritur justus" is infringing on someone else's author rights. We have taken down this content from MuseScore for the time being.
Reportedly infringed copyright:
Artist: Composer
Song: Ecce quomodo moritur justus
Publisher: CEDRO (Centro Español de Derechos Reprográficos)
You can dispute this report, if you believe the copyright content has been mistakenly identified or if you have obtained all the necessary rights, licenses and/or permissions to upload and share this work on MuseScore.
In order to do that, please go to the link:

Yours sincerely,
MuseScore team"  
In response, I filed a dispute thread as proposed, arguing that this work written in the sixteenth century has long been in the public domain (CPDL), as can be seen here:
Besides, on the PDF downloaded from this site and from which I edited with Musescore, the following statement can be read in full:
"Copyright © 1999 by the Choral Public Domain Library (
Edition may be freely distributed, duplicated, performed, or recorded."
I don't have an answer yet, but I would like to understand how I could usurp anyone's rights.

Release 2.3.0

Trends in the modern world are moving towards simplification, acceleration and improvement. We add people as friends to Facebook, watch photos on Instagram, tweeting.

The community of MuseScore is very special. Here there are composers, and virtuosos, and beginners, who are just beginning to comprehend the world of sheet music. Our application lacked some part that could unite their interests.  

In our new release, we add functionality that will give you the opportunity to stay in trend, find like-minded people with a common musical taste, and be aware of what is happening in the world of MuseScore.  

The update consists of three parts.

The first is the Feed. This displays the most recently added scores of the composers you are following.

The second is the Notifications. We did not want to cause your frustration, so we placed them separately from the scores tab.

The third part is the Profiles. Now you can look at all the scores that this user added, and find like-minded people among those who subscribe to him.

Stay tuned.

Nervous...very nervous

Tomorrow, at 9:00 am, I audition to get into a high school. I have been homeschooled for so long and I need to go to this high school. I am enrolling in the piano program. To audition I have to play two stylistically different pieces, play two major scales other than C, and demo sight reading. I must get in. Homeschool isn’t for me. It’s boring, I’m falling behind on school, and I feel very lonely. If I don’t get in I will be crushed so I’m gonna try hard. The two pieces I’m playing are Ecossaise by Beethoven and Prelude No. 8 in C minor by Chrissy Ricker. The two scales I’m gonna play are F# major and C# major. Wish me luck tomorrow!

Christopher Larkin's Sheet Music Policy

After it was brought to my attention that distributing sheet music without first consulting the copyright holder(s) is technically infringement, I contacted Christopher Larkin to learn what his policy is. After some back and forth, he told me the following:

We encourage fan remixes/arrangements provided they're free. So upon further thought, it's fine if you want to release your arrangement of Hornet for free on Musescore :)

This is a good thing for this community; as long as you're never making any money off an arrangement/remix/performance, he is okay with it.

However, the moment you make money off something, even if it's something as trivial as ad revenue from YouTube, then Christopher Larkin has every right to take it down. In fact, he still has every right to take even free stuff down, but I don't think that he will exercise that right.

So if you plan to make money off a work derived from Larkin's, you'd better consult with him first. If he doesn't get back to you, chances are that he's still figuring things out; a lack of response is NOT implicit approval. If your project will not generate money, then you're almost certainly good to go, and you shouldn't need to receive explicit permission.