#LILYPOND NOTATION SOFTWARE#
#LILYPOND NOTATION CODE#

I can't think of any technical obstacle to implement a total free input (where I can use my ears and intuition ), and keeping the check for the end. I read something like hiding bars and measuring, but found out that this is not the solution to the (frustrating) problem. Please programmers of musescore, when I change the length of a note in the middle of my score, do not replace it with a rest, but shift in the notes on that staff (or give me the choice to replace or shift), because shifting is what I (and many other musicians) intend to do. So, if you tell me that musescore is better, I say 'yes, it is for some ways, but lilypond is for all ways'. The point is that in denemo (based on lilypond), I do have this TOTAL FREEDOM to go on with my music. All this is done without measures or all the stuff that keeps me from going on with my song in musescore. Once that is done, I start putting the rythm as I have it in mind. When I am creating some music, I first put in the pitch-line, without considering the rythm (even though I already have it in mind). I already saw on the musescore forum that a lot of musicians have the same problem with musescore as I do. Why I still use lilypond when I make music ( as an amateur), is the total freedom at input-time (using denemo or text). a Staff for instance should always have the same tag 'new Staff', with a TYPE- attribute, instead of having for each type of Staff another tag.

Also the way lilypond makes it's reserved words is to complex. Furthermore I think musicxml is a good evolution for a standard music notation.

#LILYPOND NOTATION SOFTWARE#

We like to support Lilypond as they are an ally with us to bring open source software to the market, and meet up with members of the the Lilypond community every now and then.

#LILYPOND NOTATION CODE#

Besides that, as both softwares are following a total different software architecture design, there isn't much overlap between the two projects in terms of code sharing.

The other one is the open source development approach. One is the use of the Emmentaler/Feta font in MuseScore which is originally created by the Lilypond founders. In the end, MuseScore is open source under GPLv2 so feel free to fork it.Īs for MuseScore's connection with Lilypond, there are two things which currently connect us. That said, if a developer demonstrates the capabilities and passion to implement an alternative notation format with a considerable market adoption like Jianpu, we'd be happy to support this effort. The MuseScore team has no plans to work on alternative music notation formats.

Lilypond notation